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

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

Примеры:

66.128.160.0/19

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

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

66.128.160.0/19AS13576SDN CommunicationsRPKI Действителен66.128.160.0

Регистратура: ARIN · Соединенные Штаты · 14 июн. 2001 г.
Выделенный блок: 66.128.160.0 – 66.128.191.255

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

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

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

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

66.128.161.0/24AS18785Santel Communications Cooperative, Inc.RPKI Действителен66.128.161.0
66.128.162.0/23AS15204INTERSTATE TELECOMMUNICATIONS COOPERATIVE, INC.RPKI Действителен66.128.162.0
66.128.164.0/23AS15204INTERSTATE TELECOMMUNICATIONS COOPERATIVE, INC.RPKI Действителен66.128.164.0
66.128.166.0/23AS13576SDN CommunicationsRPKI Действителен66.128.166.0
66.128.171.0/24AS13576SDN CommunicationsRPKI Действителен66.128.171.0
66.128.173.0/24AS13576SDN CommunicationsRPKI Действителен66.128.173.0
66.128.174.0/24AS13576SDN CommunicationsRPKI Действителен66.128.174.0
66.128.175.0/24AS13576SDN CommunicationsRPKI Действителен66.128.175.0
66.128.176.0/24AS13576SDN CommunicationsRPKI Действителен66.128.176.0
66.128.177.0/24AS398176JDS INDUSTRIES, INCRPKI Действителен66.128.177.0
66.128.178.0/24AS398112POET, LLCRPKI Действителен66.128.178.0
66.128.179.0/24AS13576SDN CommunicationsRPKI Действителен66.128.179.0
66.128.181.0/24AS46566CAPITAL Card Services, Inc.RPKI Действителен66.128.181.0
66.128.182.0/24AS15204INTERSTATE TELECOMMUNICATIONS COOPERATIVE, INC.RPKI Действителен66.128.182.0
66.128.183.0/24AS15204INTERSTATE TELECOMMUNICATIONS COOPERATIVE, INC.RPKI Действителен66.128.183.0
66.128.184.0/23AS15204INTERSTATE TELECOMMUNICATIONS COOPERATIVE, INC.RPKI Действителен66.128.184.0
66.128.188.0/24AS14675Plains Commerce BankRPKI Действителен66.128.188.0
66.128.189.0/24AS395037Sammons Financial Group, Inc.RPKI Действителен66.128.189.0

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

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.

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

См. также