BGP-præfiksopslag
Indtast et præfiks (eller en enkelt adresse). Besvares fra vores daglige kopi af den globale routingtabel.
210.112.0.0/17
Annonceret præcist
- 210.112.0.0/17AS9848SEJONG NETWORKSRPKI Ikke fundet210.112.0.0
- Register
- APNIC · Sydkorea · 30. apr. 1997
- Tildelt blok
- 210.112.0.0 – 210.112.127.255
Dækkende ruter
Ingen mindre specifik rute dækker det.
Mere specifikke ruter
- 210.112.16.0/20AS9848SEJONG NETWORKSRPKI Ikke fundet210.112.16.0
- 210.112.17.0/24AS4670ShinbiroRPKI Ikke fundet210.112.17.0
- 210.112.19.0/24AS4670ShinbiroRPKI Ikke fundet210.112.19.0
- 210.112.21.0/24AS4670ShinbiroRPKI Ikke fundet210.112.21.0
- 210.112.23.0/24AS4670ShinbiroRPKI Ikke fundet210.112.23.0
- 210.112.25.0/24AS4670ShinbiroRPKI Ikke fundet210.112.25.0
- 210.112.27.0/24AS4670ShinbiroRPKI Ikke fundet210.112.27.0
- 210.112.29.0/24AS4670ShinbiroRPKI Ikke fundet210.112.29.0
- 210.112.31.0/24AS4670ShinbiroRPKI Ikke fundet210.112.31.0
- 210.112.32.0/19AS9848SEJONG NETWORKSRPKI Ikke fundet210.112.32.0
- 210.112.48.0/24AS4670ShinbiroRPKI Ikke fundet210.112.48.0
- 210.112.50.0/24AS4670ShinbiroRPKI Ikke fundet210.112.50.0
- 210.112.51.0/24AS4670ShinbiroRPKI Ikke fundet210.112.51.0
- 210.112.53.0/24AS4670ShinbiroRPKI Ikke fundet210.112.53.0
- 210.112.55.0/24AS4670ShinbiroRPKI Ikke fundet210.112.55.0
- 210.112.57.0/24AS4670ShinbiroRPKI Ikke fundet210.112.57.0
- 210.112.58.0/24AS4670ShinbiroRPKI Ikke fundet210.112.58.0
- 210.112.60.0/24AS4670ShinbiroRPKI Ikke fundet210.112.60.0
- 210.112.61.0/24AS4670ShinbiroRPKI Ikke fundet210.112.61.0
- 210.112.63.0/24AS4670ShinbiroRPKI Ikke fundet210.112.63.0
- 210.112.64.0/19AS9848SEJONG NETWORKSRPKI Ikke fundet210.112.64.0
- 210.112.72.0/24AS4670ShinbiroRPKI Ikke fundet210.112.72.0
- 210.112.86.0/24AS131866Digital Edge KoreaRPKI Ikke fundet210.112.86.0
- 210.112.90.0/24AS4670ShinbiroRPKI Ikke fundet210.112.90.0
- 210.112.91.0/24AS4670ShinbiroRPKI Ikke fundet210.112.91.0
- 210.112.92.0/24AS4670ShinbiroRPKI Ikke fundet210.112.92.0
- 210.112.93.0/24AS4670ShinbiroRPKI Ikke fundet210.112.93.0
- 210.112.94.0/24AS4670ShinbiroRPKI Ikke fundet210.112.94.0
- 210.112.95.0/24AS4670ShinbiroRPKI Ikke fundet210.112.95.0
- 210.112.102.0/24AS4670ShinbiroRPKI Ikke fundet210.112.102.0
- 210.112.104.0/24AS131866Digital Edge KoreaRPKI Ikke fundet210.112.104.0
- 210.112.110.0/24AS131866Digital Edge KoreaRPKI Ikke fundet210.112.110.0
- 210.112.111.0/24AS131866Digital Edge KoreaRPKI Ikke fundet210.112.111.0
- 210.112.114.0/24AS4670ShinbiroRPKI Ikke fundet210.112.114.0
- 210.112.116.0/24AS131866Digital Edge KoreaRPKI Ikke fundet210.112.116.0
- 210.112.118.0/24AS131866Digital Edge KoreaRPKI Ikke fundet210.112.118.0
- 210.112.119.0/24AS131866Digital Edge KoreaRPKI Ikke fundet210.112.119.0
- 210.112.120.0/24AS131866Digital Edge KoreaRPKI Ikke fundet210.112.120.0
- 210.112.121.0/24AS131866Digital Edge KoreaRPKI Ikke fundet210.112.121.0
- 210.112.122.0/24AS131866Digital Edge KoreaRPKI Ikke fundet210.112.122.0
- 210.112.124.0/24AS131866Digital Edge KoreaRPKI Ikke fundet210.112.124.0
- 210.112.126.0/24AS131866Digital Edge KoreaRPKI Ikke fundet210.112.126.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.