BGP-prefix opzoeken
Voer een prefix (of één adres) in. Beantwoord uit onze dagelijkse kopie van de wereldwijde routeringstabel.
2800:530::/32
Exact aangekondigd
- 2800:530::/32AS52233Columbus Communications Curacao NVRPKI Geldig2800:530::
- Register
- LACNIC · Curaçao · 19 okt 2010
- Toegewezen blok
- 2800:530:: – 2800:530:ffff:ffff:ffff:ffff:ffff:ffff
Overkoepelende routes
Geen minder specifieke route omvat het.
Specifiekere routes
- 2800:530::/36AS52233Columbus Communications Curacao NVRPKI Geldig2800:530::
- 2800:530:1000::/36AS52233Columbus Communications Curacao NVRPKI Geldig2800:530:1000::
- 2800:530:2000::/36AS52233Columbus Communications Curacao NVRPKI Geldig2800:530:2000::
- 2800:530:3000::/36AS52233Columbus Communications Curacao NVRPKI Geldig2800:530:3000::
- 2800:530:4000::/36AS52233Columbus Communications Curacao NVRPKI Geldig2800:530:4000::
- 2800:530:5000::/36AS52233Columbus Communications Curacao NVRPKI Geldig2800:530:5000::
- 2800:530:6000::/36AS52233Columbus Communications Curacao NVRPKI Geldig2800:530:6000::
- 2800:530:7000::/36AS52233Columbus Communications Curacao NVRPKI Geldig2800:530:7000::
- 2800:530:8000::/36AS52233Columbus Communications Curacao NVRPKI Geldig2800:530:8000::
- 2800:530:9000::/36AS52233Columbus Communications Curacao NVRPKI Geldig2800:530:9000::
- 2800:530:a000::/36AS52233Columbus Communications Curacao NVRPKI Geldig2800:530:a000::
- 2800:530:b000::/36AS52233Columbus Communications Curacao NVRPKI Geldig2800:530:b000::
- 2800:530:c000::/36AS52233Columbus Communications Curacao NVRPKI Geldig2800:530:c000::
- 2800:530:d000::/36AS52233Columbus Communications Curacao NVRPKI Geldig2800:530:d000::
- 2800:530:e000::/36AS52233Columbus Communications Curacao NVRPKI Geldig2800:530:e000::
- 2800:530:f000::/36AS52233Columbus Communications Curacao NVRPKI Geldig2800:530: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.