BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
208.186.0.0/15
Announced exactly
- 208.186.0.0/15AS7385Allstream Business US, LLCRPKI Not found208.186.0.0
- Registry
- ARIN · United States · Aug 24, 1999
- Delegated block
- 208.186.0.0 – 208.186.127.255
Covering routes
No less-specific route covers it.
More-specific routes
- 208.186.8.0/23AS36012HUNTER COMMUNICATIONSRPKI Valid208.186.8.0
- 208.186.48.0/20AS21541101NetlinkRPKI Valid208.186.48.0
- 208.186.48.0/24AS21541101NetlinkRPKI Valid208.186.48.0
- 208.186.56.0/24AS21541101NetlinkRPKI Valid208.186.56.0
- 208.186.57.0/24AS21541101NetlinkRPKI Valid208.186.57.0
- 208.186.58.0/24AS21541101NetlinkRPKI Valid208.186.58.0
- 208.186.62.0/24AS21541101NetlinkRPKI Valid208.186.62.0
- 208.186.112.0/24AS16578Lanset America CorporationRPKI Valid208.186.112.0
- 208.186.113.0/24AS16578Lanset America CorporationRPKI Valid208.186.113.0
- 208.186.204.0/23AS23465NuveraRPKI Valid208.186.204.0
- 208.187.44.0/23AS23465NuveraRPKI Valid208.187.44.0
- 208.187.116.0/23AS23465NuveraRPKI Valid208.187.116.0
- 208.187.120.0/22AS23465NuveraRPKI Valid208.187.120.0
- 208.187.160.0/24AS16578Lanset America CorporationRPKI Valid208.187.160.0
- 208.187.161.0/24AS16578Lanset America CorporationRPKI Valid208.187.161.0
- 208.187.162.0/24AS16578Lanset America CorporationRPKI Valid208.187.162.0
- 208.187.163.0/24AS16578Lanset America CorporationRPKI Valid208.187.163.0
- 208.187.164.0/24AS16578Lanset America CorporationRPKI Valid208.187.164.0
- 208.187.165.0/24AS16578Lanset America CorporationRPKI Valid208.187.165.0
- 208.187.166.0/24AS16578Lanset America CorporationRPKI Valid208.187.166.0
- 208.187.167.0/24AS16578Lanset America CorporationRPKI Valid208.187.167.0
- 208.187.232.0/24AS29951SyptecRPKI Valid208.187.232.0
- 208.187.244.0/24AS16578Lanset America CorporationRPKI Valid208.187.244.0
- 208.187.245.0/24AS16578Lanset America CorporationRPKI Valid208.187.245.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 193.166.0.0/15. 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.