BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
202.123.128.0/19
Announced exactly
- 202.123.128.0/19AS7131PTI Pacifica Inc.RPKI Valid202.123.128.0
- Registry
- APNIC · Guam · Aug 2, 2000
- Delegated block
- 202.123.128.0 – 202.123.159.255
Covering routes
No less-specific route covers it.
More-specific routes
- 202.123.128.0/24AS7131PTI Pacifica Inc.RPKI Valid202.123.128.0
- 202.123.129.0/24AS7131PTI Pacifica Inc.RPKI Valid202.123.129.0
- 202.123.130.0/24AS7131PTI Pacifica Inc.RPKI Valid202.123.130.0
- 202.123.131.0/24AS7131PTI Pacifica Inc.RPKI Valid202.123.131.0
- 202.123.132.0/24AS7131PTI Pacifica Inc.RPKI Valid202.123.132.0
- 202.123.133.0/24AS7131PTI Pacifica Inc.RPKI Valid202.123.133.0
- 202.123.134.0/24AS7131PTI Pacifica Inc.RPKI Valid202.123.134.0
- 202.123.135.0/24AS7131PTI Pacifica Inc.RPKI Valid202.123.135.0
- 202.123.136.0/24AS7131PTI Pacifica Inc.RPKI Valid202.123.136.0
- 202.123.137.0/24AS7131PTI Pacifica Inc.RPKI Valid202.123.137.0
- 202.123.138.0/24AS7131PTI Pacifica Inc.RPKI Valid202.123.138.0
- 202.123.141.0/24AS7131PTI Pacifica Inc.RPKI Valid202.123.141.0
- 202.123.142.0/24AS7131PTI Pacifica Inc.RPKI Valid202.123.142.0
- 202.123.143.0/24AS7131PTI Pacifica Inc.RPKI Valid202.123.143.0
- 202.123.144.0/24AS7131PTI Pacifica Inc.RPKI Valid202.123.144.0
- 202.123.147.0/24AS7131PTI Pacifica Inc.RPKI Valid202.123.147.0
- 202.123.148.0/24AS7131PTI Pacifica Inc.RPKI Valid202.123.148.0
- 202.123.149.0/24AS7131PTI Pacifica Inc.RPKI Valid202.123.149.0
- 202.123.150.0/24AS7131PTI Pacifica Inc.RPKI Valid202.123.150.0
- 202.123.151.0/24AS7131PTI Pacifica Inc.RPKI Valid202.123.151.0
- 202.123.152.0/24AS7131PTI Pacifica Inc.RPKI Valid202.123.152.0
- 202.123.153.0/24AS7131PTI Pacifica Inc.RPKI Valid202.123.153.0
- 202.123.154.0/24AS7131PTI Pacifica Inc.RPKI Valid202.123.154.0
- 202.123.155.0/24AS7131PTI Pacifica Inc.RPKI Valid202.123.155.0
- 202.123.156.0/24AS7131PTI Pacifica Inc.RPKI Valid202.123.156.0
- 202.123.157.0/24AS7131PTI Pacifica Inc.RPKI Valid202.123.157.0
- 202.123.158.0/24AS7131PTI Pacifica Inc.RPKI Valid202.123.158.0
- 202.123.159.0/24AS7131PTI Pacifica Inc.RPKI Valid202.123.159.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.