BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
5.53.128.0/17
Announced exactly
- 5.53.128.0/17AS8717A1 Bulgaria EADRPKI Valid5.53.128.0
- Registry
- RIPE NCC · Bulgaria · May 29, 2012
- Delegated block
- 5.53.128.0 – 5.53.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 5.53.128.0/21AS13124A1 Bulgaria EADRPKI Valid5.53.128.0
- 5.53.136.0/22AS13124A1 Bulgaria EADRPKI Valid5.53.136.0
- 5.53.140.0/22AS13124A1 Bulgaria EADRPKI Valid5.53.140.0
- 5.53.144.0/21AS13124A1 Bulgaria EADRPKI Valid5.53.144.0
- 5.53.152.0/21AS13124A1 Bulgaria EADRPKI Valid5.53.152.0
- 5.53.160.0/21AS13124A1 Bulgaria EADRPKI Valid5.53.160.0
- 5.53.168.0/21AS13124A1 Bulgaria EADRPKI Valid5.53.168.0
- 5.53.177.0/24AS13124A1 Bulgaria EADRPKI Valid5.53.177.0
- 5.53.178.0/24AS13124A1 Bulgaria EADRPKI Valid5.53.178.0
- 5.53.179.0/24AS13124A1 Bulgaria EADRPKI Valid5.53.179.0
- 5.53.184.0/24AS13124A1 Bulgaria EADRPKI Valid5.53.184.0
- 5.53.185.0/24AS13124A1 Bulgaria EADRPKI Valid5.53.185.0
- 5.53.186.0/24AS13124A1 Bulgaria EADRPKI Valid5.53.186.0
- 5.53.187.0/24AS13124A1 Bulgaria EADRPKI Valid5.53.187.0
- 5.53.188.0/24AS13124A1 Bulgaria EADRPKI Valid5.53.188.0
- 5.53.189.0/24AS13124A1 Bulgaria EADRPKI Valid5.53.189.0
- 5.53.190.0/24AS13124A1 Bulgaria EADRPKI Valid5.53.190.0
- 5.53.191.0/24AS13124A1 Bulgaria EADRPKI Valid5.53.191.0
- 5.53.192.0/19AS13124A1 Bulgaria EADRPKI Valid5.53.192.0
- 5.53.192.0/22AS13124A1 Bulgaria EADRPKI Valid5.53.192.0
- 5.53.196.0/22AS13124A1 Bulgaria EADRPKI Valid5.53.196.0
- 5.53.200.0/22AS13124A1 Bulgaria EADRPKI Valid5.53.200.0
- 5.53.204.0/22AS13124A1 Bulgaria EADRPKI Valid5.53.204.0
- 5.53.208.0/21AS13124A1 Bulgaria EADRPKI Valid5.53.208.0
- 5.53.216.0/22AS13124A1 Bulgaria EADRPKI Valid5.53.216.0
- 5.53.222.0/23AS13124A1 Bulgaria EADRPKI Valid5.53.222.0
- 5.53.224.0/21AS13124A1 Bulgaria EADRPKI Valid5.53.224.0
- 5.53.224.0/23AS13124A1 Bulgaria EADRPKI Valid5.53.224.0
- 5.53.226.0/23AS13124A1 Bulgaria EADRPKI Valid5.53.226.0
- 5.53.228.0/23AS13124A1 Bulgaria EADRPKI Valid5.53.228.0
- 5.53.230.0/23AS13124A1 Bulgaria EADRPKI Valid5.53.230.0
- 5.53.232.0/23AS13124A1 Bulgaria EADRPKI Valid5.53.232.0
- 5.53.234.0/24AS13124A1 Bulgaria EADRPKI Valid5.53.234.0
- 5.53.235.0/24AS13124A1 Bulgaria EADRPKI Valid5.53.235.0
- 5.53.236.0/24AS13124A1 Bulgaria EADRPKI Valid5.53.236.0
- 5.53.237.0/24AS13124A1 Bulgaria EADRPKI Valid5.53.237.0
- 5.53.238.0/24AS13124A1 Bulgaria EADRPKI Valid5.53.238.0
- 5.53.240.0/24AS29580A1 Bulgaria EADRPKI Valid5.53.240.0
- 5.53.241.0/24AS29580A1 Bulgaria EADRPKI Valid5.53.241.0
- 5.53.242.0/24AS29580A1 Bulgaria EADRPKI Valid5.53.242.0
- 5.53.243.0/24AS29580A1 Bulgaria EADRPKI Valid5.53.243.0
- 5.53.244.0/24AS29580A1 Bulgaria EADRPKI Valid5.53.244.0
- 5.53.245.0/24AS29580A1 Bulgaria EADRPKI Valid5.53.245.0
- 5.53.246.0/24AS29580A1 Bulgaria EADRPKI Valid5.53.246.0
- 5.53.247.0/24AS29580A1 Bulgaria EADRPKI Valid5.53.247.0
- 5.53.248.0/23AS13124A1 Bulgaria EADRPKI Valid5.53.248.0
- 5.53.250.0/23AS13124A1 Bulgaria EADRPKI Valid5.53.250.0
- 5.53.252.0/22AS13124A1 Bulgaria EADRPKI Valid5.53.252.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.