BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
82.119.64.0/19
Announced exactly
- 82.119.64.0/19AS8262Evolink EADRPKI Valid82.119.64.0
- Registry
- RIPE NCC · Bulgaria · Feb 16, 2004
- Delegated block
- 82.119.64.0 – 82.119.95.255
Covering routes
No less-specific route covers it.
More-specific routes
- 82.119.68.0/24AS8262Evolink EADRPKI Valid82.119.68.0
- 82.119.69.0/24AS8262Evolink EADRPKI Valid82.119.69.0
- 82.119.70.0/24AS61082Ministerstvo na Truda i Socialnata PolitikaRPKI Valid82.119.70.0
- 82.119.71.0/24AS211545Prodigy LTDRPKI Valid82.119.71.0
- 82.119.72.0/24AS218676EnduroSat EADRPKI Valid82.119.72.0
- 82.119.77.0/24AS43723Computernet Services Ltd.RPKI Valid82.119.77.0
- 82.119.78.0/24AS43732TBI BANK EADRPKI Valid82.119.78.0
- 82.119.80.0/21AS8262Evolink EADRPKI Valid82.119.80.0
- 82.119.81.0/24AS197741Icard Services PLCRPKI Valid82.119.81.0
- 82.119.82.0/24AS39483OSCEOLA EOODRPKI Valid82.119.82.0
- 82.119.83.0/24AS8262Evolink EADRPKI Valid82.119.83.0
- 82.119.84.0/24AS8262Evolink EADRPKI Valid82.119.84.0
- 82.119.87.0/24AS57912Asyst EOODRPKI Valid82.119.87.0
- 82.119.88.0/23AS197184Orbital LtdRPKI Valid82.119.88.0
- 82.119.91.0/24AS49704PETASCALE SUPERCOMPUTER CONSORTIUM - BULGARIA - DZZDRPKI Valid82.119.91.0
- 82.119.93.0/24AS34376Telecom Group LtdRPKI Valid82.119.93.0
- 82.119.94.0/24AS8262Evolink EADRPKI Valid82.119.94.0
- 82.119.95.0/24AS205874Zero Byte LtdRPKI Valid82.119.95.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.