Поиск префикса BGP
Введите префикс (или отдельный адрес). Ответ из нашей ежедневной копии глобальной таблицы маршрутизации.
220.116.0.0/14
Анонсирован точно
- 220.116.0.0/14AS4766Korea TelecomRPKI Не найдено220.116.0.0
- Регистратура
- APNIC · Республика Корея · 31 дек. 2002 г.
- Выделенный блок
- 220.116.0.0 – 220.119.255.255
Покрывающие маршруты
Его не покрывает ни один менее специфичный маршрут.
Более специфичные маршруты
- 220.116.28.0/24AS38113KUMCRPKI Не найдено220.116.28.0
- 220.116.29.0/24AS38113KUMCRPKI Не найдено220.116.29.0
- 220.116.32.0/24AS38113KUMCRPKI Не найдено220.116.32.0
- 220.116.204.0/22AS4766Korea TelecomRPKI Не найдено220.116.204.0
- 220.116.230.0/24AS4766Korea TelecomRPKI Не найдено220.116.230.0
- 220.118.52.0/24AS9948NICE TCMRPKI Не найдено220.118.52.0
- 220.118.156.0/24AS23556ININextRPKI Не найдено220.118.156.0
- 220.119.44.0/23AS9870DONG-EUI UNIVERSITYRPKI Не найдено220.119.44.0
- 220.119.44.0/24AS9870DONG-EUI UNIVERSITYRPKI Не найдено220.119.44.0
- 220.119.45.0/24AS9870DONG-EUI UNIVERSITYRPKI Не найдено220.119.45.0
- 220.119.46.0/24AS9870DONG-EUI UNIVERSITYRPKI Не найдено220.119.46.0
- 220.119.46.0/25AS9870DONG-EUI UNIVERSITYRPKI Не найдено220.119.46.0
- 220.119.46.128/25AS9870DONG-EUI UNIVERSITYRPKI Не найдено220.119.46.128
- 220.119.248.0/24AS9631youngsan universityRPKI Не найдено220.119.248.0
- 220.119.249.0/24AS9631youngsan universityRPKI Не найдено220.119.249.0
- 220.119.250.0/24AS9631youngsan universityRPKI Не найдено220.119.250.0
- 220.119.251.0/24AS9631youngsan universityRPKI Не найдено220.119.251.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Сеть, широковещательный адрес, маски и число хостов для любого префикса.