BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
203.127.0.0/16
Announced exactly
- 203.127.0.0/16AS3758SingNetRPKI Valid203.127.0.0
- Registry
- APNIC · Singapore · Oct 22, 1997
- Delegated block
- 203.127.0.0 – 203.127.63.255
Covering routes
No less-specific route covers it.
More-specific routes
- 203.127.3.0/24AS9255Singapore TelecomRPKI Valid203.127.3.0
- 203.127.10.0/24AS9255Singapore TelecomRPKI Valid203.127.10.0
- 203.127.16.0/24AS3758SingNetRPKI Valid203.127.16.0
- 203.127.23.0/24AS3758SingNetRPKI Valid203.127.23.0
- 203.127.29.0/24AS3758SingNetRPKI Valid203.127.29.0
- 203.127.31.0/24AS9255Singapore TelecomRPKI Valid203.127.31.0
- 203.127.53.0/24AS3758SingNetRPKI Valid203.127.53.0
- 203.127.61.0/24AS3758SingNetRPKI Valid203.127.61.0
- 203.127.80.0/24AS3758SingNetRPKI Valid203.127.80.0
- 203.127.86.0/24AS3758SingNetRPKI Valid203.127.86.0
- 203.127.89.0/24AS3758SingNetRPKI Valid203.127.89.0
- 203.127.96.0/24AS3758SingNetRPKI Valid203.127.96.0
- 203.127.102.0/24AS3758SingNetRPKI Valid203.127.102.0
- 203.127.104.0/24AS9255Singapore TelecomRPKI Valid203.127.104.0
- 203.127.108.0/24AS7473Singapore Telecommunications LtdRPKI Valid203.127.108.0
- 203.127.110.0/24AS3758SingNetRPKI Valid203.127.110.0
- 203.127.140.0/24AS3758SingNetRPKI Valid203.127.140.0
- 203.127.146.0/24AS3758SingNetRPKI Valid203.127.146.0
- 203.127.181.0/24AS9255Singapore TelecomRPKI Valid203.127.181.0
- 203.127.201.0/24AS9255Singapore TelecomRPKI Valid203.127.201.0
- 203.127.202.0/24AS9255Singapore TelecomRPKI Valid203.127.202.0
- 203.127.206.0/24AS9890ATOS Information Technology (Singapore) Pte LtdRPKI Valid203.127.206.0
- 203.127.211.0/24AS3758SingNetRPKI Valid203.127.211.0
- 203.127.217.0/24AS3758SingNetRPKI Valid203.127.217.0
- 203.127.223.0/24AS3758SingNetRPKI Valid203.127.223.0
- 203.127.232.0/24AS3758SingNetRPKI Valid203.127.232.0
- 203.127.235.0/24AS3758SingNetRPKI Valid203.127.235.0
- 203.127.240.0/20AS3758SingNetRPKI Valid203.127.240.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.