Tools
Speed test, network tools, Config Compare, and Looking Glass — outside-in BGP, RPKI and IRR checks.
Network toolbox#
- Speed test — browser-based throughput/latency test against the platform.
- Network tools — ping, traceroute, DNS lookup, WHOIS, port checks from the server side, and My IP: dual-stack public-address detection with geo/ASN detail. The IPv4 and IPv6 probes run from yourbrowser (that's the only place both families can be observed); if something blocks them — an extension, a filtering network — the tool says it couldn't check rather than claiming a family is absent.
- Config Compare — side-by-side diff for configs, route tables and any text dump, with block-aware sorting and major/minor change classification. See
Config Comparebelow. - Looking Glass — see routing from the internet toward your networks. Enter a domain, IP, prefix or ASN and get a verdict on how the global BGP table carries it. See
Looking Glassbelow.
Looking Glass#
One input — domain, IP, prefix or ASN — resolves to the prefix the global routing table actually carries, and returns a verdict scorecard, a world map of which route collectors can see you, the per-collector detail, and the AS paths. Data comes from RIPE's 23 active route collectors and their ~370 peering sessions. No packets are sent to the network being examined, and no sign-in is required. Open Looking Glass →
Findings are split into checks, which drive the headline verdict, and signals, which add context and can raise “needs attention” but never mark an otherwise-clean prefix as broken.
| Announced | Whether the global table carries a route covering the resource — and, when you asked about an aggregate, which more-specific prefix is actually carried. |
| Origin / MOAS | Which AS originates the prefix, and whether more than one does. Multiple origins belonging to the same organisation — an AS migration, a dual-homed customer — are a warning rather than a conflict. A second origin seen by only a handful of peers is called out separately: that is what a quiet hijack looks like from outside, and it is exactly what the default filtering on most routing data hides. |
| RPKI | ROA validity, per origin. All four states are distinguished, because invalid_asn and invalid_length have opposite remediations and unknown means no ROA covers the prefix at all. The ROA's current maxLength is named — “widen maxLength” is not actionable without it. |
| IRR | Reconciles the announcement against the routing registries. A route object naming a different AS than the one announcing is a failure: upstreams that rebuild prefix filters from IRR will either reject your announcement or accept someone else's. |
| Address space | Whether the prefix falls inside reserved or special-purpose space that should not cross the public internet. |
| Communities | Traffic-suppression and propagation tags. BLACKHOLE (RFC 7999) and NO_ADVERTISE fail: a blackholed prefix is announced and unreachable at the same time, which no reachability probe from a single vantage point can tell apart from a healthy route. |
Signals cover visibility (the share of RIS peers carrying the route), route age (recently-appeared address space is worth a look), ORIGIN attribute (redistribution into BGP is the fingerprint of the classic accidental leak), deaggregation (different peers seeing different prefix lengths), and NO_EXPORT, which is graded by how many sessions carry it — on one session out of several hundred it is a peer's own policy, not a limit on your prefix.
Entering an ASN reports the network rather than a prefix: holder and registry, how much address space it announces, per-family visibility, observed BGP neighbours, and its announced-prefix inventory — click any prefix to run a full report on it.
A run updates the URL, so a result can be linked, bookmarked or recovered with the back button; the link re-runs the lookup, so what someone else opens is current rather than a stale snapshot. The verdict can be copied or downloaded as Markdown or JSON for a ticket or a peering email, and the collector table exports to CSV.
Self-test (admin)#
Administrators can run the built-in self-test suite that exercises every network tool end-to-end and reports pass/fail — assurance that the toolbox itself is healthy.
Visitor analytics (admin)#
Tool usage captures rich, anonymous-appropriate metadata (browser, OS, screen, connection, geography) presented in an admin dashboard — usable for capacity planning and audience insight.