BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
210.104.0.0/16
Announced exactly
- 210.104.0.0/16AS4766Korea TelecomRPKI Not found210.104.0.0
- Registry
- APNIC · South Korea · Aug 29, 1997
- Delegated block
- 210.104.0.0 – 210.105.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 210.104.8.0/24AS45400Korea TelecomRPKI Not found210.104.8.0
- 210.104.9.0/24AS45400Korea TelecomRPKI Not found210.104.9.0
- 210.104.10.0/24AS45400Korea TelecomRPKI Not found210.104.10.0
- 210.104.11.0/24AS45400Korea TelecomRPKI Not found210.104.11.0
- 210.104.12.0/24AS45400Korea TelecomRPKI Not found210.104.12.0
- 210.104.13.0/24AS45400Korea TelecomRPKI Not found210.104.13.0
- 210.104.14.0/24AS45400Korea TelecomRPKI Not found210.104.14.0
- 210.104.15.0/24AS45400Korea TelecomRPKI Not found210.104.15.0
- 210.104.20.0/24AS45400Korea TelecomRPKI Not found210.104.20.0
- 210.104.21.0/24AS9683Seoul Facilities CorporationRPKI Not found210.104.21.0
- 210.104.22.0/24AS45400Korea TelecomRPKI Not found210.104.22.0
- 210.104.24.0/24AS131846GYEONGGI-DO FIRE SERVICESRPKI Not found210.104.24.0
- 210.104.24.0/25AS131846GYEONGGI-DO FIRE SERVICESRPKI Not found210.104.24.0
- 210.104.26.0/24AS45400Korea TelecomRPKI Not found210.104.26.0
- 210.104.27.0/24AS45400Korea TelecomRPKI Not found210.104.27.0
- 210.104.28.0/24AS45400Korea TelecomRPKI Not found210.104.28.0
- 210.104.32.0/24AS4766Korea TelecomRPKI Not found210.104.32.0
- 210.104.33.0/24AS4766Korea TelecomRPKI Not found210.104.33.0
- 210.104.34.0/24AS4766Korea TelecomRPKI Not found210.104.34.0
- 210.104.39.0/24AS4766Korea TelecomRPKI Not found210.104.39.0
- 210.104.41.0/24AS17841NATIONAL INFORMATION RESOURCES SERVICERPKI Not found210.104.41.0
- 210.104.44.0/24AS45400Korea TelecomRPKI Not found210.104.44.0
- 210.104.48.0/20AS4766Korea TelecomRPKI Not found210.104.48.0
- 210.104.57.0/24AS4766Korea TelecomRPKI Not found210.104.57.0
- 210.104.58.0/23AS4766Korea TelecomRPKI Not found210.104.58.0
- 210.104.80.0/24AS4766Korea TelecomRPKI Not found210.104.80.0
- 210.104.100.128/25AS9647Seoul Metropolitan GovernmentRPKI Not found210.104.100.128
- 210.104.102.0/24AS45400Korea TelecomRPKI Not found210.104.102.0
- 210.104.103.0/24AS9647Seoul Metropolitan GovernmentRPKI Not found210.104.103.0
- 210.104.112.0/24AS55633pundang jesaeng general hospitalRPKI Not found210.104.112.0
- 210.104.123.0/24AS45400Korea TelecomRPKI Not found210.104.123.0
- 210.104.126.0/24AS9647Seoul Metropolitan GovernmentRPKI Not found210.104.126.0
- 210.104.128.0/24AS9647Seoul Metropolitan GovernmentRPKI Not found210.104.128.0
- 210.104.129.0/24AS9647Seoul Metropolitan GovernmentRPKI Not found210.104.129.0
- 210.104.132.0/24AS10170The Bank of KoreaRPKI Not found210.104.132.0
- 210.104.133.0/24AS10170The Bank of KoreaRPKI Not found210.104.133.0
- 210.104.138.0/24AS45400Korea TelecomRPKI Not found210.104.138.0
- 210.104.140.0/24AS17841NATIONAL INFORMATION RESOURCES SERVICERPKI Not found210.104.140.0
- 210.104.148.0/24AS17841NATIONAL INFORMATION RESOURCES SERVICERPKI Not found210.104.148.0
- 210.104.156.0/24AS131870KSPORPKI Not found210.104.156.0
- 210.104.157.0/24AS131870KSPORPKI Not found210.104.157.0
- 210.104.158.0/24AS131870KSPORPKI Not found210.104.158.0
- 210.104.203.0/24AS17584Inchon Metropolitan Office Of EducationRPKI Not found210.104.203.0
- 210.104.218.0/24AS45400Korea TelecomRPKI Not found210.104.218.0
- 210.104.237.0/24AS45400Korea TelecomRPKI Not found210.104.237.0
- 210.104.239.0/24AS4766Korea TelecomRPKI Not found210.104.239.0
- 210.104.243.0/25AS45400Korea TelecomRPKI Not found210.104.243.0
- 210.104.249.0/24AS17841NATIONAL INFORMATION RESOURCES SERVICERPKI Not found210.104.249.0
- 210.104.250.0/24AS17841NATIONAL INFORMATION RESOURCES SERVICERPKI Not found210.104.250.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.