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

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

Примеры:

143.46.0.0/16

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

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

143.46.0.0/16AS1637Headquarters, USAISCRPKI Не найдено143.46.0.0

Регистратура: ARIN · Соединенные Штаты · 26 мар. 1990 г.
Выделенный блок: 143.46.0.0 – 143.46.255.255

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

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

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

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

143.46.5.0/24AS1637Headquarters, USAISCRPKI Не найдено143.46.5.0
143.46.8.0/23AS1637Headquarters, USAISCRPKI Не найдено143.46.8.0
143.46.10.0/24AS1637Headquarters, USAISCRPKI Не найдено143.46.10.0
143.46.11.0/24AS1637Headquarters, USAISCRPKI Не найдено143.46.11.0
143.46.12.0/24AS1637Headquarters, USAISCRPKI Не найдено143.46.12.0
143.46.17.0/24AS1637Headquarters, USAISCRPKI Не найдено143.46.17.0
143.46.18.0/24AS1637Headquarters, USAISCRPKI Не найдено143.46.18.0
143.46.20.0/24AS1637Headquarters, USAISCRPKI Не найдено143.46.20.0
143.46.21.0/24AS1637Headquarters, USAISCRPKI Не найдено143.46.21.0
143.46.22.0/24AS1637Headquarters, USAISCRPKI Не найдено143.46.22.0
143.46.23.0/24AS1637Headquarters, USAISCRPKI Не найдено143.46.23.0
143.46.24.0/24AS1637Headquarters, USAISCRPKI Не найдено143.46.24.0
143.46.25.0/24AS1637Headquarters, USAISCRPKI Не найдено143.46.25.0
143.46.26.0/24AS1637Headquarters, USAISCRPKI Не найдено143.46.26.0
143.46.27.0/24AS1637Headquarters, USAISCRPKI Не найдено143.46.27.0
143.46.32.0/24AS1637Headquarters, USAISCRPKI Не найдено143.46.32.0
143.46.33.0/24AS1637Headquarters, USAISCRPKI Не найдено143.46.33.0
143.46.34.0/24AS1637Headquarters, USAISCRPKI Не найдено143.46.34.0
143.46.35.0/24AS1637Headquarters, USAISCRPKI Не найдено143.46.35.0
143.46.36.0/24AS1637Headquarters, USAISCRPKI Не найдено143.46.36.0
143.46.37.0/24AS1637Headquarters, USAISCRPKI Не найдено143.46.37.0
143.46.39.0/24AS1637Headquarters, USAISCRPKI Не найдено143.46.39.0
143.46.48.0/24AS1637Headquarters, USAISCRPKI Не найдено143.46.48.0
143.46.49.0/24AS1637Headquarters, USAISCRPKI Не найдено143.46.49.0
143.46.50.0/24AS1637Headquarters, USAISCRPKI Не найдено143.46.50.0
143.46.51.0/24AS1637Headquarters, USAISCRPKI Не найдено143.46.51.0
143.46.53.0/24AS1637Headquarters, USAISCRPKI Не найдено143.46.53.0
143.46.60.0/24AS1637Headquarters, USAISCRPKI Не найдено143.46.60.0
143.46.110.0/24AS1637Headquarters, USAISCRPKI Не найдено143.46.110.0
143.46.116.0/22AS1637Headquarters, USAISCRPKI Не найдено143.46.116.0
143.46.120.0/22AS1637Headquarters, USAISCRPKI Не найдено143.46.120.0
143.46.128.0/23AS1637Headquarters, USAISCRPKI Не найдено143.46.128.0
143.46.130.0/23AS1637Headquarters, USAISCRPKI Не найдено143.46.130.0
143.46.134.0/23AS1637Headquarters, USAISCRPKI Не найдено143.46.134.0
143.46.140.0/24AS1637Headquarters, USAISCRPKI Не найдено143.46.140.0
143.46.141.0/24AS1637Headquarters, USAISCRPKI Не найдено143.46.141.0
143.46.142.0/24AS1637Headquarters, USAISCRPKI Не найдено143.46.142.0
143.46.143.0/24AS1637Headquarters, USAISCRPKI Не найдено143.46.143.0
143.46.144.0/24AS1637Headquarters, USAISCRPKI Не найдено143.46.144.0
143.46.145.0/24AS1637Headquarters, USAISCRPKI Не найдено143.46.145.0
143.46.146.0/24AS1637Headquarters, USAISCRPKI Не найдено143.46.146.0
143.46.147.0/24AS1637Headquarters, USAISCRPKI Не найдено143.46.147.0
143.46.150.0/24AS1637Headquarters, USAISCRPKI Не найдено143.46.150.0
143.46.151.0/24AS1637Headquarters, USAISCRPKI Не найдено143.46.151.0
143.46.158.0/24AS1637Headquarters, USAISCRPKI Не найдено143.46.158.0
143.46.161.0/24AS1637Headquarters, USAISCRPKI Не найдено143.46.161.0
143.46.164.0/22AS1637Headquarters, USAISCRPKI Не найдено143.46.164.0
143.46.190.0/24AS1637Headquarters, USAISCRPKI Не найдено143.46.190.0
143.46.210.0/24AS1637Headquarters, USAISCRPKI Не найдено143.46.210.0
143.46.229.0/24AS1637Headquarters, USAISCRPKI Не найдено143.46.229.0
143.46.240.0/24AS1637Headquarters, USAISCRPKI Не найдено143.46.240.0
143.46.253.0/24AS1637Headquarters, USAISCRPKI Не найдено143.46.253.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.

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

См. также