BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
206.72.0.0/18
Announced exactly
- 206.72.0.0/18AS5056Aureon Network ServicesRPKI Not found206.72.0.0
- Registry
- ARIN · United States · Jul 28, 1995
- Delegated block
- 206.72.0.0 – 206.72.63.255
Covering routes
No less-specific route covers it.
More-specific routes
- 206.72.2.0/24AS62825Walnut CommunicationsRPKI Not found206.72.2.0
- 206.72.5.0/24AS397305FMCTCRPKI Not found206.72.5.0
- 206.72.6.0/24AS397305FMCTCRPKI Not found206.72.6.0
- 206.72.9.0/24AS63394Eastern Iowa IP, LLCRPKI Not found206.72.9.0
- 206.72.13.0/24AS20273WCCTARPKI Not found206.72.13.0
- 206.72.16.0/24AS5056Aureon Network ServicesRPKI Not found206.72.16.0
- 206.72.17.0/24AS397475F&B Communications, Inc.RPKI Not found206.72.17.0
- 206.72.20.0/24AS63394Eastern Iowa IP, LLCRPKI Not found206.72.20.0
- 206.72.23.0/24AS395876Huxley Communications CooperativeRPKI Not found206.72.23.0
- 206.72.25.0/24AS399559Alpine Communications L.C.RPKI Not found206.72.25.0
- 206.72.26.0/24AS62825Walnut CommunicationsRPKI Not found206.72.26.0
- 206.72.27.0/24AS33690Aureon Network ServicesRPKI Not found206.72.27.0
- 206.72.29.0/24AS5056Aureon Network ServicesRPKI Not found206.72.29.0
- 206.72.33.0/24AS399693Northwest CommunicationsRPKI Not found206.72.33.0
- 206.72.35.0/24AS399693Northwest CommunicationsRPKI Not found206.72.35.0
- 206.72.36.0/22AS399693Northwest CommunicationsRPKI Not found206.72.36.0
- 206.72.40.0/23AS399693Northwest CommunicationsRPKI Not found206.72.40.0
- 206.72.43.0/24AS399693Northwest CommunicationsRPKI Not found206.72.43.0
- 206.72.44.0/22AS399693Northwest CommunicationsRPKI Not found206.72.44.0
- 206.72.48.0/23AS399693Northwest CommunicationsRPKI Not found206.72.48.0
- 206.72.50.0/24AS399693Northwest CommunicationsRPKI Not found206.72.50.0
- 206.72.51.0/24AS18883FiberNet Communications L.C.RPKI Not found206.72.51.0
- 206.72.52.0/22AS399693Northwest CommunicationsRPKI Not found206.72.52.0
- 206.72.56.0/21AS397446Midwest Fiber Network, LLCRPKI Not found206.72.56.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 62.103.0.0/16. 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.