BGP-prefix opzoeken
Voer een prefix (of één adres) in. Beantwoord uit onze dagelijkse kopie van de wereldwijde routeringstabel.
180.64.0.0/13
Exact aangekondigd
- 180.64.0.0/13AS9318SK Broadband Co LtdRPKI Geen ROA180.64.0.0
- Register
- APNIC · Zuid-Korea · 7 jul 2009
- Toegewezen blok
- 180.64.0.0 – 180.71.255.255
Overkoepelende routes
Geen minder specifieke route omvat het.
Specifiekere routes
- 180.64.0.0/16AS9318SK Broadband Co LtdRPKI Geen ROA180.64.0.0
- 180.64.135.0/24AS55632Sejong City Office of EducationRPKI Geen ROA180.64.135.0
- 180.64.141.0/24AS55632Sejong City Office of EducationRPKI Geen ROA180.64.141.0
- 180.64.142.0/24AS55632Sejong City Office of EducationRPKI Geen ROA180.64.142.0
- 180.64.199.0/24AS131874KDB CAPITAL CORPORATIONRPKI Geen ROA180.64.199.0
- 180.64.208.0/24AS45389Jeonbuk State office of Education Future Education Research InstituteRPKI Geen ROA180.64.208.0
- 180.64.216.0/24AS9647Seoul Metropolitan GovernmentRPKI Geen ROA180.64.216.0
- 180.64.218.0/24AS152214Korean Air LinesRPKI Geen ROA180.64.218.0
- 180.65.0.0/16AS9318SK Broadband Co LtdRPKI Geen ROA180.65.0.0
- 180.65.53.0/24AS10060YONSEI UNIVERSITY HEALTH SYSTEMRPKI Geen ROA180.65.53.0
- 180.65.57.0/24AS10060YONSEI UNIVERSITY HEALTH SYSTEMRPKI Geen ROA180.65.57.0
- 180.65.59.0/24AS10060YONSEI UNIVERSITY HEALTH SYSTEMRPKI Geen ROA180.65.59.0
- 180.66.0.0/16AS9318SK Broadband Co LtdRPKI Geen ROA180.66.0.0
- 180.67.0.0/16AS9318SK Broadband Co LtdRPKI Geen ROA180.67.0.0
- 180.67.21.0/24AS10060YONSEI UNIVERSITY HEALTH SYSTEMRPKI Geen ROA180.67.21.0
- 180.68.0.0/16AS9318SK Broadband Co LtdRPKI Geen ROA180.68.0.0
- 180.69.0.0/16AS9318SK Broadband Co LtdRPKI Geen ROA180.69.0.0
- 180.70.0.0/16AS9318SK Broadband Co LtdRPKI Geen ROA180.70.0.0
- 180.71.0.0/16AS9318SK Broadband Co LtdRPKI Geen ROA180.71.0.0
- 180.71.192.0/22AS9318SK Broadband Co LtdRPKI Geen ROA180.71.192.0
Deze tekst is nog niet beschikbaar in het Nederlands. Hij wordt in het Engels getoond tot er een vertaling is gepubliceerd.
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 144.122.0.0/16 (Middle East Technical University, AS1967). 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.
Veelgestelde vragen
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.