BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
212.116.96.0/19
Announced exactly
- 212.116.96.0/19AS35000JSC "Severen-Telecom"RPKI Not found212.116.96.0
- Registry
- RIPE NCC · Russia · Jun 19, 2008
- Delegated block
- 212.116.96.0 – 212.116.127.255
Covering routes
No less-specific route covers it.
More-specific routes
- 212.116.96.0/23AS56669LLC Gazpromneft ITORPKI Not found212.116.96.0
- 212.116.98.0/23AS56669LLC Gazpromneft ITORPKI Not found212.116.98.0
- 212.116.112.0/24AS48096Enterprise Cloud Ltd.RPKI Not found212.116.112.0
- 212.116.115.0/24AS35278SPRINTHOST.RU LLCRPKI Not found212.116.115.0
- 212.116.116.0/24AS48308OOO TTCRPKI Not found212.116.116.0
- 212.116.117.0/24AS48308OOO TTCRPKI Not found212.116.117.0
- 212.116.118.0/24AS48308OOO TTCRPKI Not found212.116.118.0
- 212.116.119.0/24AS48308OOO TTCRPKI Not found212.116.119.0
- 212.116.120.0/24AS48096Enterprise Cloud Ltd.RPKI Not found212.116.120.0
- 212.116.121.0/24AS48096Enterprise Cloud Ltd.RPKI Not found212.116.121.0
- 212.116.122.0/24AS48096Enterprise Cloud Ltd.RPKI Not found212.116.122.0
- 212.116.123.0/24AS48096Enterprise Cloud Ltd.RPKI Not found212.116.123.0
- 212.116.124.0/23AS39853LLC Gazpromneft ITORPKI Not found212.116.124.0
- 212.116.126.0/23AS39853LLC Gazpromneft ITORPKI Not found212.116.126.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 62.103.0.0/16. 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.