BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
77.93.128.0/19
Announced exactly
- 77.93.128.0/19AS8851EDGE ta GCI ComRPKI Valid77.93.128.0
- Registry
- RIPE NCC · United Kingdom · May 18, 2007
- Delegated block
- 77.93.128.0 – 77.93.159.255
Covering routes
No less-specific route covers it.
More-specific routes
- 77.93.128.0/24AS8851EDGE ta GCI ComRPKI Valid77.93.128.0
- 77.93.131.0/24AS8851EDGE ta GCI ComRPKI Valid77.93.131.0
- 77.93.132.0/22AS8851EDGE ta GCI ComRPKI Valid77.93.132.0
- 77.93.133.0/24AS140641YOTTA YOTTA NETWORK SERVICES PRIVATE LIMITEDRPKI Valid77.93.133.0
- 77.93.137.0/24AS16509Amazon.com, Inc.RPKI Valid77.93.137.0
- 77.93.138.0/24AS197223WEDROPCODE-ASRPKI Valid77.93.138.0
- 77.93.139.0/24AS5511OPENTRANSITRPKI Valid77.93.139.0
- 77.93.141.0/24AS205021SHIFTEK-HOSTINGRPKI Valid77.93.141.0
- 77.93.142.0/24AS54252Sprious LLCRPKI Valid77.93.142.0
- 77.93.143.0/24AS21339CONTINGENCYNETWORKSRPKI Valid77.93.143.0
- 77.93.144.0/21AS8851EDGE ta GCI ComRPKI Valid77.93.144.0
- 77.93.148.0/24AS219450VOYARRPKI Valid77.93.148.0
- 77.93.149.0/24AS16509Amazon.com, Inc.RPKI Valid77.93.149.0
- 77.93.152.0/22AS401479Database Mart LLCRPKI Valid77.93.152.0
- 77.93.152.0/24AS401479Database Mart LLCRPKI Valid77.93.152.0
- 77.93.153.0/24AS401479Database Mart LLCRPKI Valid77.93.153.0
- 77.93.154.0/24AS401479Database Mart LLCRPKI Valid77.93.154.0
- 77.93.155.0/24AS401479Database Mart LLCRPKI Valid77.93.155.0
- 77.93.156.0/23AS8851EDGE ta GCI ComRPKI Valid77.93.156.0
- 77.93.157.0/24AS212336BYTEVIRTLLCRPKI Valid77.93.157.0
- 77.93.158.0/24AS214271QTNETWORKRPKI Valid77.93.158.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 193.166.0.0/15. 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.