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

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

Примеры:

118.184.128.0/17

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

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

118.184.128.0/17AS23650AS Number for CHINANET jiangsu province backboneRPKI Действителен118.184.128.0

Регистратура: APNIC · Китай · 19 окт. 2007 г.
Выделенный блок: 118.184.128.0 – 118.184.255.255

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

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

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

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

118.184.128.0/21AS137702Nanjing, Jiangsu Province, P.R.China.RPKI Действителен118.184.128.0
118.184.136.0/21AS138950Jiangsu Wuxi International IDC networkRPKI Действителен118.184.136.0
118.184.144.0/21AS23650AS Number for CHINANET jiangsu province backboneRPKI Действителен118.184.144.0
118.184.160.0/21AS140293CHINATELECOM Jiangsu province Changzhou 5G networkRPKI Действителен118.184.160.0
118.184.168.0/21AS23650AS Number for CHINANET jiangsu province backboneRPKI Действителен118.184.168.0
118.184.176.0/21AS23650AS Number for CHINANET jiangsu province backboneRPKI Действителен118.184.176.0
118.184.184.0/21AS138950Jiangsu Wuxi International IDC networkRPKI Действителен118.184.184.0
118.184.192.0/21AS140293CHINATELECOM Jiangsu province Changzhou 5G networkRPKI Действителен118.184.192.0
118.184.208.0/21AS140293CHINATELECOM Jiangsu province Changzhou 5G networkRPKI Действителен118.184.208.0
118.184.216.0/21AS140293CHINATELECOM Jiangsu province Changzhou 5G networkRPKI Действителен118.184.216.0
118.184.240.0/21AS140293CHINATELECOM Jiangsu province Changzhou 5G networkRPKI Действителен118.184.240.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.

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

См. также