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

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

Примеры:

89.30.0.0/17

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

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

89.30.0.0/17AS4455IX Reach LtdRPKI Действителен89.30.0.0

Регистратура: RIPE NCC · Франция · 22 авг. 2006 г.
Выделенный блок: 89.30.0.0 – 89.30.127.255

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

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

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

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

89.30.5.0/24AS4455IX Reach LtdRPKI Действителен89.30.5.0
89.30.13.0/24AS4455IX Reach LtdRPKI Действителен89.30.13.0
89.30.14.0/24AS4455IX Reach LtdRPKI Действителен89.30.14.0
89.30.21.0/24AS4455IX Reach LtdRPKI Действителен89.30.21.0
89.30.25.0/24AS4455IX Reach LtdRPKI Действителен89.30.25.0
89.30.26.0/24AS4455IX Reach LtdRPKI Действителен89.30.26.0
89.30.36.0/24AS4455IX Reach LtdRPKI Действителен89.30.36.0
89.30.48.0/24AS4455IX Reach LtdRPKI Действителен89.30.48.0
89.30.56.0/24AS31216BSO Network Solutions SASRPKI Действителен89.30.56.0
89.30.57.0/24AS31216BSO Network Solutions SASRPKI Действителен89.30.57.0
89.30.58.0/24AS31216BSO Network Solutions SASRPKI Действителен89.30.58.0
89.30.66.0/24AS4455IX Reach LtdRPKI Действителен89.30.66.0
89.30.68.0/22AS4455IX Reach LtdRPKI Действителен89.30.68.0
89.30.68.0/24AS4455IX Reach LtdRPKI Действителен89.30.68.0
89.30.69.0/24AS4455IX Reach LtdRPKI Действителен89.30.69.0
89.30.79.0/24AS31216BSO Network Solutions SASRPKI Действителен89.30.79.0
89.30.84.0/24AS31216BSO Network Solutions SASRPKI Действителен89.30.84.0
89.30.87.0/24AS31216BSO Network Solutions SASRPKI Действителен89.30.87.0
89.30.106.0/24AS60331Une Vision Nouvelle de la Communication VINC SASRPKI Действителен89.30.106.0
89.30.113.0/24AS29646FFastFill Europe LimitedRPKI Действителен89.30.113.0
89.30.121.0/24AS4455IX Reach LtdRPKI Действителен89.30.121.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.

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

См. также