BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
96.9.192.0/18
Announced exactly
- 96.9.192.0/18AS20278Nexeon Technologies, Inc.RPKI Not found96.9.192.0
- Registry
- ARIN · United States · Mar 10, 2015
- Delegated block
- 96.9.192.0 – 96.9.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 96.9.208.0/23AS20278Nexeon Technologies, Inc.RPKI Not found96.9.208.0
- 96.9.210.0/24AS59253LEASEWEB SINGAPORE PTE. LTD.RPKI Valid96.9.210.0
- 96.9.211.0/24AS8888xTom Pty LtdRPKI Valid96.9.211.0
- 96.9.212.0/24AS8888xTom Pty LtdRPKI Valid96.9.212.0
- 96.9.213.0/24AS8888xTom Pty LtdRPKI Valid96.9.213.0
- 96.9.214.0/23AS199741TransitX LtdRPKI Valid96.9.214.0
- 96.9.220.0/24AS20278Nexeon Technologies, Inc.RPKI Not found96.9.220.0
- 96.9.221.0/24AS16509Amazon.com, Inc.RPKI Valid96.9.221.0
- 96.9.222.0/24AS20278Nexeon Technologies, Inc.RPKI Not found96.9.222.0
- 96.9.223.0/24AS20278Nexeon Technologies, Inc.RPKI Not found96.9.223.0
- 96.9.225.0/24AS18450WebNX, Inc.RPKI Valid96.9.225.0
- 96.9.226.0/24AS32489Amanah Tech Inc.RPKI Not found96.9.226.0
- 96.9.228.0/23AS133752LEASEWEB HONG KONG LIMITEDRPKI Valid96.9.228.0
- 96.9.230.0/24AS20278Nexeon Technologies, Inc.RPKI Not found96.9.230.0
- 96.9.231.0/24AS8888xTom Pty LtdRPKI Valid96.9.231.0
- 96.9.240.0/20AS20278Nexeon Technologies, Inc.RPKI Valid96.9.240.0
- 96.9.240.0/24AS20278Nexeon Technologies, Inc.RPKI Valid96.9.240.0
- 96.9.241.0/24AS20278Nexeon Technologies, Inc.RPKI Valid96.9.241.0
- 96.9.242.0/24AS20278Nexeon Technologies, Inc.RPKI Valid96.9.242.0
- 96.9.243.0/24AS20278Nexeon Technologies, Inc.RPKI Valid96.9.243.0
- 96.9.244.0/24AS20278Nexeon Technologies, Inc.RPKI Valid96.9.244.0
- 96.9.245.0/24AS20278Nexeon Technologies, Inc.RPKI Valid96.9.245.0
- 96.9.246.0/24AS20278Nexeon Technologies, Inc.RPKI Valid96.9.246.0
- 96.9.247.0/24AS20278Nexeon Technologies, Inc.RPKI Valid96.9.247.0
- 96.9.248.0/24AS20278Nexeon Technologies, Inc.RPKI Valid96.9.248.0
- 96.9.249.0/24AS20278Nexeon Technologies, Inc.RPKI Valid96.9.249.0
- 96.9.250.0/24AS20278Nexeon Technologies, Inc.RPKI Valid96.9.250.0
- 96.9.251.0/24AS20278Nexeon Technologies, Inc.RPKI Valid96.9.251.0
- 96.9.252.0/24AS20278Nexeon Technologies, Inc.RPKI Valid96.9.252.0
- 96.9.253.0/24AS20278Nexeon Technologies, Inc.RPKI Valid96.9.253.0
- 96.9.254.0/24AS20278Nexeon Technologies, Inc.RPKI Valid96.9.254.0
- 96.9.255.0/24AS20278Nexeon Technologies, Inc.RPKI Valid96.9.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.