Поиск префикса BGP
Введите префикс (или отдельный адрес). Ответ из нашей ежедневной копии глобальной таблицы маршрутизации.
203.236.0.0/17
Анонсирован точно
- 203.236.0.0/17AS4766Korea TelecomRPKI Не найдено203.236.0.0
- Регистратура
- APNIC · Республика Корея · 29 сент. 1996 г.
- Выделенный блок
- 203.236.0.0 – 203.236.31.255
Покрывающие маршруты
Его не покрывает ни один менее специфичный маршрут.
Более специфичные маршруты
- 203.236.0.0/19AS9644SK TelecomRPKI Не найдено203.236.0.0
- 203.236.32.0/21AS9644SK TelecomRPKI Не найдено203.236.32.0
- 203.236.40.0/22AS9644SK TelecomRPKI Не найдено203.236.40.0
- 203.236.48.0/24AS55592Korea Data Telecommunication Co., Ltd.RPKI Не найдено203.236.48.0
- 203.236.64.0/24AS9696Oscar EnterpriseRPKI Не найдено203.236.64.0
- 203.236.65.0/24AS9696Oscar EnterpriseRPKI Не найдено203.236.65.0
- 203.236.66.0/24AS9696Oscar EnterpriseRPKI Не найдено203.236.66.0
- 203.236.67.0/24AS9696Oscar EnterpriseRPKI Не найдено203.236.67.0
- 203.236.68.0/24AS9696Oscar EnterpriseRPKI Не найдено203.236.68.0
- 203.236.69.0/24AS9696Oscar EnterpriseRPKI Не найдено203.236.69.0
- 203.236.70.0/24AS9696Oscar EnterpriseRPKI Не найдено203.236.70.0
- 203.236.71.0/24AS9696Oscar EnterpriseRPKI Не найдено203.236.71.0
- 203.236.72.0/24AS9696Oscar EnterpriseRPKI Не найдено203.236.72.0
- 203.236.73.0/24AS9696Oscar EnterpriseRPKI Не найдено203.236.73.0
- 203.236.74.0/24AS9490Oscar EnterpriseRPKI Не найдено203.236.74.0
- 203.236.76.0/24AS9696Oscar EnterpriseRPKI Не найдено203.236.76.0
- 203.236.78.0/24AS9696Oscar EnterpriseRPKI Не найдено203.236.78.0
- 203.236.79.0/24AS9696Oscar EnterpriseRPKI Не найдено203.236.79.0
- 203.236.80.0/24AS9575KCTCRPKI Не найдено203.236.80.0
- 203.236.80.0/25AS9575KCTCRPKI Не найдено203.236.80.0
- 203.236.80.128/25AS9575KCTCRPKI Не найдено203.236.80.128
- 203.236.84.0/24AS45399Hanjin Information Systems Telecommunication Co., LtdRPKI Не найдено203.236.84.0
- 203.236.120.0/24AS45989KL-Net Corp.RPKI Не найдено203.236.120.0
Этот текст пока недоступен на языке «русский». До публикации перевода он показан на языке «английский».
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 2.48.0.0/14. 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Сеть, широковещательный адрес, маски и число хостов для любого префикса.