BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
47.208.0.0/12
Announced exactly
- 47.208.0.0/12AS19108OptimumRPKI Not found47.208.0.0
- Registry
- ARIN · United States · Sep 8, 2015
- Delegated block
- 47.208.0.0 – 47.223.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 47.208.0.0/15AS19108OptimumRPKI Not found47.208.0.0
- 47.209.64.0/18AS19108OptimumRPKI Not found47.209.64.0
- 47.209.80.0/20AS19108OptimumRPKI Not found47.209.80.0
- 47.209.128.0/17AS19108OptimumRPKI Not found47.209.128.0
- 47.209.192.0/19AS19108OptimumRPKI Not found47.209.192.0
- 47.210.0.0/15AS19108OptimumRPKI Not found47.210.0.0
- 47.210.0.0/17AS19108OptimumRPKI Not found47.210.0.0
- 47.210.128.0/17AS19108OptimumRPKI Not found47.210.128.0
- 47.211.144.0/20AS19108OptimumRPKI Not found47.211.144.0
- 47.211.192.0/20AS19108OptimumRPKI Not found47.211.192.0
- 47.211.208.0/20AS19108OptimumRPKI Not found47.211.208.0
- 47.212.0.0/14AS19108OptimumRPKI Not found47.212.0.0
- 47.212.0.0/17AS19108OptimumRPKI Not found47.212.0.0
- 47.212.96.0/19AS19108OptimumRPKI Not found47.212.96.0
- 47.212.192.0/20AS19108OptimumRPKI Not found47.212.192.0
- 47.213.0.0/16AS19108OptimumRPKI Not found47.213.0.0
- 47.213.80.0/20AS19108OptimumRPKI Not found47.213.80.0
- 47.213.112.0/20AS19108OptimumRPKI Not found47.213.112.0
- 47.213.182.0/23AS19108OptimumRPKI Not found47.213.182.0
- 47.214.0.0/16AS19108OptimumRPKI Not found47.214.0.0
- 47.214.28.0/22AS19108OptimumRPKI Not found47.214.28.0
- 47.214.32.0/22AS19108OptimumRPKI Not found47.214.32.0
- 47.214.36.0/22AS19108OptimumRPKI Not found47.214.36.0
- 47.214.40.0/22AS19108OptimumRPKI Not found47.214.40.0
- 47.214.44.0/22AS19108OptimumRPKI Not found47.214.44.0
- 47.214.48.0/22AS19108OptimumRPKI Not found47.214.48.0
- 47.214.128.0/18AS19108OptimumRPKI Not found47.214.128.0
- 47.214.192.0/18AS19108OptimumRPKI Not found47.214.192.0
- 47.215.32.0/23AS19108OptimumRPKI Not found47.215.32.0
- 47.215.68.0/22AS19108OptimumRPKI Not found47.215.68.0
- 47.215.96.0/20AS19108OptimumRPKI Not found47.215.96.0
- 47.215.128.0/17AS19108OptimumRPKI Not found47.215.128.0
- 47.215.128.0/18AS19108OptimumRPKI Not found47.215.128.0
- 47.215.192.0/18AS19108OptimumRPKI Not found47.215.192.0
- 47.216.0.0/16AS19108OptimumRPKI Not found47.216.0.0
- 47.216.0.0/17AS19108OptimumRPKI Not found47.216.0.0
- 47.216.128.0/17AS19108OptimumRPKI Not found47.216.128.0
- 47.216.144.0/20AS19108OptimumRPKI Not found47.216.144.0
- 47.217.0.0/16AS19108OptimumRPKI Not found47.217.0.0
- 47.217.128.0/18AS19108OptimumRPKI Not found47.217.128.0
- 47.217.192.0/18AS19108OptimumRPKI Not found47.217.192.0
- 47.218.0.0/15AS19108OptimumRPKI Not found47.218.0.0
- 47.218.0.0/17AS19108OptimumRPKI Not found47.218.0.0
- 47.218.8.0/22AS19108OptimumRPKI Not found47.218.8.0
- 47.218.12.0/22AS19108OptimumRPKI Not found47.218.12.0
- 47.218.16.0/22AS19108OptimumRPKI Not found47.218.16.0
- 47.218.20.0/22AS19108OptimumRPKI Not found47.218.20.0
- 47.218.128.0/17AS19108OptimumRPKI Not found47.218.128.0
- 47.219.0.0/17AS19108OptimumRPKI Not found47.219.0.0
- 47.219.128.0/17AS19108OptimumRPKI Not found47.219.128.0
- 47.219.176.0/20AS19108OptimumRPKI Not found47.219.176.0
- 47.220.0.0/14AS19108OptimumRPKI Not found47.220.0.0
- 47.221.0.0/17AS19108OptimumRPKI Not found47.221.0.0
- 47.221.128.0/17AS19108OptimumRPKI Not found47.221.128.0
- 47.223.0.0/17AS19108OptimumRPKI Not found47.223.0.0
- 47.223.128.0/17AS19108OptimumRPKI Not found47.223.128.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 158.36.0.0/14. 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.