BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
165.21.0.0/16
Announced exactly
- 165.21.0.0/16AS3758SingNetRPKI Valid165.21.0.0
- Registry
- APNIC · Singapore · Mar 31, 1993
- Delegated block
- 165.21.0.0 – 165.21.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 165.21.18.0/24AS3758SingNetRPKI Valid165.21.18.0
- 165.21.19.0/24AS3758SingNetRPKI Valid165.21.19.0
- 165.21.24.0/21AS9506Singtel Fibre BroadbandRPKI Valid165.21.24.0
- 165.21.24.0/22AS9506Singtel Fibre BroadbandRPKI Valid165.21.24.0
- 165.21.28.0/23AS9506Singtel Fibre BroadbandRPKI Valid165.21.28.0
- 165.21.31.0/24AS3758SingNetRPKI Valid165.21.31.0
- 165.21.36.0/23AS3758SingNetRPKI Valid165.21.36.0
- 165.21.49.0/24AS3758SingNetRPKI Valid165.21.49.0
- 165.21.50.0/24AS3758SingNetRPKI Valid165.21.50.0
- 165.21.64.0/22AS9506Singtel Fibre BroadbandRPKI Valid165.21.64.0
- 165.21.68.0/23AS9506Singtel Fibre BroadbandRPKI Valid165.21.68.0
- 165.21.70.0/24AS3758SingNetRPKI Valid165.21.70.0
- 165.21.71.0/24AS3758SingNetRPKI Valid165.21.71.0
- 165.21.72.0/24AS3758SingNetRPKI Valid165.21.72.0
- 165.21.75.0/24AS9506Singtel Fibre BroadbandRPKI Valid165.21.75.0
- 165.21.76.0/23AS9506Singtel Fibre BroadbandRPKI Valid165.21.76.0
- 165.21.78.0/24AS9506Singtel Fibre BroadbandRPKI Valid165.21.78.0
- 165.21.88.0/24AS3758SingNetRPKI Valid165.21.88.0
- 165.21.91.0/24AS3758SingNetRPKI Valid165.21.91.0
- 165.21.93.0/24AS3758SingNetRPKI Valid165.21.93.0
- 165.21.94.0/24AS3758SingNetRPKI Valid165.21.94.0
- 165.21.95.0/24AS3758SingNetRPKI Valid165.21.95.0
- 165.21.104.0/24AS3758SingNetRPKI Valid165.21.104.0
- 165.21.108.0/24AS3758SingNetRPKI Valid165.21.108.0
- 165.21.109.0/24AS3758SingNetRPKI Valid165.21.109.0
- 165.21.112.0/21AS9506Singtel Fibre BroadbandRPKI Valid165.21.112.0
- 165.21.122.0/24AS3758SingNetRPKI Valid165.21.122.0
- 165.21.123.0/24AS3758SingNetRPKI Valid165.21.123.0
- 165.21.124.0/22AS9506Singtel Fibre BroadbandRPKI Valid165.21.124.0
- 165.21.128.0/22AS9506Singtel Fibre BroadbandRPKI Valid165.21.128.0
- 165.21.134.0/24AS9506Singtel Fibre BroadbandRPKI Valid165.21.134.0
- 165.21.135.0/24AS9506Singtel Fibre BroadbandRPKI Valid165.21.135.0
- 165.21.154.0/24AS9506Singtel Fibre BroadbandRPKI Valid165.21.154.0
- 165.21.155.0/24AS9506Singtel Fibre BroadbandRPKI Valid165.21.155.0
- 165.21.238.0/24AS3758SingNetRPKI Valid165.21.238.0
- 165.21.244.0/24AS3758SingNetRPKI Valid165.21.244.0
- 165.21.246.0/24AS3758SingNetRPKI Valid165.21.246.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.