BGP-prefix opzoeken
Voer een prefix (of één adres) in. Beantwoord uit onze dagelijkse kopie van de wereldwijde routeringstabel.
59.8.0.0/13
Exact aangekondigd
- 59.8.0.0/13AS4766Korea TelecomRPKI Geen ROA59.8.0.0
- Register
- APNIC · Zuid-Korea · 2 aug 2004
- Toegewezen blok
- 59.0.0.0 – 59.31.255.255
Overkoepelende routes
- 59.0.0.0/12AS4766Korea TelecomRPKI Geen ROA59.0.0.0
- 59.0.0.0/11AS4766Korea TelecomRPKI Geen ROA59.0.0.0
Specifiekere routes
- 59.8.0.0/24AS45377Jeju Special Self Governing Provincial office of EducationRPKI Geen ROA59.8.0.0
- 59.8.186.0/24AS4766Korea TelecomRPKI Geen ROA59.8.186.0
- 59.8.187.0/24AS4766Korea TelecomRPKI Geen ROA59.8.187.0
- 59.8.188.0/24AS4766Korea TelecomRPKI Geen ROA59.8.188.0
- 59.8.189.0/24AS4766Korea TelecomRPKI Geen ROA59.8.189.0
- 59.8.190.0/24AS4766Korea TelecomRPKI Geen ROA59.8.190.0
- 59.8.241.0/24AS38401Gyeonggi Provincial Anseong Office of EducationRPKI Geen ROA59.8.241.0
- 59.10.75.0/24AS55613KOREA APPRAISAL BOARDRPKI Geen ROA59.10.75.0
- 59.10.93.128/25AS4766Korea TelecomRPKI Geen ROA59.10.93.128
- 59.10.244.0/24AS9776KOOKMIN BANKRPKI Geen ROA59.10.244.0
- 59.11.43.0/24AS9318SK Broadband Co LtdRPKI Geen ROA59.11.43.0
- 59.11.56.0/23AS4766Korea TelecomRPKI Geen ROA59.11.56.0
- 59.11.68.0/24AS10185Hana Bank Co.RPKI Geen ROA59.11.68.0
- 59.11.69.0/24AS4766Korea TelecomRPKI Geen ROA59.11.69.0
- 59.11.228.0/24AS4766Korea TelecomRPKI Geen ROA59.11.228.0
- 59.11.229.0/24AS4766Korea TelecomRPKI Geen ROA59.11.229.0
- 59.12.121.0/24AS38705KOREA DATARPKI Geen ROA59.12.121.0
- 59.12.136.0/24AS4766Korea TelecomRPKI Geen ROA59.12.136.0
- 59.12.137.0/24AS4766Korea TelecomRPKI Geen ROA59.12.137.0
- 59.12.138.0/24AS4766Korea TelecomRPKI Geen ROA59.12.138.0
- 59.12.139.0/24AS4766Korea TelecomRPKI Geen ROA59.12.139.0
- 59.12.171.0/24AS23554Shinhan BankRPKI Geen ROA59.12.171.0
- 59.12.182.0/24AS4766Korea TelecomRPKI Geen ROA59.12.182.0
- 59.12.188.0/24AS4766Korea TelecomRPKI Geen ROA59.12.188.0
- 59.12.223.0/24AS38395GwangJuHaNam Office of EducationRPKI Geen ROA59.12.223.0
- 59.12.227.0/24AS131817Hecto Innovation Co., LtdRPKI Geen ROA59.12.227.0
- 59.13.50.0/23AS4766Korea TelecomRPKI Geen ROA59.13.50.0
- 59.13.128.0/24AS38400Gyeonggi-do Pyongtaek Office EducationRPKI Geen ROA59.13.128.0
- 59.13.159.0/24AS4766Korea TelecomRPKI Geen ROA59.13.159.0
- 59.13.162.0/24AS4766Korea TelecomRPKI Geen ROA59.13.162.0
- 59.14.66.0/24AS131093viva republicaRPKI Geen ROA59.14.66.0
- 59.14.102.0/23AS46009YABESKRPKI Geen ROA59.14.102.0
- 59.14.104.0/24AS46009YABESKRPKI Geen ROA59.14.104.0
- 59.14.123.0/24AS46009YABESKRPKI Geen ROA59.14.123.0
- 59.14.124.0/23AS46009YABESKRPKI Geen ROA59.14.124.0
- 59.14.124.0/24AS46009YABESKRPKI Geen ROA59.14.124.0
- 59.14.125.0/24AS46009YABESKRPKI Geen ROA59.14.125.0
- 59.14.126.0/24AS46009YABESKRPKI Geen ROA59.14.126.0
- 59.15.10.0/24AS45399Hanjin Information Systems Telecommunication Co., LtdRPKI Geen ROA59.15.10.0
- 59.15.30.0/24AS9526KOSCOMRPKI Geen ROA59.15.30.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.