BGP-præfiksopslag
Indtast et præfiks (eller en enkelt adresse). Besvares fra vores daglige kopi af den globale routingtabel.
183.78.192.0/18
Annonceret præcist
- 183.78.192.0/18AS38091LG HelloVision Corp.RPKI Ikke fundet183.78.192.0
- Register
- APNIC · Sydkorea · 5. nov. 2009
- Tildelt blok
- 183.78.192.0 – 183.78.255.255
Dækkende ruter
Ingen mindre specifik rute dækker det.
Mere specifikke ruter
- 183.78.192.0/21AS9698LG HelloVision Corp.RPKI Ikke fundet183.78.192.0
- 183.78.193.0/24AS9698LG HelloVision Corp.RPKI Ikke fundet183.78.193.0
- 183.78.200.0/24AS9698LG HelloVision Corp.RPKI Ikke fundet183.78.200.0
- 183.78.201.0/24AS9698LG HelloVision Corp.RPKI Ikke fundet183.78.201.0
- 183.78.202.0/24AS9698LG HelloVision Corp.RPKI Ikke fundet183.78.202.0
- 183.78.203.0/24AS9698LG HelloVision Corp.RPKI Ikke fundet183.78.203.0
- 183.78.204.0/24AS9698LG HelloVision Corp.RPKI Ikke fundet183.78.204.0
- 183.78.205.0/24AS9698LG HelloVision Corp.RPKI Ikke fundet183.78.205.0
- 183.78.206.0/24AS9698LG HelloVision Corp.RPKI Ikke fundet183.78.206.0
- 183.78.207.0/24AS9698LG HelloVision Corp.RPKI Ikke fundet183.78.207.0
- 183.78.208.0/20AS9698LG HelloVision Corp.RPKI Ikke fundet183.78.208.0
- 183.78.208.0/24AS9698LG HelloVision Corp.RPKI Ikke fundet183.78.208.0
- 183.78.209.0/24AS9698LG HelloVision Corp.RPKI Ikke fundet183.78.209.0
- 183.78.210.0/24AS9698LG HelloVision Corp.RPKI Ikke fundet183.78.210.0
- 183.78.211.0/24AS9698LG HelloVision Corp.RPKI Ikke fundet183.78.211.0
- 183.78.213.0/24AS9698LG HelloVision Corp.RPKI Ikke fundet183.78.213.0
- 183.78.214.0/24AS9698LG HelloVision Corp.RPKI Ikke fundet183.78.214.0
- 183.78.215.0/24AS9698LG HelloVision Corp.RPKI Ikke fundet183.78.215.0
- 183.78.216.0/21AS9698LG HelloVision Corp.RPKI Ikke fundet183.78.216.0
- 183.78.224.0/21AS9698LG HelloVision Corp.RPKI Ikke fundet183.78.224.0
- 183.78.227.0/24AS9698LG HelloVision Corp.RPKI Ikke fundet183.78.227.0
- 183.78.232.0/24AS9698LG HelloVision Corp.RPKI Ikke fundet183.78.232.0
- 183.78.233.0/24AS9698LG HelloVision Corp.RPKI Ikke fundet183.78.233.0
- 183.78.234.0/24AS9698LG HelloVision Corp.RPKI Ikke fundet183.78.234.0
- 183.78.235.0/24AS9698LG HelloVision Corp.RPKI Ikke fundet183.78.235.0
- 183.78.236.0/24AS9698LG HelloVision Corp.RPKI Ikke fundet183.78.236.0
- 183.78.237.0/24AS9698LG HelloVision Corp.RPKI Ikke fundet183.78.237.0
- 183.78.238.0/24AS9698LG HelloVision Corp.RPKI Ikke fundet183.78.238.0
- 183.78.239.0/24AS9698LG HelloVision Corp.RPKI Ikke fundet183.78.239.0
- 183.78.240.0/21AS9698LG HelloVision Corp.RPKI Ikke fundet183.78.240.0
- 183.78.248.0/24AS9698LG HelloVision Corp.RPKI Ikke fundet183.78.248.0
- 183.78.249.0/24AS9698LG HelloVision Corp.RPKI Ikke fundet183.78.249.0
- 183.78.250.0/24AS9698LG HelloVision Corp.RPKI Ikke fundet183.78.250.0
- 183.78.251.0/24AS9698LG HelloVision Corp.RPKI Ikke fundet183.78.251.0
- 183.78.252.0/24AS9698LG HelloVision Corp.RPKI Ikke fundet183.78.252.0
- 183.78.253.0/24AS9698LG HelloVision Corp.RPKI Ikke fundet183.78.253.0
- 183.78.254.0/24AS9698LG HelloVision Corp.RPKI Ikke fundet183.78.254.0
- 183.78.255.0/24AS9698LG HelloVision Corp.RPKI Ikke fundet183.78.255.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.