BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
207.30.0.0/16
Announced exactly
- 207.30.0.0/16AS209CenturyLink Communications, LLCRPKI Not found207.30.0.0
- Registry
- ARIN · United States · Jan 22, 1996
- Delegated block
- 207.30.0.0 – 207.30.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 207.30.0.0/18AS2379CenturyLink Communications, LLCRPKI Not found207.30.0.0
- 207.30.5.0/24AS209CenturyLink Communications, LLCRPKI Not found207.30.5.0
- 207.30.6.0/23AS209CenturyLink Communications, LLCRPKI Not found207.30.6.0
- 207.30.11.0/24AS209CenturyLink Communications, LLCRPKI Not found207.30.11.0
- 207.30.21.0/24AS209CenturyLink Communications, LLCRPKI Not found207.30.21.0
- 207.30.28.0/24AS22511Presidio Networked Solutions LLCRPKI Not found207.30.28.0
- 207.30.29.0/24AS22511Presidio Networked Solutions LLCRPKI Not found207.30.29.0
- 207.30.32.0/24AS12090AAA NationalRPKI Not found207.30.32.0
- 207.30.48.0/24AS209CenturyLink Communications, LLCRPKI Not found207.30.48.0
- 207.30.52.0/24AS209CenturyLink Communications, LLCRPKI Not found207.30.52.0
- 207.30.62.0/23AS46729Saint Leo University IncorporatedRPKI Not found207.30.62.0
- 207.30.64.0/21AS2379CenturyLink Communications, LLCRPKI Not found207.30.64.0
- 207.30.68.0/23AS209CenturyLink Communications, LLCRPKI Not found207.30.68.0
- 207.30.72.0/23AS2379CenturyLink Communications, LLCRPKI Not found207.30.72.0
- 207.30.74.0/24AS2379CenturyLink Communications, LLCRPKI Not found207.30.74.0
- 207.30.76.0/22AS2379CenturyLink Communications, LLCRPKI Not found207.30.76.0
- 207.30.80.0/20AS2379CenturyLink Communications, LLCRPKI Not found207.30.80.0
- 207.30.80.0/22AS4282CenturyLink Communications, LLCRPKI Not found207.30.80.0
- 207.30.96.0/19AS2379CenturyLink Communications, LLCRPKI Not found207.30.96.0
- 207.30.118.0/24AS209CenturyLink Communications, LLCRPKI Not found207.30.118.0
- 207.30.119.0/24AS209CenturyLink Communications, LLCRPKI Not found207.30.119.0
- 207.30.128.0/17AS2379CenturyLink Communications, LLCRPKI Not found207.30.128.0
- 207.30.145.0/24AS2379CenturyLink Communications, LLCRPKI Not found207.30.145.0
- 207.30.159.0/24AS209CenturyLink Communications, LLCRPKI Not found207.30.159.0
- 207.30.162.0/24AS209CenturyLink Communications, LLCRPKI Not found207.30.162.0
- 207.30.168.0/24AS209CenturyLink Communications, LLCRPKI Not found207.30.168.0
- 207.30.182.0/24AS209CenturyLink Communications, LLCRPKI Not found207.30.182.0
- 207.30.184.0/24AS3356Level 3 Parent, LLCRPKI Not found207.30.184.0
- 207.30.190.0/23AS209CenturyLink Communications, LLCRPKI Not found207.30.190.0
- 207.30.190.0/24AS209CenturyLink Communications, LLCRPKI Not found207.30.190.0
- 207.30.191.0/24AS209CenturyLink Communications, LLCRPKI Not found207.30.191.0
- 207.30.192.0/23AS209CenturyLink Communications, LLCRPKI Not found207.30.192.0
- 207.30.201.0/24AS209CenturyLink Communications, LLCRPKI Not found207.30.201.0
- 207.30.202.0/23AS209CenturyLink Communications, LLCRPKI Not found207.30.202.0
- 207.30.204.0/23AS209CenturyLink Communications, LLCRPKI Not found207.30.204.0
- 207.30.206.0/23AS209CenturyLink Communications, LLCRPKI Not found207.30.206.0
- 207.30.217.0/24AS209CenturyLink Communications, LLCRPKI Not found207.30.217.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.