BGP-prefix opzoeken
Voer een prefix (of één adres) in. Beantwoord uit onze dagelijkse kopie van de wereldwijde routeringstabel.
2607:9000::/32
Exact aangekondigd
- 2607:9000::/32AS11878tzulo, inc.RPKI Geen ROA2607:9000::
- Register
- ARIN · Verenigde Staten · 13 apr 2010
- Toegewezen blok
- 2607:9000:: – 2607:9000:ffff:ffff:ffff:ffff:ffff:ffff
Overkoepelende routes
Geen minder specifieke route omvat het.
Specifiekere routes
- 2607:9000::/36AS11878tzulo, inc.RPKI Geldig2607:9000::
- 2607:9000:100::/40AS11878tzulo, inc.RPKI Geldig2607:9000:100::
- 2607:9000:300::/40AS11878tzulo, inc.RPKI Geldig2607:9000:300::
- 2607:9000:400::/40AS11878tzulo, inc.RPKI Geldig2607:9000:400::
- 2607:9000:500::/40AS11878tzulo, inc.RPKI Geldig2607:9000:500::
- 2607:9000:600::/40AS11878tzulo, inc.RPKI Geldig2607:9000:600::
- 2607:9000:700::/40AS11878tzulo, inc.RPKI Geldig2607:9000:700::
- 2607:9000:800::/40AS11878tzulo, inc.RPKI Geldig2607:9000:800::
- 2607:9000:900::/40AS11878tzulo, inc.RPKI Geldig2607:9000:900::
- 2607:9000:a00::/40AS11878tzulo, inc.RPKI Geldig2607:9000:a00::
- 2607:9000:b00::/40AS11878tzulo, inc.RPKI Geldig2607:9000:b00::
- 2607:9000:c00::/40AS11878tzulo, inc.RPKI Geldig2607:9000:c00::
- 2607:9000:d00::/40AS11878tzulo, inc.RPKI Geldig2607:9000:d00::
- 2607:9000:e00::/40AS11878tzulo, inc.RPKI Geldig2607:9000:e00::
- 2607:9000:f00::/40AS11878tzulo, inc.RPKI Geldig2607:9000:f00::
- 2607:9000:1000::/36AS11878tzulo, inc.RPKI Geldig2607:9000:1000::
- 2607:9000:2000::/36AS11878tzulo, inc.RPKI Geldig2607:9000:2000::
- 2607:9000:3000::/36AS11878tzulo, inc.RPKI Geldig2607:9000:3000::
- 2607:9000:4000::/36AS11878tzulo, inc.RPKI Geldig2607:9000:4000::
- 2607:9000:5000::/36AS11878tzulo, inc.RPKI Geldig2607:9000:5000::
- 2607:9000:6000::/36AS11878tzulo, inc.RPKI Geldig2607:9000:6000::
- 2607:9000:7000::/36AS11878tzulo, inc.RPKI Geldig2607:9000:7000::
- 2607:9000:8000::/36AS11878tzulo, inc.RPKI Geldig2607:9000:8000::
- 2607:9000:9000::/36AS11878tzulo, inc.RPKI Geldig2607:9000:9000::
- 2607:9000:a000::/36AS11878tzulo, inc.RPKI Geldig2607:9000:a000::
- 2607:9000:e000::/36AS11878tzulo, inc.RPKI Geldig2607:9000:e000::
- 2607:9000:f000::/36AS11878tzulo, inc.RPKI Geldig2607:9000:f000::
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.