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

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

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

Примеры:

156.75.0.0/17

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

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

  • 156.75.0.0/17AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Не найдено156.75.0.0
Регистратура
ARIN · Соединенные Штаты · 19 дек. 1991 г.
Выделенный блок
156.75.0.0 – 156.75.255.255

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

1
  • 156.75.0.0/16AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Не найдено156.75.0.0

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

Более специфичных: 24 от исходных AS: 1
  • 156.75.0.0/24AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Не найдено156.75.0.0
  • 156.75.1.0/24AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Не найдено156.75.1.0
  • 156.75.2.0/24AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Не найдено156.75.2.0
  • 156.75.3.0/24AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Не найдено156.75.3.0
  • 156.75.5.0/24AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Не найдено156.75.5.0
  • 156.75.6.0/24AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Не найдено156.75.6.0
  • 156.75.7.0/24AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Не найдено156.75.7.0
  • 156.75.10.0/24AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Не найдено156.75.10.0
  • 156.75.13.0/24AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Не найдено156.75.13.0
  • 156.75.14.0/24AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Не найдено156.75.14.0
  • 156.75.15.0/24AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Не найдено156.75.15.0
  • 156.75.16.0/21AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Не найдено156.75.16.0
  • 156.75.20.0/24AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Не найдено156.75.20.0
  • 156.75.24.0/23AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Не найдено156.75.24.0
  • 156.75.28.0/23AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Не найдено156.75.28.0
  • 156.75.30.0/24AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Не найдено156.75.30.0
  • 156.75.64.0/24AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Не найдено156.75.64.0
  • 156.75.65.0/24AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Не найдено156.75.65.0
  • 156.75.66.0/24AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Не найдено156.75.66.0
  • 156.75.67.0/24AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Не найдено156.75.67.0
  • 156.75.68.0/24AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Не найдено156.75.68.0
  • 156.75.69.0/24AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Не найдено156.75.69.0
  • 156.75.73.0/24AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Не найдено156.75.73.0
  • 156.75.75.0/24AS8103Florida Department of Management Services - Division of TelecommunicationsRPKI Не найдено156.75.75.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.

См. также