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

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

Примеры:

65.88.0.0/14

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

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

65.88.0.0/14AS3356Level 3 Parent, LLCRPKI Не найдено65.88.0.0

Регистратура: ARIN · Соединенные Штаты · 21 дек. 2000 г.
Выделенный блок: 65.88.0.0 – 65.91.255.255

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

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

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

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

65.88.84.0/22AS62CyrusOne LLCRPKI Не найдено65.88.84.0
65.88.85.0/24AS401985Family DollarRPKI Не найдено65.88.85.0
65.88.88.0/23AS35999The New York Public Library, Astor, Lenox, and Tilden FoundationsRPKI Не найдено65.88.88.0
65.88.89.0/24AS35999The New York Public Library, Astor, Lenox, and Tilden FoundationsRPKI Не найдено65.88.89.0
65.88.96.0/20AS6621Hughes Network Systems, LLCRPKI Не найдено65.88.96.0
65.89.28.0/24AS14590Desert Schools Federal Credit UnionRPKI Не найдено65.89.28.0
65.89.172.0/24AS29946Union WirelessRPKI Не найдено65.89.172.0
65.89.173.0/24AS29946Union WirelessRPKI Не найдено65.89.173.0
65.89.176.0/23AS3356Level 3 Parent, LLCRPKI Не найдено65.89.176.0
65.89.208.0/23AS3356Level 3 Parent, LLCRPKI Не найдено65.89.208.0
65.90.11.0/24AS16574Gtek Computers LLCRPKI Не найдено65.90.11.0
65.90.67.0/24AS80General Electric CompanyRPKI Не найдено65.90.67.0
65.90.80.0/21AS62CyrusOne LLCRPKI Не найдено65.90.80.0
65.90.138.0/24AS32342Genex Services IncRPKI Не найдено65.90.138.0
65.91.11.0/24AS3356Level 3 Parent, LLCRPKI Не найдено65.91.11.0
65.91.162.0/24AS15065Slic Network Solutions, IncRPKI Не найдено65.91.162.0
65.91.196.0/24AS16574Gtek Computers LLCRPKI Не найдено65.91.196.0
65.91.197.0/24AS16574Gtek Computers LLCRPKI Не найдено65.91.197.0
65.91.198.0/24AS16574Gtek Computers LLCRPKI Не найдено65.91.198.0
65.91.199.0/24AS16574Gtek Computers LLCRPKI Не найдено65.91.199.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.

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

См. также