BGP-prefix opzoeken
Voer een prefix (of één adres) in. Beantwoord uit onze dagelijkse kopie van de wereldwijde routeringstabel.
70.39.0.0/19
Exact aangekondigd
- 70.39.0.0/19AS5056Aureon Network ServicesRPKI Geen ROA70.39.0.0
- Register
- ARIN · Verenigde Staten · 15 jul 2008
- Toegewezen blok
- 70.39.0.0 – 70.39.31.255
Overkoepelende routes
Geen minder specifieke route omvat het.
Specifiekere routes
- 70.39.0.0/24AS46892Winnebago Cooperative Telecom AssociationRPKI Geen ROA70.39.0.0
- 70.39.2.0/24AS46892Winnebago Cooperative Telecom AssociationRPKI Geen ROA70.39.2.0
- 70.39.3.0/24AS397475F&B Communications, Inc.RPKI Geen ROA70.39.3.0
- 70.39.5.0/24AS396443Western Iowa NetworksRPKI Geldig70.39.5.0
- 70.39.7.0/24AS5056Aureon Network ServicesRPKI Geen ROA70.39.7.0
- 70.39.12.0/24AS20273WCCTARPKI Geen ROA70.39.12.0
- 70.39.13.0/24AS18883FiberNet Communications L.C.RPKI Geen ROA70.39.13.0
- 70.39.15.0/24AS65777UNASSIGNEDRPKI Geen ROA70.39.15.0
- 70.39.16.0/22AS19628Mahaska Communication Group, LLCRPKI Geen ROA70.39.16.0
- 70.39.16.0/24AS19628Mahaska Communication Group, LLCRPKI Geen ROA70.39.16.0
- 70.39.17.0/24AS19628Mahaska Communication Group, LLCRPKI Geen ROA70.39.17.0
- 70.39.18.0/24AS19628Mahaska Communication Group, LLCRPKI Geen ROA70.39.18.0
- 70.39.19.0/24AS19628Mahaska Communication Group, LLCRPKI Geen ROA70.39.19.0
- 70.39.20.0/24AS13356Panora TelcoRPKI Geen ROA70.39.20.0
- 70.39.21.0/24AS5056Aureon Network ServicesRPKI Geen ROA70.39.21.0
- 70.39.22.0/24AS397475F&B Communications, Inc.RPKI Geen ROA70.39.22.0
- 70.39.24.0/23AS399559Alpine Communications L.C.RPKI Geen ROA70.39.24.0
- 70.39.27.0/24AS63394Eastern Iowa IP, LLCRPKI Geen ROA70.39.27.0
- 70.39.30.0/24AS5056Aureon Network ServicesRPKI Geen ROA70.39.30.0
- 70.39.31.0/24AS5056Aureon Network ServicesRPKI Geen ROA70.39.31.0
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.