About Kynex BGP
Kynex BGP is a public Internet routing lookup tool operated by Kynex Technologies India Private Limited. It brings together public BGP, RPKI, IRR and registry data for an ASN, IP address, prefix or domain, and shows where each piece of information came from and how fresh it is.
Data sources and attribution
| Source | Used for | Attribution |
|---|---|---|
| RouteViews | Prefixes originated by an ASN, routes and AS paths seen by collector peers, collector sessions, collector list, RPKI state (RouteViews validator). | University of Oregon Route Views Project. Data used via the public RouteViews API. |
| RIPEstat Data API | ASN holder and registration, address registration (whois), related prefixes, inferred neighbours, RPKI validation. | RIPE NCC. Data from RIPE RIS and the Regional Internet Registries, used under the RIPEstat terms of service. |
| NLNOG IRRexplorer | IRR route/route6 objects per registry and AS-set membership. | NLNOG. Aggregates public Internet Routing Registry databases. |
| PeeringDB | Network name, website, IRR AS-set, peering policy, IX and facility counts. | PeeringDB data, used under the PeeringDB Acceptable Use Policy. |
Domain searches use this server's DNS resolver to find addresses; only public addresses are shown. All requests to providers are made by the Kynex BGP server, never by your browser.
Freshness and update frequency
Data is fetched from the providers when a page is requested and cached for a configurable time. Default cache lifetimes: routes and AS paths 5 minutes, RPKI 15 minutes, IRR 1 hour, registration and PeeringDB data 24 hours. The operator may change these. Every lookup page shows, for each source:
- Live — fetched from the provider for this request;
- Cached — served from cache within its lifetime;
- Stale — the provider failed, so an older cached copy is shown and labelled;
- Unavailable — no data could be obtained. This never means “no records”.
The “Provider observation” time is the newest timestamp the provider itself reported, when it reports one.
Limitations
- Route collectors see the Internet only through the networks that peer with them. A route seen by collectors is not proof of global visibility, and a route that is not seen may still be reachable.
- ASNs next to another ASN in an AS path are path adjacencies. They are not proof of a direct BGP session or of a customer/provider relationship.
- RIPEstat neighbours are inferences from RIPE RIS data, not confirmed relationships.
- IRR objects are registrations, not cryptographic authorisations. Only RPKI ROAs authorise route origins.
- RPKI “Unknown” means the state could not be determined (for example the validator was unreachable). It is never shown as Valid.
- RouteViews' per-ASN prefix list has no per-prefix timestamp; “last observed” times come from individual route lookups.
- Large networks are sampled: route and peer pages look up a limited number of prefixes per page to respect provider rate limits.
- The looking glass queries public data APIs only. It has no access to any router.
- No global Internet statistics are shown, because none are computed from a complete data set here.
Contact
Contact details will be published by the site operator.
API documentation for this site: /docs (OpenAPI).