BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
212.104.96.0/19
Announced exactly
- 212.104.96.0/19AS8717A1 Bulgaria EADRPKI Valid212.104.96.0
- Registry
- RIPE NCC · Bulgaria · Jul 9, 2003
- Delegated block
- 212.104.96.0 – 212.104.127.255
Covering routes
No less-specific route covers it.
More-specific routes
- 212.104.96.0/22AS13124A1 Bulgaria EADRPKI Valid212.104.96.0
- 212.104.100.0/23AS13124A1 Bulgaria EADRPKI Valid212.104.100.0
- 212.104.102.0/23AS13124A1 Bulgaria EADRPKI Valid212.104.102.0
- 212.104.104.0/22AS13124A1 Bulgaria EADRPKI Valid212.104.104.0
- 212.104.108.0/23AS13124A1 Bulgaria EADRPKI Valid212.104.108.0
- 212.104.112.0/24AS13124A1 Bulgaria EADRPKI Valid212.104.112.0
- 212.104.113.0/24AS13124A1 Bulgaria EADRPKI Valid212.104.113.0
- 212.104.114.0/24AS13124A1 Bulgaria EADRPKI Valid212.104.114.0
- 212.104.115.0/24AS13124A1 Bulgaria EADRPKI Valid212.104.115.0
- 212.104.116.0/22AS12716A1 Bulgaria EADRPKI Valid212.104.116.0
- 212.104.120.0/24AS13124A1 Bulgaria EADRPKI Valid212.104.120.0
- 212.104.121.0/24AS13124A1 Bulgaria EADRPKI Valid212.104.121.0
- 212.104.122.0/24AS13124A1 Bulgaria EADRPKI Valid212.104.122.0
- 212.104.123.0/24AS13124A1 Bulgaria EADRPKI Valid212.104.123.0
- 212.104.124.0/24AS13124A1 Bulgaria EADRPKI Valid212.104.124.0
- 212.104.125.0/24AS13124A1 Bulgaria EADRPKI Valid212.104.125.0
- 212.104.126.0/24AS13124A1 Bulgaria EADRPKI Valid212.104.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, 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.