Поиск префикса BGP
Введите префикс (или отдельный адрес). Ответ из нашей ежедневной копии глобальной таблицы маршрутизации.
2405:4800::/30
Анонсирован точно
- 2405:4800::/30AS18403FPT Telecom CompanyRPKI Действителен2405:4800::
- Регистратура
- APNIC · Вьетнам · 20 окт. 2008 г.
- Выделенный блок
- 2405:4800:: – 2405:4800:ffff:ffff:ffff:ffff:ffff:ffff
Покрывающие маршруты
Его не покрывает ни один менее специфичный маршрут.
Более специфичные маршруты
- 2405:4800::/32AS18403FPT Telecom CompanyRPKI Действителен2405:4800::
- 2405:4800:10c::/48AS18403FPT Telecom CompanyRPKI Действителен2405:4800:10c::
- 2405:4800:10d::/48AS18403FPT Telecom CompanyRPKI Действителен2405:4800:10d::
- 2405:4800:206::/48AS18403FPT Telecom CompanyRPKI Действителен2405:4800:206::
- 2405:4800:2fe::/48AS18403FPT Telecom CompanyRPKI Действителен2405:4800:2fe::
- 2405:4800:18c2::/48AS18403FPT Telecom CompanyRPKI Действителен2405:4800:18c2::
- 2405:4800:5cc2::/48AS18403FPT Telecom CompanyRPKI Действителен2405:4800:5cc2::
- 2405:4800:a403::/48AS18403FPT Telecom CompanyRPKI Действителен2405:4800:a403::
- 2405:4800:a601::/48AS18403FPT Telecom CompanyRPKI Действителен2405:4800:a601::
- 2405:4801::/32AS18403FPT Telecom CompanyRPKI Действителен2405:4801::
- 2405:4802::/32AS18403FPT Telecom CompanyRPKI Действителен2405:4802::
- 2405:4803::/32AS18403FPT Telecom CompanyRPKI Действителен2405:4803::
- 2405:4803:a000::/36AS18403FPT Telecom CompanyRPKI Действителен2405:4803:a000::
- 2405:4803:b000::/36AS18403FPT Telecom CompanyRPKI Действителен2405:4803:b000::
- 2405:4803:c000::/36AS18403FPT Telecom CompanyRPKI Действителен2405:4803:c000::
- 2405:4803:d000::/36AS18403FPT Telecom CompanyRPKI Действителен2405:4803:d000::
- 2405:4803:e000::/36AS18403FPT Telecom CompanyRPKI Действителен2405:4803:e000::
- 2405:4803:f000::/36AS18403FPT Telecom CompanyRPKI Действителен2405:4803:f000::
Этот текст пока недоступен на языке «русский». До публикации перевода он показан на языке «английский».
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 2.48.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.
Частые вопросы
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.
См. также
- Проверка маршрута RPKIАвторизована ли исходная AS маршрута в ROA?
- Поиск ASNВладелец, регистратура и все префиксы, которые анонсирует AS.
- Поиск по IPASN, провайдер, маршрут, обратный DNS и местоположение любого адреса.
- Калькулятор CIDRСеть, широковещательный адрес, маски и число хостов для любого префикса.