BGP-prefix opzoeken
Voer een prefix (of één adres) in. Beantwoord uit onze dagelijkse kopie van de wereldwijde routeringstabel.
59.16.0.0/12
Exact aangekondigd
- 59.16.0.0/12AS4766Korea TelecomRPKI Geen ROA59.16.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/11AS4766Korea TelecomRPKI Geen ROA59.0.0.0
Specifiekere routes
- 59.16.0.0/13AS4766Korea TelecomRPKI Geen ROA59.16.0.0
- 59.16.50.0/24AS4766Korea TelecomRPKI Geen ROA59.16.50.0
- 59.16.91.0/25AS55608KB Life Insurance Co., Ltd.RPKI Geen ROA59.16.91.0
- 59.17.3.0/24AS10188Songdo Chadwick international SchoolRPKI Geen ROA59.17.3.0
- 59.17.47.128/25AS7620Toss BankRPKI Geen ROA59.17.47.128
- 59.17.186.0/24AS17567Airport Railroad Co ltdRPKI Geen ROA59.17.186.0
- 59.17.188.0/24AS17567Airport Railroad Co ltdRPKI Geen ROA59.17.188.0
- 59.18.64.0/19AS4766Korea TelecomRPKI Geen ROA59.18.64.0
- 59.18.87.0/24AS4766Korea TelecomRPKI Geen ROA59.18.87.0
- 59.18.96.0/19AS4766Korea TelecomRPKI Geen ROA59.18.96.0
- 59.18.215.0/24AS18032SHINHAN DSRPKI Geen ROA59.18.215.0
- 59.18.252.0/24AS131836Firstfire Marine InsuranceRPKI Geen ROA59.18.252.0
- 59.23.228.0/22AS152232kt cloud Co., LtdRPKI Geen ROA59.23.228.0
- 59.24.0.0/13AS4766Korea TelecomRPKI Geen ROA59.24.0.0
- 59.25.64.0/24AS38104Hyejeon UniversityRPKI Geen ROA59.25.64.0
- 59.25.65.0/24AS38104Hyejeon UniversityRPKI Geen ROA59.25.65.0
- 59.25.66.0/24AS38104Hyejeon UniversityRPKI Geen ROA59.25.66.0
- 59.25.67.0/24AS38104Hyejeon UniversityRPKI Geen ROA59.25.67.0
- 59.25.68.0/24AS38104Hyejeon UniversityRPKI Geen ROA59.25.68.0
- 59.26.6.0/24AS9782WooSong UniversityRPKI Geen ROA59.26.6.0
- 59.26.7.0/24AS18029Daejeon Helath Sciences CollegeRPKI Geen ROA59.26.7.0
- 59.26.221.0/24AS9775Hannam UniversityRPKI Geen ROA59.26.221.0
- 59.26.222.0/24AS9775Hannam UniversityRPKI Geen ROA59.26.222.0
- 59.26.223.0/24AS9775Hannam UniversityRPKI Geen ROA59.26.223.0
- 59.27.104.0/24AS10058NACUFOKRPKI Geen ROA59.27.104.0
- 59.27.163.0/24AS23552Korea Nazarene UniversityRPKI Geen ROA59.27.163.0
- 59.27.164.0/22AS23552Korea Nazarene UniversityRPKI Geen ROA59.27.164.0
- 59.27.168.0/24AS23552Korea Nazarene UniversityRPKI Geen ROA59.27.168.0
- 59.29.21.0/24AS55615DOUZONEBIZONRPKI Geen ROA59.29.21.0
- 59.29.54.0/24AS55615DOUZONEBIZONRPKI Geen ROA59.29.54.0
- 59.29.213.128/25AS18034Gangneung-Wonju National UniversityRPKI Geen ROA59.29.213.128
- 59.30.254.0/24AS55615DOUZONEBIZONRPKI Geen ROA59.30.254.0
- 59.31.246.128/25AS4766Korea TelecomRPKI Geen ROA59.31.246.128
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.