BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
175.200.0.0/13
Announced exactly
- 175.200.0.0/13AS4766Korea TelecomRPKI Not found175.200.0.0
- Registry
- APNIC · South Korea · Jan 27, 2010
- Delegated block
- 175.192.0.0 – 175.255.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 175.200.11.0/24AS4793Hyundai Heavy IndustriesRPKI Not found175.200.11.0
- 175.200.11.0/25AS4793Hyundai Heavy IndustriesRPKI Not found175.200.11.0
- 175.200.11.128/25AS4793Hyundai Heavy IndustriesRPKI Not found175.200.11.128
- 175.200.12.0/24AS4793Hyundai Heavy IndustriesRPKI Not found175.200.12.0
- 175.200.12.0/25AS4793Hyundai Heavy IndustriesRPKI Not found175.200.12.0
- 175.200.12.128/25AS4793Hyundai Heavy IndustriesRPKI Not found175.200.12.128
- 175.202.181.0/24AS4766Korea TelecomRPKI Not found175.202.181.0
- 175.202.182.0/24AS4766Korea TelecomRPKI Not found175.202.182.0
- 175.202.208.0/24AS18305POSCO DXRPKI Not found175.202.208.0
- 175.202.211.0/24AS18305POSCO DXRPKI Not found175.202.211.0
- 175.202.212.0/24AS18305POSCO DXRPKI Not found175.202.212.0
- 175.202.213.0/24AS18305POSCO DXRPKI Not found175.202.213.0
- 175.204.143.0/24AS55625Chungwoon UniversityRPKI Not found175.204.143.0
- 175.204.144.0/23AS55625Chungwoon UniversityRPKI Not found175.204.144.0
- 175.204.240.0/22AS38105SOON CHUN HYANG UNIVERSITYRPKI Not found175.204.240.0
- 175.204.244.0/24AS38105SOON CHUN HYANG UNIVERSITYRPKI Not found175.204.244.0
- 175.205.105.0/24AS4766Korea TelecomRPKI Not found175.205.105.0
- 175.206.170.0/24AS55615DOUZONEBIZONRPKI Not found175.206.170.0
- 175.206.172.0/24AS55615DOUZONEBIZONRPKI Not found175.206.172.0
- 175.207.5.0/24AS55593netmarbleRPKI Not found175.207.5.0
- 175.207.6.0/24AS55593netmarbleRPKI Not found175.207.6.0
- 175.207.16.0/24AS55593netmarbleRPKI Not found175.207.16.0
- 175.207.17.0/24AS55593netmarbleRPKI Not found175.207.17.0
- 175.207.18.0/24AS55593netmarbleRPKI Not found175.207.18.0
- 175.207.32.0/22AS4766Korea TelecomRPKI Not found175.207.32.0
- 175.207.36.0/23AS4766Korea TelecomRPKI Not found175.207.36.0
- 175.207.38.0/24AS38676flexnetworksRPKI Not found175.207.38.0
- 175.207.39.0/24AS38676flexnetworksRPKI Not found175.207.39.0
- 175.207.71.0/24AS45376HL Holdings CorporationRPKI Not found175.207.71.0
- 175.207.72.0/24AS45376HL Holdings CorporationRPKI Not found175.207.72.0
- 175.207.73.0/24AS45376HL Holdings CorporationRPKI Not found175.207.73.0
- 175.207.74.0/24AS45376HL Holdings CorporationRPKI Not found175.207.74.0
- 175.207.76.0/24AS45376HL Holdings CorporationRPKI Not found175.207.76.0
- 175.207.77.0/24AS45376HL Holdings CorporationRPKI Not found175.207.77.0
- 175.207.78.0/24AS45376HL Holdings CorporationRPKI Not found175.207.78.0
- 175.207.79.0/24AS4766Korea TelecomRPKI Not found175.207.79.0
- 175.207.86.0/24AS131850Hana Insurance Co., Ltd.RPKI Not found175.207.86.0
- 175.207.87.0/24AS131851Hana Insurance Co., Ltd.RPKI Not found175.207.87.0
- 175.207.91.128/25AS38701Piranha SystemsRPKI Not found175.207.91.128
- 175.207.98.0/23AS4766Korea TelecomRPKI Not found175.207.98.0
- 175.207.140.0/24AS38701Piranha SystemsRPKI Not found175.207.140.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.