BGP-præfiksopslag
Indtast et præfiks (eller en enkelt adresse). Besvares fra vores daglige kopi af den globale routingtabel.
205.179.0.0/16
Annonceret præcist
- 205.179.0.0/16AS3257GTT Communications Inc.RPKI Ikke fundet205.179.0.0
- Register
- ARIN · USA · 20. mar. 1995
- Tildelt blok
- 205.179.0.0 – 205.179.255.255
Dækkende ruter
Ingen mindre specifik rute dækker det.
Mere specifikke ruter
- 205.179.128.0/18AS20001Charter Communications IncRPKI Gyldig205.179.128.0
- 205.179.192.0/20AS20001Charter Communications IncRPKI Gyldig205.179.192.0
- 205.179.208.0/24AS32043NeoFiber Communications inc.RPKI Gyldig205.179.208.0
- 205.179.210.0/24AS2914NTT America, Inc.RPKI Gyldig205.179.210.0
- 205.179.211.0/24AS401783TOKALA COMMUNICATIONS INC.RPKI Gyldig205.179.211.0
- 205.179.212.0/24AS2914NTT America, Inc.RPKI Gyldig205.179.212.0
- 205.179.213.0/24AS2914NTT America, Inc.RPKI Gyldig205.179.213.0
- 205.179.214.0/24AS6220inContact Inc.RPKI Gyldig205.179.214.0
- 205.179.215.0/24AS2914NTT America, Inc.RPKI Gyldig205.179.215.0
- 205.179.216.0/24AS2914NTT America, Inc.RPKI Gyldig205.179.216.0
- 205.179.217.0/24AS2914NTT America, Inc.RPKI Gyldig205.179.217.0
- 205.179.218.0/24AS2914NTT America, Inc.RPKI Gyldig205.179.218.0
- 205.179.219.0/24AS32043NeoFiber Communications inc.RPKI Gyldig205.179.219.0
- 205.179.220.0/22AS199524G-Core Labs S.A.RPKI Gyldig205.179.220.0
- 205.179.224.0/20AS20001Charter Communications IncRPKI Gyldig205.179.224.0
- 205.179.240.0/22AS199524G-Core Labs S.A.RPKI Gyldig205.179.240.0
- 205.179.244.0/22AS2914NTT America, Inc.RPKI Gyldig205.179.244.0
- 205.179.248.0/22AS9009M247 Europe SRLRPKI Gyldig205.179.248.0
- 205.179.252.0/24AS32043NeoFiber Communications inc.RPKI Gyldig205.179.252.0
- 205.179.254.0/24AS2914NTT America, Inc.RPKI Gyldig205.179.254.0
- 205.179.255.0/24AS2914NTT America, Inc.RPKI Gyldig205.179.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.