Поиск префикса BGP
Введите префикс (или отдельный адрес). Ответ из нашей ежедневной копии глобальной таблицы маршрутизации.
206.158.0.0/15
Анонсирован точно
- 206.158.0.0/15AS174Cogent Communications, LLCRPKI Не найдено206.158.0.0
- Регистратура
- ARIN · Соединенные Штаты · 6 окт. 1995 г.
- Выделенный блок
- 206.158.0.0 – 206.159.255.255
Покрывающие маршруты
Его не покрывает ни один менее специфичный маршрут.
Более специфичные маршруты
- 206.158.2.0/24AS15142Automated Data Systems, IncRPKI Не найдено206.158.2.0
- 206.158.4.0/22AS32614High Desert Internet ServicesRPKI Не найдено206.158.4.0
- 206.158.62.0/23AS21729Crown Equipment CorporationRPKI Не найдено206.158.62.0
- 206.158.128.0/20AS11404Wave BroadbandRPKI Не найдено206.158.128.0
- 206.158.144.0/20AS11404Wave BroadbandRPKI Не найдено206.158.144.0
- 206.158.160.0/20AS11404Wave BroadbandRPKI Не найдено206.158.160.0
- 206.158.176.0/20AS11404Wave BroadbandRPKI Не найдено206.158.176.0
- 206.158.192.0/20AS11404Wave BroadbandRPKI Не найдено206.158.192.0
- 206.158.208.0/20AS11404Wave BroadbandRPKI Не найдено206.158.208.0
- 206.158.224.0/20AS11404Wave BroadbandRPKI Не найдено206.158.224.0
- 206.158.240.0/20AS11404Wave BroadbandRPKI Не найдено206.158.240.0
- 206.159.0.0/20AS11404Wave BroadbandRPKI Не найдено206.159.0.0
- 206.159.16.0/20AS7459Grande Communications Networks, LLCRPKI Не найдено206.159.16.0
- 206.159.32.0/20AS6079RCNRPKI Не найдено206.159.32.0
- 206.159.48.0/20AS6079RCNRPKI Не найдено206.159.48.0
- 206.159.118.0/23AS32614High Desert Internet ServicesRPKI Не найдено206.159.118.0
- 206.159.152.0/21AS29968Dunkirk & Fredonia Telephone CompanyRPKI Не найдено206.159.152.0
- 206.159.152.0/23AS29968Dunkirk & Fredonia Telephone CompanyRPKI Не найдено206.159.152.0
- 206.159.154.0/23AS29968Dunkirk & Fredonia Telephone CompanyRPKI Не найдено206.159.154.0
- 206.159.156.0/23AS29968Dunkirk & Fredonia Telephone CompanyRPKI Не найдено206.159.156.0
- 206.159.158.0/23AS29968Dunkirk & Fredonia Telephone CompanyRPKI Не найдено206.159.158.0
- 206.159.160.0/21AS29968Dunkirk & Fredonia Telephone CompanyRPKI Не найдено206.159.160.0
- 206.159.160.0/23AS29968Dunkirk & Fredonia Telephone CompanyRPKI Не найдено206.159.160.0
- 206.159.162.0/23AS29968Dunkirk & Fredonia Telephone CompanyRPKI Не найдено206.159.162.0
- 206.159.164.0/23AS29968Dunkirk & Fredonia Telephone CompanyRPKI Не найдено206.159.164.0
- 206.159.166.0/23AS29968Dunkirk & Fredonia Telephone CompanyRPKI Не найдено206.159.166.0
- 206.159.176.0/20AS11398CenturyLink Communications, LLCRPKI Не найдено206.159.176.0
- 206.159.192.0/18AS2828Verizon BusinessRPKI Не найдено206.159.192.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Сеть, широковещательный адрес, маски и число хостов для любого префикса.