BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
204.134.0.0/16
Announced exactly
- 204.134.0.0/16AS209CenturyLink Communications, LLCRPKI Not found204.134.0.0
- Registry
- ARIN · United States · Aug 26, 1994
- Delegated block
- 204.134.0.0 – 204.134.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 204.134.48.0/24AS3912CHECSRPKI Not found204.134.48.0
- 204.134.49.0/24AS3912CHECSRPKI Not found204.134.49.0
- 204.134.50.0/24AS3912CHECSRPKI Not found204.134.50.0
- 204.134.54.0/24AS17153New Mexico TechRPKI Not found204.134.54.0
- 204.134.55.0/24AS3912CHECSRPKI Not found204.134.55.0
- 204.134.56.0/23AS3912CHECSRPKI Not found204.134.56.0
- 204.134.66.0/24AS3912CHECSRPKI Not found204.134.66.0
- 204.134.67.0/24AS40498New Mexico Lambda Rail, Inc.RPKI Not found204.134.67.0
- 204.134.68.0/24AS40498New Mexico Lambda Rail, Inc.RPKI Not found204.134.68.0
- 204.134.85.0/24AS11570Eastern New Mexico UniversityRPKI Not found204.134.85.0
- 204.134.98.0/23AS19437SECURED SERVERS LLCRPKI Not found204.134.98.0
- 204.134.102.0/24AS3912CHECSRPKI Not found204.134.102.0
- 204.134.103.0/24AS3912CHECSRPKI Not found204.134.103.0
- 204.134.152.0/24AS397024AMG National Trust BankRPKI Not found204.134.152.0
- 204.134.155.0/24AS3356Level 3 Parent, LLCRPKI Not found204.134.155.0
- 204.134.194.0/23AS395846Direct Communications Rockland, IncRPKI Not found204.134.194.0
- 204.134.224.0/21AS17380Project Mutual Telephone Cooperative Association, Inc.RPKI Not found204.134.224.0
- 204.134.234.0/24AS397157UNASSIGNEDRPKI Not found204.134.234.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.