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

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

Примеры:

209.148.32.0/19

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

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

209.148.32.0/19AS27506Crown Castle Fiber LLCRPKI Не найдено209.148.32.0

Регистратура: ARIN · Соединенные Штаты · 3 апр. 2008 г.
Выделенный блок: 209.148.32.0 – 209.148.63.255

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

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

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

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

209.148.32.0/20AS27506Crown Castle Fiber LLCRPKI Не найдено209.148.32.0
209.148.32.0/22AS46887Crown Castle Fiber LLCRPKI Не найдено209.148.32.0
209.148.36.0/22AS46887Crown Castle Fiber LLCRPKI Не найдено209.148.36.0
209.148.40.0/22AS46887Crown Castle Fiber LLCRPKI Не найдено209.148.40.0
209.148.40.0/24AS23004VIEWTRADE SECURITIESRPKI Не найдено209.148.40.0
209.148.43.0/24AS22042Flow Traders US LLCRPKI Не найдено209.148.43.0
209.148.44.0/22AS46887Crown Castle Fiber LLCRPKI Не найдено209.148.44.0
209.148.46.0/24AS46887Crown Castle Fiber LLCRPKI Не найдено209.148.46.0
209.148.48.0/20AS27506Crown Castle Fiber LLCRPKI Не найдено209.148.48.0
209.148.48.0/22AS46887Crown Castle Fiber LLCRPKI Не найдено209.148.48.0
209.148.52.0/22AS46887Crown Castle Fiber LLCRPKI Не найдено209.148.52.0
209.148.56.0/24AS46887Crown Castle Fiber LLCRPKI Не найдено209.148.56.0
209.148.57.0/24AS11490UNASSIGNEDRPKI Не найдено209.148.57.0
209.148.58.0/23AS46887Crown Castle Fiber LLCRPKI Не найдено209.148.58.0
209.148.59.0/24AS46887Crown Castle Fiber LLCRPKI Не найдено209.148.59.0
209.148.60.0/22AS46887Crown Castle Fiber LLCRPKI Не найдено209.148.60.0
209.148.61.0/24AS36193Walleye Capital LLCRPKI Не найдено209.148.61.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.

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

См. также