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

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

Примеры:

2402:2700::/32

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

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

2402:2700::/32AS132061Realmove Company LimitedRPKI Не найдено2402:2700::

Регистратура: APNIC · Таиланд · 7 окт. 2011 г.
Выделенный блок: 2402:2700:: – 2402:2700:ffff:ffff:ffff:ffff:ffff:ffff

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

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

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

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

2402:2700::/33AS132061Realmove Company LimitedRPKI Не найдено2402:2700::
2402:2700:10::/48AS132061Realmove Company LimitedRPKI Не найдено2402:2700:10::
2402:2700:11::/48AS132061Realmove Company LimitedRPKI Не найдено2402:2700:11::
2402:2700:12::/48AS132061Realmove Company LimitedRPKI Не найдено2402:2700:12::
2402:2700:13::/48AS132061Realmove Company LimitedRPKI Не найдено2402:2700:13::
2402:2700:14::/48AS132061Realmove Company LimitedRPKI Не найдено2402:2700:14::
2402:2700:15::/48AS132061Realmove Company LimitedRPKI Не найдено2402:2700:15::
2402:2700:16::/48AS132061Realmove Company LimitedRPKI Не найдено2402:2700:16::
2402:2700:17::/48AS132061Realmove Company LimitedRPKI Не найдено2402:2700:17::
2402:2700:18::/48AS132061Realmove Company LimitedRPKI Не найдено2402:2700:18::
2402:2700:19::/48AS132061Realmove Company LimitedRPKI Не найдено2402:2700:19::
2402:2700:1a::/48AS132061Realmove Company LimitedRPKI Не найдено2402:2700:1a::
2402:2700:1b::/48AS132061Realmove Company LimitedRPKI Не найдено2402:2700:1b::
2402:2700:1c::/48AS132061Realmove Company LimitedRPKI Не найдено2402:2700:1c::
2402:2700:1d::/48AS132061Realmove Company LimitedRPKI Не найдено2402:2700:1d::
2402:2700:1e::/48AS132061Realmove Company LimitedRPKI Не найдено2402:2700:1e::
2402:2700:1f::/48AS132061Realmove Company LimitedRPKI Не найдено2402:2700:1f::
2402:2700:8000::/33AS132618Real Future Company LimitedRPKI Не найдено2402:2700:8000::

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

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.

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

См. также