BGP-præfiksopslag
Indtast et præfiks (eller en enkelt adresse). Besvares fra vores daglige kopi af den globale routingtabel.
59.0.0.0/13
Annonceret præcist
- 59.0.0.0/13AS4766Korea TelecomRPKI Ikke fundet59.0.0.0
- Register
- APNIC · Sydkorea · 2. aug. 2004
- Tildelt blok
- 59.0.0.0 – 59.31.255.255
Dækkende ruter
- 59.0.0.0/12AS4766Korea TelecomRPKI Ikke fundet59.0.0.0
- 59.0.0.0/11AS4766Korea TelecomRPKI Ikke fundet59.0.0.0
Mere specifikke ruter
- 59.0.113.0/24AS4766Korea TelecomRPKI Ikke fundet59.0.113.0
- 59.0.144.0/24AS4766Korea TelecomRPKI Ikke fundet59.0.144.0
- 59.0.170.0/24AS4766Korea TelecomRPKI Ikke fundet59.0.170.0
- 59.0.171.0/24AS4766Korea TelecomRPKI Ikke fundet59.0.171.0
- 59.0.172.0/24AS4766Korea TelecomRPKI Ikke fundet59.0.172.0
- 59.0.173.0/24AS4766Korea TelecomRPKI Ikke fundet59.0.173.0
- 59.0.174.0/24AS4766Korea TelecomRPKI Ikke fundet59.0.174.0
- 59.0.175.0/24AS4766Korea TelecomRPKI Ikke fundet59.0.175.0
- 59.0.176.0/24AS4766Korea TelecomRPKI Ikke fundet59.0.176.0
- 59.0.177.0/24AS4766Korea TelecomRPKI Ikke fundet59.0.177.0
- 59.1.40.0/24AS7560Jeonbuk National UniversityRPKI Ikke fundet59.1.40.0
- 59.1.41.0/24AS7560Jeonbuk National UniversityRPKI Ikke fundet59.1.41.0
- 59.1.92.0/24AS131814Presbyterian Medical CenterRPKI Ikke fundet59.1.92.0
- 59.2.3.128/25AS9570Jeonbuk BankRPKI Ikke fundet59.2.3.128
- 59.2.109.0/24AS4766Korea TelecomRPKI Ikke fundet59.2.109.0
- 59.2.112.0/24AS9954Kunsan National University (KNU)RPKI Ikke fundet59.2.112.0
- 59.3.141.128/25AS38681Jeollanamdo Educational Research Information InstituteRPKI Ikke fundet59.3.141.128
- 59.3.221.0/24AS38681Jeollanamdo Educational Research Information InstituteRPKI Ikke fundet59.3.221.0
- 59.4.89.0/24AS4766Korea TelecomRPKI Ikke fundet59.4.89.0
- 59.4.90.0/24AS4766Korea TelecomRPKI Ikke fundet59.4.90.0
- 59.4.91.0/24AS4766Korea TelecomRPKI Ikke fundet59.4.91.0
- 59.4.92.0/24AS4766Korea TelecomRPKI Ikke fundet59.4.92.0
- 59.4.93.0/24AS4766Korea TelecomRPKI Ikke fundet59.4.93.0
- 59.4.94.0/24AS4766Korea TelecomRPKI Ikke fundet59.4.94.0
- 59.4.95.0/24AS4766Korea TelecomRPKI Ikke fundet59.4.95.0
- 59.4.96.0/24AS4766Korea TelecomRPKI Ikke fundet59.4.96.0
- 59.4.97.0/24AS4766Korea TelecomRPKI Ikke fundet59.4.97.0
- 59.4.98.0/24AS4766Korea TelecomRPKI Ikke fundet59.4.98.0
- 59.5.12.0/24AS131835samyangfoods.coRPKI Ikke fundet59.5.12.0
- 59.5.41.0/24AS23587Korea Credit BureauRPKI Ikke fundet59.5.41.0
- 59.7.33.128/25AS131853MYONGJI HOSPITALRPKI Ikke fundet59.7.33.128
- 59.7.252.0/24AS23554Shinhan BankRPKI Ikke fundet59.7.252.0
- 59.7.254.0/24AS23555Shinhan BankRPKI Ikke fundet59.7.254.0
- 59.7.255.0/24AS23555Shinhan BankRPKI Ikke fundet59.7.255.0
Denne tekst findes endnu ikke på dansk. Den vises på engelsk, indtil en oversættelse er udgivet.
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 158.36.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.
Ofte stillede spørgsmål
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.