Поиск префикса BGP
Введите префикс (или отдельный адрес). Ответ из нашей ежедневной копии глобальной таблицы маршрутизации.
194.186.0.0/16
Анонсирован точно
- 194.186.0.0/16AS3216PJSC "Vimpelcom"RPKI Не найдено194.186.0.0
- Регистратура
- RIPE NCC · Россия · 5 дек. 1995 г.
- Выделенный блок
- 194.186.0.0 – 194.186.255.255
Покрывающие маршруты
Его не покрывает ни один менее специфичный маршрут.
Более специфичные маршруты
- 194.186.14.0/24AS35580ECG-ASRPKI Не найдено194.186.14.0
- 194.186.20.0/24AS3216PJSC "Vimpelcom"RPKI Не найдено194.186.20.0
- 194.186.22.0/24AS3216PJSC "Vimpelcom"RPKI Не найдено194.186.22.0
- 194.186.28.0/23AS3216PJSC "Vimpelcom"RPKI Не найдено194.186.28.0
- 194.186.30.0/24AS3216PJSC "Vimpelcom"RPKI Не найдено194.186.30.0
- 194.186.48.0/23AS3216PJSC "Vimpelcom"RPKI Не найдено194.186.48.0
- 194.186.48.0/24AS56679Voin Telecom LLCRPKI Не найдено194.186.48.0
- 194.186.50.0/24AS3216PJSC "Vimpelcom"RPKI Не найдено194.186.50.0
- 194.186.53.0/24AS3216PJSC "Vimpelcom"RPKI Не найдено194.186.53.0
- 194.186.62.0/24AS3216PJSC "Vimpelcom"RPKI Не найдено194.186.62.0
- 194.186.63.0/24AS47764LLC VKRPKI Не найдено194.186.63.0
- 194.186.78.0/24AS16345PJSC "Vimpelcom"RPKI Не найдено194.186.78.0
- 194.186.82.0/24AS33908AO KirovtelecomRPKI Не найдено194.186.82.0
- 194.186.83.0/24AS34098PJSC Bank ZENITRPKI Не найдено194.186.83.0
- 194.186.100.0/22AS3216PJSC "Vimpelcom"RPKI Не найдено194.186.100.0
- 194.186.101.0/24AS3216PJSC "Vimpelcom"RPKI Не найдено194.186.101.0
- 194.186.102.0/23AS3216PJSC "Vimpelcom"RPKI Не найдено194.186.102.0
- 194.186.104.0/23AS3216PJSC "Vimpelcom"RPKI Не найдено194.186.104.0
- 194.186.106.0/24AS21483PJSC "Vimpelcom"RPKI Не найдено194.186.106.0
- 194.186.116.0/22AS21483PJSC "Vimpelcom"RPKI Не найдено194.186.116.0
- 194.186.122.0/23AS3216PJSC "Vimpelcom"RPKI Не найдено194.186.122.0
- 194.186.129.0/24AS3216PJSC "Vimpelcom"RPKI Не найдено194.186.129.0
- 194.186.144.0/24AS212670DataFort LLCRPKI Не найдено194.186.144.0
- 194.186.154.0/23AS3216PJSC "Vimpelcom"RPKI Не найдено194.186.154.0
- 194.186.154.0/24AS3216PJSC "Vimpelcom"RPKI Не найдено194.186.154.0
- 194.186.166.0/24AS34802Commercial Bank "Renaissance Credit" LLCRPKI Не найдено194.186.166.0
- 194.186.167.0/24AS3216PJSC "Vimpelcom"RPKI Не найдено194.186.167.0
- 194.186.188.0/24AS3216PJSC "Vimpelcom"RPKI Не найдено194.186.188.0
- 194.186.189.0/24AS3216PJSC "Vimpelcom"RPKI Не найдено194.186.189.0
- 194.186.220.0/24AS3216PJSC "Vimpelcom"RPKI Не найдено194.186.220.0
- 194.186.221.0/24AS16345PJSC "Vimpelcom"RPKI Не найдено194.186.221.0
- 194.186.228.0/22AS3216PJSC "Vimpelcom"RPKI Не найдено194.186.228.0
- 194.186.231.0/24AS3216PJSC "Vimpelcom"RPKI Не найдено194.186.231.0
- 194.186.242.0/24AS198502JSC "First Asset Management"RPKI Не найдено194.186.242.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Сеть, широковещательный адрес, маски и число хостов для любого префикса.