Поиск префикса BGP
Введите префикс (или отдельный адрес). Ответ из нашей ежедневной копии глобальной таблицы маршрутизации.
204.118.0.0/15
Анонсирован точно
- 204.118.0.0/15AS174Cogent Communications, LLCRPKI Не найдено204.118.0.0
- Регистратура
- ARIN · Соединенные Штаты · 12 авг. 1994 г.
- Выделенный блок
- 204.118.0.0 – 204.119.255.255
Покрывающие маршруты
Его не покрывает ни один менее специфичный маршрут.
Более специфичные маршруты
- 204.118.7.0/24AS1906Northrop GrummanRPKI Не найдено204.118.7.0
- 204.118.19.0/24AS54239BLOOMINGDALE HOME TELEPHONE COMPANY, INCRPKI Не найдено204.118.19.0
- 204.118.31.0/24AS174Cogent Communications, LLCRPKI Не найдено204.118.31.0
- 204.118.48.0/24AS40056Westgate Resorts LtdRPKI Не найдено204.118.48.0
- 204.118.63.0/24AS4972UNITED PARCEL SERVICERPKI Не найдено204.118.63.0
- 204.118.64.0/21AS26133Frankfort Plant BoardRPKI Не найдено204.118.64.0
- 204.118.72.0/21AS26133Frankfort Plant BoardRPKI Не найдено204.118.72.0
- 204.118.120.0/23AS15227LUMOS Networks, Inc.RPKI Не найдено204.118.120.0
- 204.119.0.0/23AS11404Wave BroadbandRPKI Не найдено204.119.0.0
- 204.119.3.0/24AS12044Willamette Valley InternetRPKI Не найдено204.119.3.0
- 204.119.24.0/24AS400317GoldConnectRPKI Действителен204.119.24.0
- 204.119.27.0/24AS400317GoldConnectRPKI Не найдено204.119.27.0
- 204.119.60.0/24AS400317GoldConnectRPKI Не найдено204.119.60.0
- 204.119.64.0/18AS2828Verizon BusinessRPKI Не найдено204.119.64.0
- 204.119.138.0/23AS394601Global NexusRPKI Не найдено204.119.138.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.
См. также
- Проверка маршрута RPKIАвторизована ли исходная AS маршрута в ROA?
- Поиск ASNВладелец, регистратура и все префиксы, которые анонсирует AS.
- Поиск по IPASN, провайдер, маршрут, обратный DNS и местоположение любого адреса.
- Калькулятор CIDRСеть, широковещательный адрес, маски и число хостов для любого префикса.