▸ OVERALL TRAFFIC STATS INTERNET TO A LOT OF AS10214 EYEBALLS
▸ INBOUND TRAFFIC (24H)
▸ INBOUND TRAFFIC (24H)
▸ INBOUND TRAFFIC (24H)
▸ PER–SYD POP TO POP UTILISATION INTER-CAPITAL FIBRE PATHS
▸ NBN POI UTILISATION WA · — POIs
▸ INTERNET LATENCY ICMP PINGERS EVERY ~30s
▸ DNS POWERDNS RECURSORS · QUESTIONS PER SECOND
If DNS is broken, your internet is functionally broken. We run two PowerDNS recursors per site and advertise the same anycast resolver IPs from both nodes via BGP to all edge/border routers. Selective AS-path prepends prefer the primary while preserving automatic failover if a recursor or upstream path fails. We also perform regular security patching and updates, with monitoring and alerting for service health and performance.
▸ DNS QUESTIONS BY RECURSOR (24H)
▸ LOOKING GLASS PER01 · SYD01 · VIA LG.PENTANET.COM.AU
───────────────────────────────────────────────────── Ready. Pick a query type, target, and press SEND. ─────────────────────────────────────────────────────
▸ STATUS & INCIDENTS VIA PENTANET.COM.AU/NETWORK-STATUS
▸ ABOUT / FEEDBACK BUILT BY THE ENGINEERS, NOT THE MARKETERS
This dashboard is built and maintained by Pentanet's Network and Technology teams — the same engineers who plan, deploy, and run AS10214. It exists to show off what's genuinely happening inside the network: packets, paths, latencies, pings, subscriber stability. No spin, no curation.
If you're curious, the web server you're talking to (which has no direct connection to any AS10214 network infrastructure) just fetches data from a dedicated Grafana instance behind a firewall, which fans out to our metrics and observability tools (Akvorado for flows, Telegraf and Zabbix for monitoring, InfluxDB and Postgres for data) — the same plumbing and data our engineers might use.