Поиск префикса BGP

Введите префикс (или отдельный адрес). Ответ из нашей ежедневной копии глобальной таблицы маршрутизации.

Примеры:

220.88.0.0/14

Взгляд одного коллектора (APNIC). Маршрут, отфильтрованный до него, не показывается.

Анонсирован точно

220.88.0.0/14AS4766Korea TelecomRPKI Не найдено220.88.0.0

Регистратура: APNIC · Республика Корея · 29 авг. 2002 г.
Выделенный блок: 220.88.0.0 – 220.91.255.255

Покрывающие маршруты

Его не покрывает ни один менее специфичный маршрут.

Более специфичные маршруты

Более специфичных: 29 от исходных AS: 7

220.89.9.0/24AS4766Korea TelecomRPKI Не найдено220.89.9.0
220.89.62.0/24AS152232kt cloud Co., LtdRPKI Не найдено220.89.62.0
220.89.86.0/23AS4766Korea TelecomRPKI Не найдено220.89.86.0
220.90.25.0/24AS4766Korea TelecomRPKI Не найдено220.90.25.0
220.90.96.0/25AS4766Korea TelecomRPKI Не найдено220.90.96.0
220.90.97.0/24AS4766Korea TelecomRPKI Не найдено220.90.97.0
220.90.98.0/23AS4766Korea TelecomRPKI Не найдено220.90.98.0
220.90.100.0/22AS4766Korea TelecomRPKI Не найдено220.90.100.0
220.90.104.0/24AS4766Korea TelecomRPKI Не найдено220.90.104.0
220.90.105.0/24AS4766Korea TelecomRPKI Не найдено220.90.105.0
220.90.106.0/24AS4766Korea TelecomRPKI Не найдено220.90.106.0
220.90.107.0/24AS4766Korea TelecomRPKI Не найдено220.90.107.0
220.90.109.0/24AS4766Korea TelecomRPKI Не найдено220.90.109.0
220.90.110.0/24AS4766Korea TelecomRPKI Не найдено220.90.110.0
220.90.112.0/22AS4766Korea TelecomRPKI Не найдено220.90.112.0
220.90.116.0/24AS4766Korea TelecomRPKI Не найдено220.90.116.0
220.90.117.0/24AS9778DAEJIN UNIVERSITYRPKI Не найдено220.90.117.0
220.90.118.0/23AS9778DAEJIN UNIVERSITYRPKI Не найдено220.90.118.0
220.90.120.0/24AS9778DAEJIN UNIVERSITYRPKI Не найдено220.90.120.0
220.90.122.0/24AS38695bucheon universityRPKI Не найдено220.90.122.0
220.90.123.0/24AS38695bucheon universityRPKI Не найдено220.90.123.0
220.90.124.0/24AS38695bucheon universityRPKI Не найдено220.90.124.0
220.90.140.0/24AS4766Korea TelecomRPKI Не найдено220.90.140.0
220.90.166.0/24AS4766Korea TelecomRPKI Не найдено220.90.166.0
220.90.177.0/24AS9782WooSong UniversityRPKI Не найдено220.90.177.0
220.90.187.0/24AS9782WooSong UniversityRPKI Не найдено220.90.187.0
220.90.197.0/24AS9782WooSong UniversityRPKI Не найдено220.90.197.0
220.90.199.0/24AS55593netmarbleRPKI Не найдено220.90.199.0
220.90.250.0/23AS9949Hoseo UniversityRPKI Не найдено220.90.250.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.

Частые вопросы

См. также