Перейти к содержанию
ipaddress.co.il

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

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

Примеры:

132.64.0.0/13

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

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

  • 132.64.0.0/13AS378IUCC - Israel InterUniversity Computation CenterRPKI Не найдено132.64.0.0
Регистратура
RIPE NCC · Израиль · 1 янв. 1984 г.
Выделенный блок
132.64.0.0 – 132.65.255.255

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

0

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

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

Более специфичных: 13 от исходных AS: 1
  • 132.64.0.0/15AS378IUCC - Israel InterUniversity Computation CenterRPKI Действителен132.64.0.0
  • 132.66.0.0/15AS378IUCC - Israel InterUniversity Computation CenterRPKI Действителен132.66.0.0
  • 132.66.4.0/24AS378IUCC - Israel InterUniversity Computation CenterRPKI Действителен132.66.4.0
  • 132.66.7.0/24AS378IUCC - Israel InterUniversity Computation CenterRPKI Действителен132.66.7.0
  • 132.66.16.0/23AS378IUCC - Israel InterUniversity Computation CenterRPKI Действителен132.66.16.0
  • 132.66.32.0/23AS378IUCC - Israel InterUniversity Computation CenterRPKI Действителен132.66.32.0
  • 132.66.225.0/24AS378IUCC - Israel InterUniversity Computation CenterRPKI Действителен132.66.225.0
  • 132.66.251.0/24AS378IUCC - Israel InterUniversity Computation CenterRPKI Действителен132.66.251.0
  • 132.68.0.0/15AS378IUCC - Israel InterUniversity Computation CenterRPKI Действителен132.68.0.0
  • 132.68.1.0/24AS378IUCC - Israel InterUniversity Computation CenterRPKI Действителен132.68.1.0
  • 132.68.238.0/24AS378IUCC - Israel InterUniversity Computation CenterRPKI Действителен132.68.238.0
  • 132.68.239.0/24AS378IUCC - Israel InterUniversity Computation CenterRPKI Действителен132.68.239.0
  • 132.70.0.0/15AS378IUCC - Israel InterUniversity Computation CenterRPKI Действителен132.70.0.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.

См. также