BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
207.140.0.0/15
Announced exactly
- 207.140.0.0/15AS7018AT&T Enterprises, LLCRPKI Not found207.140.0.0
- Registry
- ARIN · United States · May 22, 1996
- Delegated block
- 207.140.0.0 – 207.141.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 207.140.8.0/21AS54142White Cloud Communications US, LLCRPKI Not found207.140.8.0
- 207.140.16.0/24AS2386AT&T Enterprises, LLCRPKI Not found207.140.16.0
- 207.140.17.0/24AS2386AT&T Enterprises, LLCRPKI Not found207.140.17.0
- 207.140.40.0/23AS26311Ranch WiFi LLCRPKI Not found207.140.40.0
- 207.140.40.0/24AS26311Ranch WiFi LLCRPKI Not found207.140.40.0
- 207.140.41.0/24AS26311Ranch WiFi LLCRPKI Not found207.140.41.0
- 207.140.43.0/24AS6619SamsungSDS Inc.RPKI Not found207.140.43.0
- 207.140.61.0/24AS3942055THCOLUMN LLCRPKI Not found207.140.61.0
- 207.140.66.0/24AS12153HBI Branded Apparel Enterprises, LLCRPKI Not found207.140.66.0
- 207.140.73.0/24AS2386AT&T Enterprises, LLCRPKI Not found207.140.73.0
- 207.140.115.0/24AS54809MCM Systems, LLCRPKI Not found207.140.115.0
- 207.140.148.0/24AS7310Gartner GroupRPKI Not found207.140.148.0
- 207.140.149.0/24AS13581SHI International Corp.RPKI Valid207.140.149.0
- 207.140.191.0/24AS13581SHI International Corp.RPKI Valid207.140.191.0
- 207.140.201.0/24AS25762Bank of ChinaRPKI Valid207.140.201.0
- 207.140.216.0/23AS4473AT&T Enterprises, LLCRPKI Not found207.140.216.0
- 207.140.220.0/22AS4473AT&T Enterprises, LLCRPKI Not found207.140.220.0
- 207.141.26.0/24AS11211NCIC Operator ServicesRPKI Not found207.141.26.0
- 207.141.72.0/24AS13641UNASSIGNEDRPKI Not found207.141.72.0
- 207.141.73.0/24AS13641UNASSIGNEDRPKI Not found207.141.73.0
- 207.141.74.0/24AS13641UNASSIGNEDRPKI Not found207.141.74.0
- 207.141.75.0/24AS13641UNASSIGNEDRPKI Not found207.141.75.0
- 207.141.76.0/22AS13641UNASSIGNEDRPKI Not found207.141.76.0
- 207.141.100.0/24AS394819NNSA Office Of Secure TransportationRPKI Not found207.141.100.0
- 207.141.187.0/24AS2386AT&T Enterprises, LLCRPKI Not found207.141.187.0
- 207.141.218.0/24AS47016Extron ElectronicsRPKI Not found207.141.218.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 49.224.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.