Поиск префикса BGP
Введите префикс (или отдельный адрес). Ответ из нашей ежедневной копии глобальной таблицы маршрутизации.
64.212.0.0/15
Анонсирован точно
- 64.212.0.0/15AS3549Level 3 Parent, LLCRPKI Не найдено64.212.0.0
- Регистратура
- ARIN · Соединенные Штаты · 15 мар. 2000 г.
- Выделенный блок
- 64.212.0.0 – 64.213.255.255
Покрывающие маршруты
- 64.212.0.0/14AS3549Level 3 Parent, LLCRPKI Не найдено64.212.0.0
Более специфичные маршруты
- 64.212.61.0/24AS13631CITADEL ENTERPRISE AMERICAS LLCRPKI Не найдено64.212.61.0
- 64.212.63.0/24AS13480Ongoing Operations, LLCRPKI Не найдено64.212.63.0
- 64.212.72.0/24AS36165ITM TELECOMRPKI Действителен64.212.72.0
- 64.212.73.0/24AS36165ITM TELECOMRPKI Действителен64.212.73.0
- 64.212.74.0/24AS36165ITM TELECOMRPKI Действителен64.212.74.0
- 64.212.75.0/24AS36165ITM TELECOMRPKI Действителен64.212.75.0
- 64.212.76.0/24AS36165ITM TELECOMRPKI Действителен64.212.76.0
- 64.212.77.0/24AS36165ITM TELECOMRPKI Действителен64.212.77.0
- 64.212.78.0/24AS36165ITM TELECOMRPKI Действителен64.212.78.0
- 64.212.79.0/24AS36165ITM TELECOMRPKI Действителен64.212.79.0
- 64.212.138.0/24AS3549Level 3 Parent, LLCRPKI Не найдено64.212.138.0
- 64.212.208.0/24AS31837Lionbridge Technologies, Inc.RPKI Не найдено64.212.208.0
- 64.213.37.0/24AS11178AccessPlusRPKI Не найдено64.213.37.0
- 64.213.56.0/21AS18809Cable OndaRPKI Действителен64.213.56.0
- 64.213.130.0/24AS16659Crown Castle USARPKI Не найдено64.213.130.0
- 64.213.134.0/24AS16789YARDI SYSTEMS, INCRPKI Не найдено64.213.134.0
- 64.213.148.0/24AS10753Level 3 Parent, LLCRPKI Не найдено64.213.148.0
- 64.213.209.0/24AS3549Level 3 Parent, LLCRPKI Не найдено64.213.209.0
- 64.213.216.0/21AS14828Hiawatha Broadband Communications, IncRPKI Не найдено64.213.216.0
- 64.213.224.0/19AS11992Liberty Mobile Puerto Rico Inc.RPKI Не найдено64.213.224.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Сеть, широковещательный адрес, маски и число хостов для любого префикса.