Поиск префикса BGP
Введите префикс (или отдельный адрес). Ответ из нашей ежедневной копии глобальной таблицы маршрутизации.
206.228.0.0/14
Анонсирован точно
- 206.228.0.0/14AS174Cogent Communications, LLCRPKI Не найдено206.228.0.0
- Регистратура
- ARIN · Соединенные Штаты · 6 нояб. 1995 г.
- Выделенный блок
- 206.228.0.0 – 206.231.255.255
Покрывающие маршруты
Его не покрывает ни один менее специфичный маршрут.
Более специфичные маршруты
- 206.228.5.0/24AS400807BRYAN MUNICIPAL UTILITIESRPKI Не найдено206.228.5.0
- 206.228.96.0/20AS11398CenturyLink Communications, LLCRPKI Не найдено206.228.96.0
- 206.228.140.0/22AS11924Montana Opticom, LLCRPKI Не найдено206.228.140.0
- 206.228.201.0/24AS40320KROHNE, INC.RPKI Не найдено206.228.201.0
- 206.229.88.0/23AS18632Volcano Vision, Inc.RPKI Не найдено206.229.88.0
- 206.229.88.0/24AS18632Volcano Vision, Inc.RPKI Не найдено206.229.88.0
- 206.229.89.0/24AS18632Volcano Vision, Inc.RPKI Не найдено206.229.89.0
- 206.229.115.0/24AS33560Lincoln Investment Planning, LLC.RPKI Не найдено206.229.115.0
- 206.229.154.0/23AS174Cogent Communications, LLCRPKI Не найдено206.229.154.0
- 206.230.60.0/23AS32614High Desert Internet ServicesRPKI Не найдено206.230.60.0
- 206.230.70.0/24AS11676Conduent Business Services, LLCRPKI Не найдено206.230.70.0
- 206.230.104.0/21AS14828Hiawatha Broadband Communications, IncRPKI Не найдено206.230.104.0
- 206.230.192.0/20AS6079RCNRPKI Не найдено206.230.192.0
- 206.230.208.0/20AS6079RCNRPKI Не найдено206.230.208.0
- 206.230.224.0/20AS6079RCNRPKI Не найдено206.230.224.0
- 206.230.240.0/20AS6079RCNRPKI Не найдено206.230.240.0
- 206.231.8.0/22AS29968Dunkirk & Fredonia Telephone CompanyRPKI Не найдено206.231.8.0
- 206.231.8.0/24AS29968Dunkirk & Fredonia Telephone CompanyRPKI Не найдено206.231.8.0
- 206.231.10.0/24AS29968Dunkirk & Fredonia Telephone CompanyRPKI Не найдено206.231.10.0
- 206.231.44.0/24AS22742Connecticut Education NetworkRPKI Не найдено206.231.44.0
- 206.231.72.0/21AS3816COLOMBIA TELECOMUNICACIONES S.A. ESP BICRPKI Не найдено206.231.72.0
- 206.231.120.0/21AS14813Columbus Telecommunications (Barbados) LimitedRPKI Не найдено206.231.120.0
- 206.231.120.0/23AS14813Columbus Telecommunications (Barbados) LimitedRPKI Не найдено206.231.120.0
- 206.231.120.0/24AS14813Columbus Telecommunications (Barbados) LimitedRPKI Не найдено206.231.120.0
- 206.231.122.0/23AS14813Columbus Telecommunications (Barbados) LimitedRPKI Не найдено206.231.122.0
- 206.231.124.0/23AS14813Columbus Telecommunications (Barbados) LimitedRPKI Не найдено206.231.124.0
- 206.231.124.0/24AS14813Columbus Telecommunications (Barbados) LimitedRPKI Не найдено206.231.124.0
- 206.231.125.0/24AS14813Columbus Telecommunications (Barbados) LimitedRPKI Не найдено206.231.125.0
- 206.231.126.0/23AS14813Columbus Telecommunications (Barbados) LimitedRPKI Не найдено206.231.126.0
- 206.231.178.0/24AS7795LUMOS Networks, Inc.RPKI Не найдено206.231.178.0
- 206.231.179.0/24AS7795LUMOS Networks, Inc.RPKI Не найдено206.231.179.0
- 206.231.224.0/20AS3257GTT Communications Inc.RPKI Не найдено206.231.224.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Сеть, широковещательный адрес, маски и число хостов для любого префикса.