BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
206.8.0.0/14
Announced exactly
- 206.8.0.0/14AS5006Inteliquent, inc.RPKI Not found206.8.0.0
- Registry
- ARIN · United States · May 8, 1995
- Delegated block
- 206.8.0.0 – 206.11.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 206.8.2.0/24AS15011Jaguar CommunicationsRPKI Not found206.8.2.0
- 206.8.120.0/24AS5006Inteliquent, inc.RPKI Not found206.8.120.0
- 206.8.121.0/24AS5006Inteliquent, inc.RPKI Not found206.8.121.0
- 206.8.122.0/24AS5006Inteliquent, inc.RPKI Not found206.8.122.0
- 206.8.123.0/24AS5006Inteliquent, inc.RPKI Not found206.8.123.0
- 206.8.196.0/24AS40160Inteliquent, inc.RPKI Not found206.8.196.0
- 206.8.250.0/24AS40160Inteliquent, inc.RPKI Not found206.8.250.0
- 206.8.255.0/24AS40160Inteliquent, inc.RPKI Not found206.8.255.0
- 206.9.85.0/24AS5006Inteliquent, inc.RPKI Not found206.9.85.0
- 206.9.205.0/24AS15011Jaguar CommunicationsRPKI Not found206.9.205.0
- 206.9.206.0/23AS15011Jaguar CommunicationsRPKI Not found206.9.206.0
- 206.9.208.0/23AS15011Jaguar CommunicationsRPKI Not found206.9.208.0
- 206.9.215.0/24AS15011Jaguar CommunicationsRPKI Not found206.9.215.0
- 206.9.217.0/24AS15011Jaguar CommunicationsRPKI Not found206.9.217.0
- 206.9.220.0/23AS15011Jaguar CommunicationsRPKI Not found206.9.220.0
- 206.9.240.0/24AS15011Jaguar CommunicationsRPKI Not found206.9.240.0
- 206.9.255.0/24AS5715Inteliquent, inc.RPKI Not found206.9.255.0
- 206.10.80.0/21AS5006Inteliquent, inc.RPKI Not found206.10.80.0
- 206.10.110.0/23AS55076Johnson Telephone CompanyRPKI Not found206.10.110.0
- 206.10.124.0/24AS15011Jaguar CommunicationsRPKI Not found206.10.124.0
- 206.10.152.0/21AS5006Inteliquent, inc.RPKI Not found206.10.152.0
- 206.10.152.0/22AS5006Inteliquent, inc.RPKI Not found206.10.152.0
- 206.10.156.0/22AS5006Inteliquent, inc.RPKI Not found206.10.156.0
- 206.11.16.0/24AS40160Inteliquent, inc.RPKI Not found206.11.16.0
- 206.11.94.0/24AS35985One Ring Networks, Inc.RPKI Not found206.11.94.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 85.240.0.0/13. This tool looks a prefix up in our daily copy of the global routing table and shows three things:
- Exact announcements: which AS originates exactly this prefix. More than one origin (a MOAS) is normal for anycast services and some multihomed networks, and suspicious otherwise.
- Covering routes: less-specific announcements that contain it. Traffic follows the most specific route, so a covering route matters if the more-specific one disappears.
- More-specifics: announcements inside it, which may belong to other networks (customers, or a hijack).
Each announced route is also checked against the RPKI: whether a ROA authorises its origin AS.
The table is the view from APNIC’s route collector. Most of the global table is the same from everywhere, but a route that is filtered before it reaches that collector will not appear.
Frequently asked questions
Why is my /24 not listed but a /16 is?
Your addresses are announced as part of the larger block, and no one announces the /24 separately. That is the normal case for most customers of a provider.
What is a more-specific hijack?
Someone announces a longer prefix inside your space. Because routers prefer the most specific route, traffic goes to them. RPKI with a strict max length makes such announcements invalid.
Can I enter a single address?
Yes. The tool then shows the most specific announced route that contains it.