BGP-prefix opzoeken
Voer een prefix (of één adres) in. Beantwoord uit onze dagelijkse kopie van de wereldwijde routeringstabel.
2602:f864::/32
Exact aangekondigd
- 2602:f864::/32AS402628IDCRPKI Geldig2602:f864::
- Register
- ARIN · Verenigde Staten · 29 jul 2024
- Toegewezen blok
- 2602:f864:: – 2602:f864:ffff:ffff:ffff:ffff:ffff:ffff
Overkoepelende routes
Geen minder specifieke route omvat het.
Specifiekere routes
- 2602:f864:120::/47AS36530IDC CubeRPKI Geldig2602:f864:120::
- 2602:f864:122::/47AS36530IDC CubeRPKI Geldig2602:f864:122::
- 2602:f864:201::/48AS36530IDC CubeRPKI Geldig2602:f864:201::
- 2602:f864:210::/44AS402628IDCRPKI Geldig2602:f864:210::
- 2602:f864:211::/48AS36530IDC CubeRPKI Geldig2602:f864:211::
- 2602:f864:212::/48AS36530IDC CubeRPKI Geldig2602:f864:212::
- 2602:f864:21c::/48AS36530IDC CubeRPKI Geldig2602:f864:21c::
- 2602:f864:220::/44AS402628IDCRPKI Geldig2602:f864:220::
- 2602:f864:241::/48AS402628IDCRPKI Geldig2602:f864:241::
- 2602:f864:242::/48AS36530IDC CubeRPKI Geldig2602:f864:242::
- 2602:f864:248::/48AS402628IDCRPKI Geldig2602:f864:248::
- 2602:f864:260::/44AS402628IDCRPKI Geldig2602:f864:260::
- 2602:f864:300::/44AS36530IDC CubeRPKI Geldig2602:f864:300::
- 2602:f864:a01::/48AS36530IDC CubeRPKI Geldig2602:f864:a01::
- 2602:f864:c00::/40AS402628IDCRPKI Geldig2602:f864:c00::
- 2602:f864:d00::/40AS398340IDCRPKI Geldig2602:f864:d00::
- 2602:f864:e00::/40AS36530IDC CubeRPKI Geldig2602:f864:e00::
- 2602:f864:f04::/47AS199436BangLong YangRPKI Geldig2602:f864:f04::
- 2602:f864:f04::/48AS199436BangLong YangRPKI Geldig2602:f864:f04::
- 2602:f864:f05::/48AS199436BangLong YangRPKI Geldig2602:f864:f05::
- 2602:f864:f14::/47AS199436BangLong YangRPKI Geldig2602:f864:f14::
- 2602:f864:f14::/48AS199436BangLong YangRPKI Geldig2602:f864:f14::
- 2602:f864:f15::/48AS199436BangLong YangRPKI Geldig2602:f864:f15::
- 2602:f864:ffe::/47AS199436BangLong YangRPKI Geldig2602:f864:ffe::
Deze tekst is nog niet beschikbaar in het Nederlands. Hij wordt in het Engels getoond tot er een vertaling is gepubliceerd.
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 144.122.0.0/16 (Middle East Technical University, AS1967). 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.
Veelgestelde vragen
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.