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

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

Примеры:

204.176.0.0/14

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

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

204.176.0.0/14AS701Verizon BusinessRPKI Не найдено204.176.0.0

Регистратура: ARIN · Соединенные Штаты · 17 окт. 1994 г.
Выделенный блок: 204.176.0.0 – 204.179.255.255

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

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

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

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

204.176.42.0/24AS15297EPLUS, Inc.RPKI Не найдено204.176.42.0
204.176.49.0/24AS10982TiVo, Inc.RPKI Не найдено204.176.49.0
204.176.96.0/24AS22574CocoNet CorporationRPKI Не найдено204.176.96.0
204.176.194.0/24AS40264Charter Communications LLCRPKI Не найдено204.176.194.0
204.176.204.0/24AS6220inContact Inc.RPKI Не найдено204.176.204.0
204.177.96.0/20AS7795LUMOS Networks, Inc.RPKI Не найдено204.177.96.0
204.177.181.0/24AS13666Verizon BusinessRPKI Не найдено204.177.181.0
204.177.184.0/21AS4208The Iserv Company, LLCRPKI Не найдено204.177.184.0
204.178.8.0/21AS6431AT&T Enterprises, LLCRPKI Не найдено204.178.8.0
204.179.65.0/24AS32806MTNSAT Holdings LLCRPKI Не найдено204.179.65.0
204.179.96.0/24AS16833Tullett Prebon Americas Corp.RPKI Действителен204.179.96.0
204.179.168.0/24AS397056AgWorks, LLCRPKI Действителен204.179.168.0
204.179.192.0/19AS29878Community Hospital of the Monterey PeninsulaRPKI Не найдено204.179.192.0
204.179.219.0/24AS29878Community Hospital of the Monterey PeninsulaRPKI Не найдено204.179.219.0
204.179.229.0/24AS12184Forrester ResearchRPKI Не найдено204.179.229.0
204.179.240.0/24AS10361Bloomberg, LPRPKI Действителен204.179.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, 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.

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

См. также