Поиск префикса BGP
Введите префикс (или отдельный адрес). Ответ из нашей ежедневной копии глобальной таблицы маршрутизации.
38.50.192.0/18
Анонсирован точно
- 38.50.192.0/18AS13693Vexus FiberRPKI Не найдено38.50.192.0
- Регистратура
- ARIN · Соединенные Штаты · 16 апр. 1991 г.
- Выделенный блок
- 38.0.0.0 – 38.255.255.255
Покрывающие маршруты
- 38.0.0.0/8AS174Cogent Communications, LLCRPKI Не найдено38.0.0.0
Более специфичные маршруты
- 38.50.192.0/21AS13693Vexus FiberRPKI Не найдено38.50.192.0
- 38.50.192.0/23AS13693Vexus FiberRPKI Не найдено38.50.192.0
- 38.50.194.0/23AS13693Vexus FiberRPKI Не найдено38.50.194.0
- 38.50.196.0/24AS13693Vexus FiberRPKI Не найдено38.50.196.0
- 38.50.197.0/24AS13693Vexus FiberRPKI Не найдено38.50.197.0
- 38.50.198.0/23AS13693Vexus FiberRPKI Не найдено38.50.198.0
- 38.50.200.0/21AS13693Vexus FiberRPKI Не найдено38.50.200.0
- 38.50.200.0/23AS13693Vexus FiberRPKI Не найдено38.50.200.0
- 38.50.202.0/23AS13693Vexus FiberRPKI Не найдено38.50.202.0
- 38.50.204.0/22AS13693Vexus FiberRPKI Не найдено38.50.204.0
- 38.50.208.0/21AS13693Vexus FiberRPKI Не найдено38.50.208.0
- 38.50.208.0/22AS13693Vexus FiberRPKI Не найдено38.50.208.0
- 38.50.212.0/23AS13693Vexus FiberRPKI Не найдено38.50.212.0
- 38.50.214.0/24AS13693Vexus FiberRPKI Не найдено38.50.214.0
- 38.50.215.0/24AS13693Vexus FiberRPKI Не найдено38.50.215.0
- 38.50.216.0/22AS397772Vexus FiberRPKI Не найдено38.50.216.0
- 38.50.220.0/23AS398149Vexus FiberRPKI Не найдено38.50.220.0
- 38.50.220.0/24AS398149Vexus FiberRPKI Не найдено38.50.220.0
- 38.50.222.0/23AS19734Vexus FiberRPKI Не найдено38.50.222.0
- 38.50.224.0/22AS13693Vexus FiberRPKI Не найдено38.50.224.0
- 38.50.228.0/22AS13693Vexus FiberRPKI Не найдено38.50.228.0
- 38.50.232.0/22AS13693Vexus FiberRPKI Не найдено38.50.232.0
- 38.50.236.0/23AS13693Vexus FiberRPKI Не найдено38.50.236.0
- 38.50.238.0/24AS13693Vexus FiberRPKI Не найдено38.50.238.0
- 38.50.239.0/24AS13693Vexus FiberRPKI Не найдено38.50.239.0
- 38.50.240.0/22AS13693Vexus FiberRPKI Не найдено38.50.240.0
- 38.50.244.0/24AS13693Vexus FiberRPKI Не найдено38.50.244.0
- 38.50.245.0/24AS13693Vexus FiberRPKI Не найдено38.50.245.0
- 38.50.246.0/24AS13693Vexus FiberRPKI Не найдено38.50.246.0
- 38.50.247.0/24AS13693Vexus FiberRPKI Не найдено38.50.247.0
- 38.50.248.0/22AS13693Vexus FiberRPKI Не найдено38.50.248.0
- 38.50.248.0/23AS13693Vexus FiberRPKI Не найдено38.50.248.0
- 38.50.250.0/24AS13693Vexus FiberRPKI Не найдено38.50.250.0
- 38.50.252.0/24AS13693Vexus FiberRPKI Не найдено38.50.252.0
- 38.50.253.0/24AS13693Vexus FiberRPKI Не найдено38.50.253.0
- 38.50.254.0/24AS13693Vexus FiberRPKI Не найдено38.50.254.0
- 38.50.255.0/24AS13693Vexus FiberRPKI Не найдено38.50.255.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Сеть, широковещательный адрес, маски и число хостов для любого префикса.