BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
210.90.0.0/16
Announced exactly
- 210.90.0.0/16AS4766Korea TelecomRPKI Not found210.90.0.0
- Registry
- APNIC · South Korea · Mar 24, 1999
- Delegated block
- 210.90.0.0 – 210.91.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 210.90.0.0/24AS9647Seoul Metropolitan GovernmentRPKI Not found210.90.0.0
- 210.90.1.0/25AS9647Seoul Metropolitan GovernmentRPKI Not found210.90.1.0
- 210.90.6.0/24AS45400Korea TelecomRPKI Not found210.90.6.0
- 210.90.7.0/24AS4766Korea TelecomRPKI Not found210.90.7.0
- 210.90.8.0/24AS17841NATIONAL INFORMATION RESOURCES SERVICERPKI Not found210.90.8.0
- 210.90.9.0/25AS9647Seoul Metropolitan GovernmentRPKI Not found210.90.9.0
- 210.90.10.0/25AS9647Seoul Metropolitan GovernmentRPKI Not found210.90.10.0
- 210.90.15.0/24AS17841NATIONAL INFORMATION RESOURCES SERVICERPKI Not found210.90.15.0
- 210.90.17.0/25AS45400Korea TelecomRPKI Not found210.90.17.0
- 210.90.20.0/24AS4766Korea TelecomRPKI Not found210.90.20.0
- 210.90.20.0/25AS4766Korea TelecomRPKI Not found210.90.20.0
- 210.90.20.128/25AS4766Korea TelecomRPKI Not found210.90.20.128
- 210.90.25.128/25AS45400Korea TelecomRPKI Not found210.90.25.128
- 210.90.28.0/24AS23568CycleBoat Racing Business DivisionRPKI Not found210.90.28.0
- 210.90.44.0/24AS17600KOREA RESOURCES RECOVERY AND REUTILIZATION CORPORATIONRPKI Not found210.90.44.0
- 210.90.46.0/24AS17574Seoul Metropolitan Government Computer CenterRPKI Not found210.90.46.0
- 210.90.47.0/24AS17574Seoul Metropolitan Government Computer CenterRPKI Not found210.90.47.0
- 210.90.58.0/24AS4766Korea TelecomRPKI Not found210.90.58.0
- 210.90.66.0/25AS38682National Institute of Environmental ResearchRPKI Not found210.90.66.0
- 210.90.75.128/25AS45400Korea TelecomRPKI Not found210.90.75.128
- 210.90.76.0/24AS4766Korea TelecomRPKI Not found210.90.76.0
- 210.90.79.0/24AS4766Korea TelecomRPKI Not found210.90.79.0
- 210.90.80.0/24AS45400Korea TelecomRPKI Not found210.90.80.0
- 210.90.82.0/24AS45400Korea TelecomRPKI Not found210.90.82.0
- 210.90.94.0/25AS4766Korea TelecomRPKI Not found210.90.94.0
- 210.90.100.0/24AS4766Korea TelecomRPKI Not found210.90.100.0
- 210.90.107.0/25AS45400Korea TelecomRPKI Not found210.90.107.0
- 210.90.115.128/25AS45400Korea TelecomRPKI Not found210.90.115.128
- 210.90.122.0/25AS4766Korea TelecomRPKI Not found210.90.122.0
- 210.90.122.128/25AS4766Korea TelecomRPKI Not found210.90.122.128
- 210.90.160.0/24AS38676flexnetworksRPKI Not found210.90.160.0
- 210.90.161.0/24AS38676flexnetworksRPKI Not found210.90.161.0
- 210.90.170.0/25AS45400Korea TelecomRPKI Not found210.90.170.0
- 210.90.191.0/24AS45400Korea TelecomRPKI Not found210.90.191.0
- 210.90.193.0/25AS4766Korea TelecomRPKI Not found210.90.193.0
- 210.90.194.0/25AS45400Korea TelecomRPKI Not found210.90.194.0
- 210.90.197.0/24AS4766Korea TelecomRPKI Not found210.90.197.0
- 210.90.199.0/24AS45400Korea TelecomRPKI Not found210.90.199.0
- 210.90.214.0/24AS45400Korea TelecomRPKI Not found210.90.214.0
- 210.90.216.128/25AS45400Korea TelecomRPKI Not found210.90.216.128
- 210.90.224.0/25AS45400Korea TelecomRPKI Not found210.90.224.0
- 210.90.241.128/25AS4766Korea TelecomRPKI Not found210.90.241.128
- 210.90.246.128/25AS4766Korea TelecomRPKI Not found210.90.246.128
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.