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

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

Примеры:

146.247.96.0/19

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

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

146.247.96.0/19AS57037Manuel Krebs trading as MKQ InternetserviceRPKI Действителен146.247.96.0

Регистратура: RIPE NCC · Германия · 15 июл. 2011 г.
Выделенный блок: 146.247.96.0 – 146.247.127.255

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

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

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

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

146.247.96.0/22AS57037Manuel Krebs trading as MKQ InternetserviceRPKI Действителен146.247.96.0
146.247.100.0/24AS57037Manuel Krebs trading as MKQ InternetserviceRPKI Действителен146.247.100.0
146.247.101.0/24AS31715CloudIP LLCRPKI Действителен146.247.101.0
146.247.102.0/24AS57037Manuel Krebs trading as MKQ InternetserviceRPKI Действителен146.247.102.0
146.247.103.0/24AS57037Manuel Krebs trading as MKQ InternetserviceRPKI Действителен146.247.103.0
146.247.105.0/24AS58061Scalaxy B.V.RPKI Действителен146.247.105.0
146.247.106.0/24AS61317Hivelocity LLCRPKI Действителен146.247.106.0
146.247.108.0/24AS201938Filiago Verwaltungsgesellschaft mbH trading as Filiago GmbH und Co. KGRPKI Действителен146.247.108.0
146.247.109.0/24AS2914NTT America, Inc.RPKI Действителен146.247.109.0
146.247.110.0/24AS58061Scalaxy B.V.RPKI Действителен146.247.110.0
146.247.112.0/23AS212238Datacamp LimitedRPKI Действителен146.247.112.0
146.247.114.0/24AS29802HIVELOCITY, Inc.RPKI Действителен146.247.114.0
146.247.118.0/24AS207821IN InternetNord GmbHRPKI Действителен146.247.118.0
146.247.123.0/24AS206092F.N.S. HOLDINGS LIMITEDRPKI Действителен146.247.123.0
146.247.124.0/23AS58061Scalaxy B.V.RPKI Действителен146.247.124.0
146.247.127.0/24AS29802HIVELOCITY, Inc.RPKI Действителен146.247.127.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.

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

См. также