BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
92.253.128.0/17
Announced exactly
- 92.253.128.0/17AS44546ALFA TELECOM s.r.o.RPKI Valid92.253.128.0
- Registry
- RIPE NCC · Czechia · Dec 3, 2007
- Delegated block
- 92.253.128.0 – 92.253.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 92.253.192.0/22AS207154PE Luseya PlyusRPKI Valid92.253.192.0
- 92.253.196.0/22AS43533OOO "Gals Telecom"RPKI Valid92.253.196.0
- 92.253.200.0/24AS209067Digital Access Network LLCRPKI Valid92.253.200.0
- 92.253.202.0/24AS211433Silver Telecom Ltd.RPKI Valid92.253.202.0
- 92.253.203.0/24AS60612Albatros Ltd.RPKI Valid92.253.203.0
- 92.253.204.0/24AS204889Online Business Technologies Ltd.RPKI Valid92.253.204.0
- 92.253.205.0/24AS209213Eso-Autotechnics Ltd.RPKI Valid92.253.205.0
- 92.253.206.0/23AS209248Interset Ltd.RPKI Valid92.253.206.0
- 92.253.208.0/24AS198803Alonstelefonstroy LLPRPKI Valid92.253.208.0
- 92.253.209.0/24AS198803Alonstelefonstroy LLPRPKI Valid92.253.209.0
- 92.253.211.0/24AS198803Alonstelefonstroy LLPRPKI Valid92.253.211.0
- 92.253.212.0/22AS59577LinkCom Networks LLCRPKI Valid92.253.212.0
- 92.253.216.0/23AS51812KTVS Ltd.RPKI Valid92.253.216.0
- 92.253.218.0/23AS207676Best Line Ltd.RPKI Valid92.253.218.0
- 92.253.219.0/24AS207676Best Line Ltd.RPKI Valid92.253.219.0
- 92.253.232.0/24AS215349ITUslugi SPB LLCRPKI Valid92.253.232.0
- 92.253.233.0/24AS209229TELEVISION COMPANY "RAI" LLCRPKI Valid92.253.233.0
- 92.253.234.0/24AS207677Volkov PavelRPKI Valid92.253.234.0
- 92.253.235.0/24AS207676Best Line Ltd.RPKI Valid92.253.235.0
- 92.253.236.0/22AS59577LinkCom Networks LLCRPKI Valid92.253.236.0
- 92.253.240.0/20AS41575Intercity Ltd.RPKI Valid92.253.240.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.