BGP-præfiksopslag
Indtast et præfiks (eller en enkelt adresse). Besvares fra vores daglige kopi af den globale routingtabel.
143.244.96.0/19
Annonceret præcist
- 143.244.96.0/19AS62642Bigleaf Networks, Inc.RPKI Ikke fundet143.244.96.0
- Register
- ARIN · USA · 20. dec. 2019
- Tildelt blok
- 143.244.96.0 – 143.244.127.255
Dækkende ruter
Ingen mindre specifik rute dækker det.
Mere specifikke ruter
- 143.244.96.0/24AS62642Bigleaf Networks, Inc.RPKI Ikke fundet143.244.96.0
- 143.244.97.0/24AS62642Bigleaf Networks, Inc.RPKI Ikke fundet143.244.97.0
- 143.244.98.0/24AS62642Bigleaf Networks, Inc.RPKI Ikke fundet143.244.98.0
- 143.244.99.0/24AS62642Bigleaf Networks, Inc.RPKI Ikke fundet143.244.99.0
- 143.244.100.0/24AS62642Bigleaf Networks, Inc.RPKI Ikke fundet143.244.100.0
- 143.244.101.0/24AS62642Bigleaf Networks, Inc.RPKI Ikke fundet143.244.101.0
- 143.244.102.0/24AS62642Bigleaf Networks, Inc.RPKI Ikke fundet143.244.102.0
- 143.244.103.0/24AS62642Bigleaf Networks, Inc.RPKI Ikke fundet143.244.103.0
- 143.244.104.0/24AS62642Bigleaf Networks, Inc.RPKI Ikke fundet143.244.104.0
- 143.244.105.0/24AS62642Bigleaf Networks, Inc.RPKI Ikke fundet143.244.105.0
- 143.244.106.0/24AS62642Bigleaf Networks, Inc.RPKI Ikke fundet143.244.106.0
- 143.244.107.0/24AS62642Bigleaf Networks, Inc.RPKI Ikke fundet143.244.107.0
- 143.244.108.0/24AS62642Bigleaf Networks, Inc.RPKI Ikke fundet143.244.108.0
- 143.244.109.0/24AS62642Bigleaf Networks, Inc.RPKI Ikke fundet143.244.109.0
- 143.244.110.0/24AS62642Bigleaf Networks, Inc.RPKI Ikke fundet143.244.110.0
- 143.244.111.0/24AS62642Bigleaf Networks, Inc.RPKI Ikke fundet143.244.111.0
- 143.244.112.0/24AS62642Bigleaf Networks, Inc.RPKI Ikke fundet143.244.112.0
- 143.244.113.0/24AS62642Bigleaf Networks, Inc.RPKI Ikke fundet143.244.113.0
- 143.244.114.0/24AS62642Bigleaf Networks, Inc.RPKI Ikke fundet143.244.114.0
- 143.244.115.0/24AS62642Bigleaf Networks, Inc.RPKI Ikke fundet143.244.115.0
- 143.244.116.0/24AS62642Bigleaf Networks, Inc.RPKI Ikke fundet143.244.116.0
- 143.244.117.0/24AS62642Bigleaf Networks, Inc.RPKI Ikke fundet143.244.117.0
- 143.244.118.0/24AS62642Bigleaf Networks, Inc.RPKI Ikke fundet143.244.118.0
- 143.244.119.0/24AS62642Bigleaf Networks, Inc.RPKI Ikke fundet143.244.119.0
- 143.244.120.0/24AS62642Bigleaf Networks, Inc.RPKI Ikke fundet143.244.120.0
- 143.244.121.0/24AS62642Bigleaf Networks, Inc.RPKI Ikke fundet143.244.121.0
- 143.244.122.0/24AS62642Bigleaf Networks, Inc.RPKI Ikke fundet143.244.122.0
- 143.244.123.0/24AS62642Bigleaf Networks, Inc.RPKI Ikke fundet143.244.123.0
- 143.244.124.0/24AS62642Bigleaf Networks, Inc.RPKI Ikke fundet143.244.124.0
- 143.244.125.0/24AS62642Bigleaf Networks, Inc.RPKI Ikke fundet143.244.125.0
- 143.244.126.0/24AS62642Bigleaf Networks, Inc.RPKI Ikke fundet143.244.126.0
- 143.244.127.0/24AS62642Bigleaf Networks, Inc.RPKI Ikke fundet143.244.127.0
Denne tekst findes endnu ikke på dansk. Den vises på engelsk, indtil en oversættelse er udgivet.
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 158.36.0.0/14. 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.
Ofte stillede spørgsmål
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.