BGP-præfiksopslag
Indtast et præfiks (eller en enkelt adresse). Besvares fra vores daglige kopi af den globale routingtabel.
112.64.0.0/16
Annonceret præcist
- 112.64.0.0/16AS17621China Unicom Shanghai networkRPKI Gyldig112.64.0.0
- Register
- APNIC · Kina · 22. dec. 2008
- Tildelt blok
- 112.64.0.0 – 112.65.255.255
Dækkende ruter
Ingen mindre specifik rute dækker det.
Mere specifikke ruter
- 112.64.0.0/17AS17621China Unicom Shanghai networkRPKI Gyldig112.64.0.0
- 112.64.32.0/24AS138421China UnicomRPKI Gyldig112.64.32.0
- 112.64.33.0/24AS138421China UnicomRPKI Gyldig112.64.33.0
- 112.64.34.0/24AS138421China UnicomRPKI Gyldig112.64.34.0
- 112.64.35.0/24AS138421China UnicomRPKI Gyldig112.64.35.0
- 112.64.45.0/24AS138421China UnicomRPKI Gyldig112.64.45.0
- 112.64.64.0/24AS138421China UnicomRPKI Gyldig112.64.64.0
- 112.64.112.0/22AS138421China UnicomRPKI Gyldig112.64.112.0
- 112.64.114.0/24AS17621China Unicom Shanghai networkRPKI Gyldig112.64.114.0
- 112.64.128.0/17AS17621China Unicom Shanghai networkRPKI Gyldig112.64.128.0
- 112.64.143.0/24AS4837CHINA UNICOM China169 BackboneRPKI Gyldig112.64.143.0
- 112.64.199.0/24AS17621China Unicom Shanghai networkRPKI Gyldig112.64.199.0
- 112.64.200.0/24AS17621China Unicom Shanghai networkRPKI Gyldig112.64.200.0
- 112.64.212.0/22AS138421China UnicomRPKI Gyldig112.64.212.0
- 112.64.212.0/24AS17621China Unicom Shanghai networkRPKI Gyldig112.64.212.0
- 112.64.213.0/24AS17621China Unicom Shanghai networkRPKI Gyldig112.64.213.0
- 112.64.214.0/24AS17621China Unicom Shanghai networkRPKI Gyldig112.64.214.0
- 112.64.235.0/24AS140979China Unicom Shanghai FuTe IDC networkRPKI Gyldig112.64.235.0
- 112.64.236.0/24AS140979China Unicom Shanghai FuTe IDC networkRPKI Gyldig112.64.236.0
- 112.64.237.0/24AS140979China Unicom Shanghai FuTe IDC networkRPKI Gyldig112.64.237.0
- 112.64.238.0/24AS17621China Unicom Shanghai networkRPKI Gyldig112.64.238.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.