Поиск префикса BGP
Введите префикс (или отдельный адрес). Ответ из нашей ежедневной копии глобальной таблицы маршрутизации.
183.96.0.0/13
Анонсирован точно
- 183.96.0.0/13AS4766Korea TelecomRPKI Не найдено183.96.0.0
- Регистратура
- APNIC · Республика Корея · 4 нояб. 2009 г.
- Выделенный блок
- 183.96.0.0 – 183.127.255.255
Покрывающие маршруты
Его не покрывает ни один менее специфичный маршрут.
Более специфичные маршруты
- 183.96.231.0/24AS38663NICEINFOMATIONSERVICERPKI Не найдено183.96.231.0
- 183.96.247.0/24AS152207KART, KIDIRPKI Не найдено183.96.247.0
- 183.98.125.0/24AS9696Oscar EnterpriseRPKI Не найдено183.98.125.0
- 183.98.147.0/24AS9696Oscar EnterpriseRPKI Не найдено183.98.147.0
- 183.98.225.0/24AS9856WOORI Investment @ SecuritiesRPKI Не найдено183.98.225.0
- 183.98.230.0/24AS9696Oscar EnterpriseRPKI Не найдено183.98.230.0
- 183.98.241.0/24AS9696Oscar EnterpriseRPKI Не найдено183.98.241.0
- 183.98.243.0/24AS9696Oscar EnterpriseRPKI Не найдено183.98.243.0
- 183.98.254.0/24AS9696Oscar EnterpriseRPKI Не найдено183.98.254.0
- 183.101.94.0/24AS38693Korea Transportation Safety AuthorityRPKI Не найдено183.101.94.0
- 183.101.95.0/24AS38693Korea Transportation Safety AuthorityRPKI Не найдено183.101.95.0
- 183.101.125.0/24AS131094HYUNDAI MOTOR CORPKI Не найдено183.101.125.0
- 183.101.229.0/24AS38676flexnetworksRPKI Не найдено183.101.229.0
- 183.102.25.0/24AS23556ININextRPKI Не найдено183.102.25.0
- 183.102.26.0/24AS23556ININextRPKI Не найдено183.102.26.0
- 183.102.77.0/24AS9526KOSCOMRPKI Не найдено183.102.77.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Сеть, широковещательный адрес, маски и число хостов для любого префикса.