BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
68.248.0.0/13
Announced exactly
- 68.248.0.0/13AS7018AT&T Enterprises, LLCRPKI Not found68.248.0.0
- Registry
- ARIN · United States · Aug 1, 2003
- Delegated block
- 68.248.0.0 – 68.255.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 68.250.141.0/24AS21900LAW BULLETIN PUBLISHING COMPANYRPKI Not found68.250.141.0
- 68.251.166.0/24AS394135Securitas Electronic Security, Inc.RPKI Not found68.251.166.0
- 68.251.194.0/24AS393635Area-Wide Technologies, IncRPKI Not found68.251.194.0
- 68.251.195.0/24AS393635Area-Wide Technologies, IncRPKI Not found68.251.195.0
- 68.251.204.0/24AS32625OFFSITE, LLCRPKI Not found68.251.204.0
- 68.251.212.0/24AS22197Apps CommunicationsRPKI Not found68.251.212.0
- 68.252.156.0/22AS27482American Eagle Computer Products, Inc.RPKI Not found68.252.156.0
- 68.255.42.0/24AS31759La Rabida HospitalRPKI Not found68.255.42.0
- 68.255.122.0/24AS54283FORUM Credit UnionRPKI Not found68.255.122.0
- 68.255.128.0/24AS31759La Rabida HospitalRPKI Not found68.255.128.0
- 68.255.220.0/24AS36528UNASSIGNEDRPKI Not found68.255.220.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.