Data methodology
How this website collects and displays public routing information, and what the results do not establish.
Sources
RIPEstat / RIPE RIS. Routing lookups use RIPE NCC public data endpoints. BGP paths are collector observations. Results depend on collector coverage and collection schedules.
PeeringDB. Operator name, ASN, open peering policy and public contact information are based on the network's public profile. The website does not synchronize PeeringDB automatically.
Configured prefixes. The IPv6 table shows four prefixes configured for this portal, not every possible active advertisement. Compare with independent routing datasets before taking operational action.
Limitations and freshness
No claim is made about real-time router health, end-to-end service availability, prefix ownership beyond published registries or live BGP sessions. A missing route in RIS is not evidence that the route is absent everywhere. In this static edition, the browser contacts RIPEstat directly; caching and limits are controlled by RIPEstat.
RIS Looking Glass observations are near-real-time, with reporting delay. ASN-level routing status is a periodic snapshot. Observation timestamps are shown where provided by the upstream API.
API access
External public RIPEstat data endpoint: /api/health, /api/network/overview, https://stat.ripe.net/data/looking-glass/data.json?resource=AS218605. Queries are subject to public RIPEstat limits; this static deployment does not have its own server-side rate limiting.