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

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

Примеры:

2a05:4a40:fff0::/44

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

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

2a05:4a40:fff0::/44AS2571DHL Information Services (Europe) s.r.oRPKI Не найдено2a05:4a40:fff0::

Регистратура: RIPE NCC · Чехия · 11 янв. 2016 г.
Выделенный блок: 2a05:4a40:: – 2a05:4a47:ffff:ffff:ffff:ffff:ffff:ffff

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

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

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

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

2a05:4a40:fff0::/48AS2571DHL Information Services (Europe) s.r.oRPKI Не найдено2a05:4a40:fff0::
2a05:4a40:fff1::/48AS2571DHL Information Services (Europe) s.r.oRPKI Не найдено2a05:4a40:fff1::
2a05:4a40:fff2::/48AS2571DHL Information Services (Europe) s.r.oRPKI Не найдено2a05:4a40:fff2::
2a05:4a40:fff3::/48AS19905Vercara, LLCRPKI Не найдено2a05:4a40:fff3::
2a05:4a40:fff4::/48AS2571DHL Information Services (Europe) s.r.oRPKI Не найдено2a05:4a40:fff4::
2a05:4a40:fff5::/48AS2571DHL Information Services (Europe) s.r.oRPKI Не найдено2a05:4a40:fff5::
2a05:4a40:fff6::/48AS2571DHL Information Services (Europe) s.r.oRPKI Не найдено2a05:4a40:fff6::
2a05:4a40:fff7::/48AS2571DHL Information Services (Europe) s.r.oRPKI Не найдено2a05:4a40:fff7::
2a05:4a40:fff8::/48AS2571DHL Information Services (Europe) s.r.oRPKI Не найдено2a05:4a40:fff8::
2a05:4a40:fff9::/48AS2571DHL Information Services (Europe) s.r.oRPKI Не найдено2a05:4a40:fff9::
2a05:4a40:fffa::/48AS2571DHL Information Services (Europe) s.r.oRPKI Не найдено2a05:4a40:fffa::
2a05:4a40:fffb::/48AS2571DHL Information Services (Europe) s.r.oRPKI Не найдено2a05:4a40:fffb::
2a05:4a40:fffc::/48AS2571DHL Information Services (Europe) s.r.oRPKI Не найдено2a05:4a40:fffc::
2a05:4a40:fffd::/48AS19905Vercara, LLCRPKI Не найдено2a05:4a40:fffd::
2a05:4a40:fffe::/48AS2571DHL Information Services (Europe) s.r.oRPKI Не найдено2a05:4a40:fffe::
2a05:4a40:ffff::/48AS2571DHL Information Services (Europe) s.r.oRPKI Не найдено2a05:4a40:ffff::

Этот текст пока недоступен на языке «русский». До публикации перевода он показан на языке «английский».

On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 144.122.0.0/16 (Middle East Technical University, AS1967). 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.

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

См. также