BGP-præfiksopslag
Indtast et præfiks (eller en enkelt adresse). Besvares fra vores daglige kopi af den globale routingtabel.
2607:ffd0::/32
Annonceret præcist
- 2607:ffd0::/32AS13767DataBank Holdings, Ltd.RPKI Ikke fundet2607:ffd0::
- Register
- ARIN · USA · 21. jan. 2010
- Tildelt blok
- 2607:ffd0:: – 2607:ffd0:ffff:ffff:ffff:ffff:ffff:ffff
Dækkende ruter
Ingen mindre specifik rute dækker det.
Mere specifikke ruter
- 2607:ffd0:4::/48AS13767DataBank Holdings, Ltd.RPKI Ikke fundet2607:ffd0:4::
- 2607:ffd0:5::/48AS35937MarquisNetRPKI Ikke fundet2607:ffd0:5::
- 2607:ffd0:100::/40AS13767DataBank Holdings, Ltd.RPKI Ikke fundet2607:ffd0:100::
- 2607:ffd0:300::/40AS13767DataBank Holdings, Ltd.RPKI Ikke fundet2607:ffd0:300::
- 2607:ffd0:303::/48AS395506KODIAK NETWORKS, INC.RPKI Ikke fundet2607:ffd0:303::
- 2607:ffd0:400::/40AS13767DataBank Holdings, Ltd.RPKI Ikke fundet2607:ffd0:400::
- 2607:ffd0:500::/40AS13767DataBank Holdings, Ltd.RPKI Ikke fundet2607:ffd0:500::
- 2607:ffd0:600::/40AS13767DataBank Holdings, Ltd.RPKI Ikke fundet2607:ffd0:600::
- 2607:ffd0:700::/40AS13767DataBank Holdings, Ltd.RPKI Ikke fundet2607:ffd0:700::
- 2607:ffd0:700::/48AS13767DataBank Holdings, Ltd.RPKI Ikke fundet2607:ffd0:700::
- 2607:ffd0:701::/48AS13767DataBank Holdings, Ltd.RPKI Ikke fundet2607:ffd0:701::
- 2607:ffd0:702::/48AS13767DataBank Holdings, Ltd.RPKI Ikke fundet2607:ffd0:702::
- 2607:ffd0:800::/40AS13767DataBank Holdings, Ltd.RPKI Ikke fundet2607:ffd0:800::
- 2607:ffd0:803::/48AS13767DataBank Holdings, Ltd.RPKI Ikke fundet2607:ffd0:803::
- 2607:ffd0:900::/40AS13767DataBank Holdings, Ltd.RPKI Ikke fundet2607:ffd0:900::
- 2607:ffd0:e00::/40AS13767DataBank Holdings, Ltd.RPKI Ikke fundet2607:ffd0:e00::
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.