Поиск префикса BGP
Введите префикс (или отдельный адрес). Ответ из нашей ежедневной копии глобальной таблицы маршрутизации.
38.191.0.0/19
Анонсирован точно
- 38.191.0.0/19AS395876Huxley Communications CooperativeRPKI Не найдено38.191.0.0
- Регистратура
- ARIN · Соединенные Штаты · 16 апр. 1991 г.
- Выделенный блок
- 38.0.0.0 – 38.255.255.255
Покрывающие маршруты
- 38.0.0.0/8AS174Cogent Communications, LLCRPKI Не найдено38.0.0.0
Более специфичные маршруты
- 38.191.0.0/24AS395876Huxley Communications CooperativeRPKI Не найдено38.191.0.0
- 38.191.1.0/24AS395876Huxley Communications CooperativeRPKI Не найдено38.191.1.0
- 38.191.2.0/24AS395876Huxley Communications CooperativeRPKI Не найдено38.191.2.0
- 38.191.3.0/24AS395876Huxley Communications CooperativeRPKI Не найдено38.191.3.0
- 38.191.4.0/24AS395876Huxley Communications CooperativeRPKI Не найдено38.191.4.0
- 38.191.5.0/24AS395876Huxley Communications CooperativeRPKI Не найдено38.191.5.0
- 38.191.6.0/24AS395876Huxley Communications CooperativeRPKI Не найдено38.191.6.0
- 38.191.7.0/24AS395876Huxley Communications CooperativeRPKI Не найдено38.191.7.0
- 38.191.8.0/24AS395876Huxley Communications CooperativeRPKI Не найдено38.191.8.0
- 38.191.9.0/24AS395876Huxley Communications CooperativeRPKI Не найдено38.191.9.0
- 38.191.10.0/24AS395876Huxley Communications CooperativeRPKI Не найдено38.191.10.0
- 38.191.11.0/24AS395876Huxley Communications CooperativeRPKI Не найдено38.191.11.0
- 38.191.12.0/24AS395876Huxley Communications CooperativeRPKI Не найдено38.191.12.0
- 38.191.13.0/24AS395876Huxley Communications CooperativeRPKI Не найдено38.191.13.0
- 38.191.14.0/24AS395876Huxley Communications CooperativeRPKI Не найдено38.191.14.0
- 38.191.15.0/24AS395876Huxley Communications CooperativeRPKI Не найдено38.191.15.0
- 38.191.16.0/24AS395876Huxley Communications CooperativeRPKI Не найдено38.191.16.0
- 38.191.17.0/24AS395876Huxley Communications CooperativeRPKI Не найдено38.191.17.0
- 38.191.18.0/24AS395876Huxley Communications CooperativeRPKI Не найдено38.191.18.0
- 38.191.19.0/24AS395876Huxley Communications CooperativeRPKI Не найдено38.191.19.0
- 38.191.20.0/24AS395876Huxley Communications CooperativeRPKI Не найдено38.191.20.0
- 38.191.21.0/24AS395876Huxley Communications CooperativeRPKI Не найдено38.191.21.0
- 38.191.22.0/24AS395876Huxley Communications CooperativeRPKI Не найдено38.191.22.0
- 38.191.23.0/24AS395876Huxley Communications CooperativeRPKI Не найдено38.191.23.0
- 38.191.24.0/24AS395876Huxley Communications CooperativeRPKI Не найдено38.191.24.0
- 38.191.25.0/24AS395876Huxley Communications CooperativeRPKI Не найдено38.191.25.0
- 38.191.26.0/24AS395876Huxley Communications CooperativeRPKI Не найдено38.191.26.0
- 38.191.27.0/24AS395876Huxley Communications CooperativeRPKI Не найдено38.191.27.0
- 38.191.28.0/24AS395876Huxley Communications CooperativeRPKI Не найдено38.191.28.0
- 38.191.29.0/24AS395876Huxley Communications CooperativeRPKI Не найдено38.191.29.0
- 38.191.30.0/24AS395876Huxley Communications CooperativeRPKI Не найдено38.191.30.0
- 38.191.31.0/24AS395876Huxley Communications CooperativeRPKI Не найдено38.191.31.0
Этот текст пока недоступен на языке «русский». До публикации перевода он показан на языке «английский».
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 128.139.0.0/16. 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Сеть, широковещательный адрес, маски и число хостов для любого префикса.