BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
204.248.0.0/14
Announced exactly
- 204.248.0.0/14AS174Cogent Communications, LLCRPKI Not found204.248.0.0
- Registry
- ARIN · United States · Feb 1, 1995
- Delegated block
- 204.248.0.0 – 204.251.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 204.248.112.0/20AS14828Hiawatha Broadband Communications, IncRPKI Not found204.248.112.0
- 204.249.32.0/20AS4133Bitwise Internet Technologies, Inc.RPKI Not found204.249.32.0
- 204.249.64.0/21AS29968Dunkirk & Fredonia Telephone CompanyRPKI Not found204.249.64.0
- 204.249.64.0/23AS29968Dunkirk & Fredonia Telephone CompanyRPKI Not found204.249.64.0
- 204.249.66.0/23AS29968Dunkirk & Fredonia Telephone CompanyRPKI Not found204.249.66.0
- 204.249.68.0/23AS29968Dunkirk & Fredonia Telephone CompanyRPKI Not found204.249.68.0
- 204.249.70.0/23AS29968Dunkirk & Fredonia Telephone CompanyRPKI Not found204.249.70.0
- 204.249.124.0/22AS209CenturyLink Communications, LLCRPKI Not found204.249.124.0
- 204.249.180.0/24AS400471WHEATLAND ELECTRIC COOPERATIVE, INCRPKI Not found204.249.180.0
- 204.249.192.0/20AS8025BrightNet OklahomaRPKI Not found204.249.192.0
- 204.250.24.0/24AS18632Volcano Vision, Inc.RPKI Not found204.250.24.0
- 204.250.80.0/21AS11924Montana Opticom, LLCRPKI Not found204.250.80.0
- 204.250.82.0/24AS11924Montana Opticom, LLCRPKI Not found204.250.82.0
- 204.250.83.0/24AS11924Montana Opticom, LLCRPKI Not found204.250.83.0
- 204.250.84.0/23AS11924Montana Opticom, LLCRPKI Not found204.250.84.0
- 204.250.86.0/23AS11924Montana Opticom, LLCRPKI Not found204.250.86.0
- 204.250.96.0/20AS3734Santa Clara County Office of EducationRPKI Not found204.250.96.0
- 204.250.160.0/24AS174Cogent Communications, LLCRPKI Not found204.250.160.0
- 204.250.250.0/23AS54239BLOOMINGDALE HOME TELEPHONE COMPANY, INCRPKI Not found204.250.250.0
- 204.251.32.0/22AS2933Real/Time CommunicationsRPKI Not found204.251.32.0
- 204.251.175.0/24AS22903Databank Holdings, LtdRPKI Not found204.251.175.0
- 204.251.218.0/24AS400471WHEATLAND ELECTRIC COOPERATIVE, INCRPKI Not found204.251.218.0
- 204.251.219.0/24AS400471WHEATLAND ELECTRIC COOPERATIVE, INCRPKI Not found204.251.219.0
- 204.251.230.0/24AS20325Patelco Credit UnionRPKI Not found204.251.230.0
- 204.251.255.0/24AS46853Southwest Texas CommunicationsRPKI Not found204.251.255.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 2.48.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.