BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
212.100.160.0/19
Announced exactly
- 212.100.160.0/19AS3257GTT Communications Inc.RPKI Valid212.100.160.0
- Registry
- RIPE NCC · Belgium · Jul 12, 1999
- Delegated block
- 212.100.160.0 – 212.100.191.255
Covering routes
No less-specific route covers it.
More-specific routes
- 212.100.164.0/24AS401476Spruce Creek Networks LLCRPKI Valid212.100.164.0
- 212.100.166.0/24AS212238Datacamp LimitedRPKI Valid212.100.166.0
- 212.100.168.0/24AS42831UK Dedicated Servers LimitedRPKI Valid212.100.168.0
- 212.100.169.0/24AS133398Tele Asia LimitedRPKI Valid212.100.169.0
- 212.100.170.0/24AS40676Psychz NetworksRPKI Valid212.100.170.0
- 212.100.171.0/24AS16276OVH SASRPKI Valid212.100.171.0
- 212.100.172.0/23AS215262Cloud Nord LimitedRPKI Valid212.100.172.0
- 212.100.172.0/24AS215262Cloud Nord LimitedRPKI Valid212.100.172.0
- 212.100.173.0/24AS215262Cloud Nord LimitedRPKI Valid212.100.173.0
- 212.100.174.0/24AS46450Pilot Fiber, Inc.RPKI Valid212.100.174.0
- 212.100.175.0/24AS395954Leaseweb USA, Inc.RPKI Valid212.100.175.0
- 212.100.178.0/24AS40244Turnkey Internet Inc.RPKI Valid212.100.178.0
- 212.100.184.0/24AS210495WENIUM LTDRPKI Valid212.100.184.0
- 212.100.186.0/24AS10111Zeofast NetworkRPKI Valid212.100.186.0
- 212.100.187.0/24AS135402Wired ISP Inc.RPKI Valid212.100.187.0
- 212.100.188.0/24AS214049Netera LLCRPKI Valid212.100.188.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 193.166.0.0/15. 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.