BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
217.79.96.0/19
Announced exactly
- 217.79.96.0/19AS3257GTT Communications Inc.RPKI Not found217.79.96.0
- Registry
- RIPE NCC · United Kingdom · Jan 2, 2001
- Delegated block
- 217.79.96.0 – 217.79.111.255
Covering routes
No less-specific route covers it.
More-specific routes
- 217.79.96.0/24AS9304HGC Global Communications LimitedRPKI Valid217.79.96.0
- 217.79.98.0/24AS395954Leaseweb USA, Inc.RPKI Valid217.79.98.0
- 217.79.99.0/24AS399631StreamICanRPKI Valid217.79.99.0
- 217.79.104.0/24AS212238Datacamp LimitedRPKI Valid217.79.104.0
- 217.79.105.0/24AS212238Datacamp LimitedRPKI Valid217.79.105.0
- 217.79.106.0/24AS212238Datacamp LimitedRPKI Valid217.79.106.0
- 217.79.107.0/24AS212238Datacamp LimitedRPKI Valid217.79.107.0
- 217.79.108.0/24AS393502Zenlayer IncRPKI Valid217.79.108.0
- 217.79.112.0/24AS152460Greenhost BVRPKI Valid217.79.112.0
- 217.79.113.0/24AS198566MAMUT RAHAL SOFTWARE - FZCORPKI Valid217.79.113.0
- 217.79.116.0/24AS212238Datacamp LimitedRPKI Valid217.79.116.0
- 217.79.117.0/24AS212238Datacamp LimitedRPKI Valid217.79.117.0
- 217.79.118.0/24AS212238Datacamp LimitedRPKI Valid217.79.118.0
- 217.79.119.0/24AS212238Datacamp LimitedRPKI Valid217.79.119.0
- 217.79.120.0/24AS147281Luckynet9 Private LimitedRPKI Valid217.79.120.0
- 217.79.121.0/24AS219363UAB OrlivaRPKI Valid217.79.121.0
- 217.79.122.0/24AS199741TransitX LtdRPKI Valid217.79.122.0
- 217.79.125.0/24AS26042FiberState, LLCRPKI Valid217.79.125.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.