BGP-prefix opzoeken
Voer een prefix (of één adres) in. Beantwoord uit onze dagelijkse kopie van de wereldwijde routeringstabel.
2402:4e00:8000::/33
Exact aangekondigd
- 2402:4e00:8000::/33AS45090Shenzhen Tencent Computer Systems Company LimitedRPKI Geldig2402:4e00:8000::
- Register
- APNIC · China · 13 mei 2010
- Toegewezen blok
- 2402:4e00:: – 2402:4e00:ffff:ffff:ffff:ffff:ffff:ffff
Overkoepelende routes
- 2402:4e00::/32AS45090Shenzhen Tencent Computer Systems Company LimitedRPKI Geldig2402:4e00::
Specifiekere routes
- 2402:4e00:8000::/48AS45090Shenzhen Tencent Computer Systems Company LimitedRPKI Geldig2402:4e00:8000::
- 2402:4e00:8001::/48AS45090Shenzhen Tencent Computer Systems Company LimitedRPKI Geldig2402:4e00:8001::
- 2402:4e00:8020::/44AS45090Shenzhen Tencent Computer Systems Company LimitedRPKI Geldig2402:4e00:8020::
- 2402:4e00:8030::/48AS45090Shenzhen Tencent Computer Systems Company LimitedRPKI Geldig2402:4e00:8030::
- 2402:4e00:c000::/48AS45090Shenzhen Tencent Computer Systems Company LimitedRPKI Geldig2402:4e00:c000::
- 2402:4e00:c010::/44AS45090Shenzhen Tencent Computer Systems Company LimitedRPKI Geldig2402:4e00:c010::
- 2402:4e00:c020::/44AS45090Shenzhen Tencent Computer Systems Company LimitedRPKI Geldig2402:4e00:c020::
- 2402:4e00:c030::/44AS45090Shenzhen Tencent Computer Systems Company LimitedRPKI Geldig2402:4e00:c030::
- 2402:4e00:c040::/44AS45090Shenzhen Tencent Computer Systems Company LimitedRPKI Geldig2402:4e00:c040::
- 2402:4e00:c050::/44AS45090Shenzhen Tencent Computer Systems Company LimitedRPKI Geldig2402:4e00:c050::
- 2402:4e00:c060::/44AS45090Shenzhen Tencent Computer Systems Company LimitedRPKI Geldig2402:4e00:c060::
- 2402:4e00:c070::/44AS45090Shenzhen Tencent Computer Systems Company LimitedRPKI Geldig2402:4e00:c070::
- 2402:4e00:d018::/45AS45090Shenzhen Tencent Computer Systems Company LimitedRPKI Geldig2402:4e00:d018::
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.