BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
90.154.128.0/17
Announced exactly
- 90.154.128.0/17AS8866Vivacom Bulgaria EADRPKI Valid90.154.128.0
- Registry
- RIPE NCC · Bulgaria · Nov 13, 2006
- Delegated block
- 90.154.128.0 – 90.154.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 90.154.128.0/21AS8866Vivacom Bulgaria EADRPKI Valid90.154.128.0
- 90.154.136.0/21AS8866Vivacom Bulgaria EADRPKI Valid90.154.136.0
- 90.154.152.0/22AS34295Geo BG Net SPLtd.RPKI Valid90.154.152.0
- 90.154.152.0/24AS34295Geo BG Net SPLtd.RPKI Valid90.154.152.0
- 90.154.153.0/24AS34295Geo BG Net SPLtd.RPKI Valid90.154.153.0
- 90.154.154.0/24AS34295Geo BG Net SPLtd.RPKI Valid90.154.154.0
- 90.154.155.0/24AS34295Geo BG Net SPLtd.RPKI Valid90.154.155.0
- 90.154.168.0/21AS8866Vivacom Bulgaria EADRPKI Valid90.154.168.0
- 90.154.188.0/22AS8866Vivacom Bulgaria EADRPKI Valid90.154.188.0
- 90.154.193.0/24AS8866Vivacom Bulgaria EADRPKI Valid90.154.193.0
- 90.154.194.0/23AS8866Vivacom Bulgaria EADRPKI Valid90.154.194.0
- 90.154.196.0/22AS8866Vivacom Bulgaria EADRPKI Valid90.154.196.0
- 90.154.201.0/24AS8866Vivacom Bulgaria EADRPKI Valid90.154.201.0
- 90.154.202.0/23AS8866Vivacom Bulgaria EADRPKI Valid90.154.202.0
- 90.154.204.0/22AS8866Vivacom Bulgaria EADRPKI Valid90.154.204.0
- 90.154.209.0/24AS8866Vivacom Bulgaria EADRPKI Valid90.154.209.0
- 90.154.210.0/23AS8866Vivacom Bulgaria EADRPKI Valid90.154.210.0
- 90.154.212.0/22AS8866Vivacom Bulgaria EADRPKI Valid90.154.212.0
- 90.154.217.0/24AS8866Vivacom Bulgaria EADRPKI Valid90.154.217.0
- 90.154.218.0/23AS8866Vivacom Bulgaria EADRPKI Valid90.154.218.0
- 90.154.220.0/22AS8866Vivacom Bulgaria EADRPKI Valid90.154.220.0
- 90.154.224.0/24AS59620Global Electronic Solutions LTD.RPKI Valid90.154.224.0
- 90.154.225.0/24AS25374ESCOM Ltd. - HaskovoRPKI Valid90.154.225.0
- 90.154.229.0/24AS8866Vivacom Bulgaria EADRPKI Valid90.154.229.0
- 90.154.230.0/23AS8866Vivacom Bulgaria EADRPKI Valid90.154.230.0
- 90.154.232.0/24AS60560MEDICAL UNIVERSITY - VARNA Prof. Dr. Paraskev StoyanovRPKI Valid90.154.232.0
- 90.154.234.0/24AS8866Vivacom Bulgaria EADRPKI Valid90.154.234.0
- 90.154.235.0/24AS8866Vivacom Bulgaria EADRPKI Valid90.154.235.0
- 90.154.236.0/24AS60560MEDICAL UNIVERSITY - VARNA Prof. Dr. Paraskev StoyanovRPKI Valid90.154.236.0
- 90.154.237.0/24AS60560MEDICAL UNIVERSITY - VARNA Prof. Dr. Paraskev StoyanovRPKI Valid90.154.237.0
- 90.154.238.0/23AS8866Vivacom Bulgaria EADRPKI Valid90.154.238.0
- 90.154.240.0/21AS8866Vivacom Bulgaria EADRPKI Valid90.154.240.0
- 90.154.248.0/22AS8866Vivacom Bulgaria EADRPKI Valid90.154.248.0
- 90.154.252.0/23AS8866Vivacom Bulgaria EADRPKI Valid90.154.252.0
- 90.154.254.0/24AS8866Vivacom Bulgaria EADRPKI Valid90.154.254.0
- 90.154.255.0/24AS8866Vivacom Bulgaria EADRPKI Valid90.154.255.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.