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

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

Примеры:

2001:5f8::/32

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

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

2001:5f8::/32AS5056Aureon Network ServicesRPKI Не найдено2001:5f8::

Регистратура: ARIN · Соединенные Штаты · 9 мая 2003 г.
Выделенный блок: 2001:5f8:: – 2001:5f8:ffff:ffff:ffff:ffff:ffff:ffff

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

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

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

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

2001:5f8:300::/40AS397446Midwest Fiber Network, LLCRPKI Не найдено2001:5f8:300::
2001:5f8:700::/40AS5056Aureon Network ServicesRPKI Не найдено2001:5f8:700::
2001:5f8:b00::/40AS5056Aureon Network ServicesRPKI Не найдено2001:5f8:b00::
2001:5f8:7d09::/48AS5056Aureon Network ServicesRPKI Не найдено2001:5f8:7d09::
2001:5f8:7e03::/48AS5056Aureon Network ServicesRPKI Не найдено2001:5f8:7e03::
2001:5f8:7f09::/48AS5056Aureon Network ServicesRPKI Не найдено2001:5f8:7f09::
2001:5f8:7f0b::/48AS18883FiberNet Communications L.C.RPKI Не найдено2001:5f8:7f0b::
2001:5f8:7f0d::/48AS399693Northwest CommunicationsRPKI Не найдено2001:5f8:7f0d::
2001:5f8:7f10::/48AS5056Aureon Network ServicesRPKI Не найдено2001:5f8:7f10::
2001:5f8:7f11::/48AS5056Aureon Network ServicesRPKI Не найдено2001:5f8:7f11::
2001:5f8:7f14::/48AS5056Aureon Network ServicesRPKI Не найдено2001:5f8:7f14::
2001:5f8:7f24::/48AS5056Aureon Network ServicesRPKI Не найдено2001:5f8:7f24::
2001:5f8:7f26::/48AS5056Aureon Network ServicesRPKI Не найдено2001:5f8:7f26::
2001:5f8:7f27::/48AS5056Aureon Network ServicesRPKI Не найдено2001:5f8:7f27::
2001:5f8:8300::/40AS33690Aureon Network ServicesRPKI Не найдено2001:5f8:8300::
2001:5f8:fb31::/48AS5056Aureon Network ServicesRPKI Не найдено2001:5f8:fb31::
2001:5f8:fe02::/48AS5056Aureon Network ServicesRPKI Не найдено2001:5f8:fe02::
2001:5f8:fe03::/48AS5056Aureon Network ServicesRPKI Не найдено2001:5f8:fe03::
2001:5f8:fe04::/48AS5056Aureon Network ServicesRPKI Не найдено2001:5f8:fe04::

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

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.

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

См. также