BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
203.126.0.0/16
Announced exactly
- 203.126.0.0/16AS3758SINGNET SingNetRPKI Valid203.126.0.0
- Registry
- APNIC · Singapore · Jul 13, 2000
- Delegated block
- 203.126.0.0 – 203.126.63.255
Covering routes
No less-specific route covers it.
More-specific routes
- 203.126.2.0/24AS3758SINGNET SingNetRPKI Valid203.126.2.0
- 203.126.4.0/24AS3758SINGNET SingNetRPKI Valid203.126.4.0
- 203.126.7.0/24AS3758SINGNET SingNetRPKI Valid203.126.7.0
- 203.126.8.0/24AS9255CONNECTPLUS-AS Singapore TelecomRPKI Valid203.126.8.0
- 203.126.11.0/24AS3758SINGNET SingNetRPKI Valid203.126.11.0
- 203.126.12.0/24AS152903PSACORPORATIONLTD-AS-AP PSA Corporation LtdRPKI Valid203.126.12.0
- 203.126.14.0/24AS3758SINGNET SingNetRPKI Valid203.126.14.0
- 203.126.19.0/24AS3758SINGNET SingNetRPKI Valid203.126.19.0
- 203.126.29.0/24AS3758SINGNET SingNetRPKI Valid203.126.29.0
- 203.126.43.0/24AS3758SINGNET SingNetRPKI Valid203.126.43.0
- 203.126.52.0/24AS3758SINGNET SingNetRPKI Valid203.126.52.0
- 203.126.54.0/24AS3758SINGNET SingNetRPKI Valid203.126.54.0
- 203.126.57.0/24AS3758SINGNET SingNetRPKI Valid203.126.57.0
- 203.126.60.0/24AS3758SINGNET SingNetRPKI Valid203.126.60.0
- 203.126.64.0/24AS6619SAMSUNGSDS-AS-KR SamsungSDS Inc.RPKI Valid203.126.64.0
- 203.126.80.0/24AS3758SINGNET SingNetRPKI Valid203.126.80.0
- 203.126.87.0/24AS3758SINGNET SingNetRPKI Valid203.126.87.0
- 203.126.92.0/24AS3758SINGNET SingNetRPKI Valid203.126.92.0
- 203.126.96.0/24AS3758SINGNET SingNetRPKI Valid203.126.96.0
- 203.126.110.0/24AS3758SINGNET SingNetRPKI Valid203.126.110.0
- 203.126.112.0/24AS3758SINGNET SingNetRPKI Valid203.126.112.0
- 203.126.114.0/24AS3758SINGNET SingNetRPKI Valid203.126.114.0
- 203.126.119.0/24AS3758SINGNET SingNetRPKI Valid203.126.119.0
- 203.126.130.0/24AS9255CONNECTPLUS-AS Singapore TelecomRPKI Valid203.126.130.0
- 203.126.133.0/24AS9255CONNECTPLUS-AS Singapore TelecomRPKI Valid203.126.133.0
- 203.126.134.0/24AS9255CONNECTPLUS-AS Singapore TelecomRPKI Valid203.126.134.0
- 203.126.138.0/24AS3758SINGNET SingNetRPKI Valid203.126.138.0
- 203.126.146.0/24AS3758SINGNET SingNetRPKI Valid203.126.146.0
- 203.126.147.0/24AS9255CONNECTPLUS-AS Singapore TelecomRPKI Valid203.126.147.0
- 203.126.151.0/24AS3758SINGNET SingNetRPKI Valid203.126.151.0
- 203.126.159.0/24AS3758SINGNET SingNetRPKI Valid203.126.159.0
- 203.126.163.0/24AS3758SINGNET SingNetRPKI Valid203.126.163.0
- 203.126.172.0/24AS3758SINGNET SingNetRPKI Valid203.126.172.0
- 203.126.178.0/24AS3758SINGNET SingNetRPKI Valid203.126.178.0
- 203.126.186.0/24AS3758SINGNET SingNetRPKI Valid203.126.186.0
- 203.126.189.0/24AS3758SINGNET SingNetRPKI Valid203.126.189.0
- 203.126.192.0/24AS3758SINGNET SingNetRPKI Valid203.126.192.0
- 203.126.194.0/24AS3758SINGNET SingNetRPKI Valid203.126.194.0
- 203.126.204.0/24AS3758SINGNET SingNetRPKI Valid203.126.204.0
- 203.126.216.0/24AS3758SINGNET SingNetRPKI Valid203.126.216.0
- 203.126.219.0/24AS3758SINGNET SingNetRPKI Valid203.126.219.0
- 203.126.228.0/24AS3758SINGNET SingNetRPKI Valid203.126.228.0
- 203.126.234.0/24AS3758SINGNET SingNetRPKI Valid203.126.234.0
- 203.126.238.0/24AS3758SINGNET SingNetRPKI Valid203.126.238.0
- 203.126.243.0/24AS3758SINGNET SingNetRPKI Valid203.126.243.0
- 203.126.247.0/24AS3758SINGNET SingNetRPKI Valid203.126.247.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.