Поиск префикса BGP
Введите префикс (или отдельный адрес). Ответ из нашей ежедневной копии глобальной таблицы маршрутизации.
74.3.128.0/18
Анонсирован точно
- 74.3.128.0/18AS6327Shaw CommunicationsRPKI Не найдено74.3.128.0
- Регистратура
- ARIN · Канада · 20 мая 2009 г.
- Выделенный блок
- 74.3.128.0 – 74.3.191.255
Покрывающие маршруты
Его не покрывает ни один менее специфичный маршрут.
Более специфичные маршруты
- 74.3.128.0/21AS6327Shaw CommunicationsRPKI Не найдено74.3.128.0
- 74.3.132.0/24AS6327Shaw CommunicationsRPKI Не найдено74.3.132.0
- 74.3.133.0/24AS6327Shaw CommunicationsRPKI Не найдено74.3.133.0
- 74.3.136.0/21AS6327Shaw CommunicationsRPKI Не найдено74.3.136.0
- 74.3.144.0/21AS6327Shaw CommunicationsRPKI Не найдено74.3.144.0
- 74.3.144.0/22AS10980Stafford Communications, Inc.RPKI Не найдено74.3.144.0
- 74.3.144.0/24AS10980Stafford Communications, Inc.RPKI Не найдено74.3.144.0
- 74.3.145.0/24AS10980Stafford Communications, Inc.RPKI Не найдено74.3.145.0
- 74.3.146.0/24AS10980Stafford Communications, Inc.RPKI Не найдено74.3.146.0
- 74.3.147.0/24AS10980Stafford Communications, Inc.RPKI Не найдено74.3.147.0
- 74.3.148.0/24AS30500Wolfpaw Data Centres IncRPKI Не найдено74.3.148.0
- 74.3.149.0/24AS30500Wolfpaw Data Centres IncRPKI Не найдено74.3.149.0
- 74.3.150.0/24AS398285Peace Region Internet SocietyRPKI Не найдено74.3.150.0
- 74.3.151.0/24AS30500Wolfpaw Data Centres IncRPKI Не найдено74.3.151.0
- 74.3.152.0/22AS6327Shaw CommunicationsRPKI Не найдено74.3.152.0
- 74.3.156.0/23AS6327Shaw CommunicationsRPKI Не найдено74.3.156.0
- 74.3.158.0/24AS6327Shaw CommunicationsRPKI Не найдено74.3.158.0
- 74.3.159.0/24AS6327Shaw CommunicationsRPKI Не найдено74.3.159.0
- 74.3.160.0/20AS6327Shaw CommunicationsRPKI Не найдено74.3.160.0
- 74.3.160.0/24AS11831eSecureDataRPKI Не найдено74.3.160.0
- 74.3.161.0/24AS11831eSecureDataRPKI Не найдено74.3.161.0
- 74.3.162.0/24AS11831eSecureDataRPKI Не найдено74.3.162.0
- 74.3.163.0/24AS11831eSecureDataRPKI Не найдено74.3.163.0
- 74.3.164.0/24AS11831eSecureDataRPKI Не найдено74.3.164.0
- 74.3.165.0/24AS11831eSecureDataRPKI Не найдено74.3.165.0
- 74.3.166.0/24AS11831eSecureDataRPKI Не найдено74.3.166.0
- 74.3.167.0/24AS11831eSecureDataRPKI Не найдено74.3.167.0
- 74.3.168.0/24AS11831eSecureDataRPKI Не найдено74.3.168.0
- 74.3.171.0/24AS11831eSecureDataRPKI Не найдено74.3.171.0
- 74.3.172.0/24AS11831eSecureDataRPKI Не найдено74.3.172.0
- 74.3.173.0/24AS11831eSecureDataRPKI Не найдено74.3.173.0
- 74.3.174.0/24AS11831eSecureDataRPKI Не найдено74.3.174.0
- 74.3.175.0/24AS11831eSecureDataRPKI Не найдено74.3.175.0
- 74.3.176.0/21AS6327Shaw CommunicationsRPKI Не найдено74.3.176.0
- 74.3.176.0/23AS6327Shaw CommunicationsRPKI Не найдено74.3.176.0
- 74.3.184.0/21AS6327Shaw CommunicationsRPKI Не найдено74.3.184.0
- 74.3.186.0/24AS63052Columbia Basin Broadband CorporationRPKI Не найдено74.3.186.0
- 74.3.187.0/24AS29988Rogers Communications Canada Inc.RPKI Не найдено74.3.187.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.
См. также
- Проверка маршрута RPKIАвторизована ли исходная AS маршрута в ROA?
- Поиск ASNВладелец, регистратура и все префиксы, которые анонсирует AS.
- Поиск по IPASN, провайдер, маршрут, обратный DNS и местоположение любого адреса.
- Калькулятор CIDRСеть, широковещательный адрес, маски и число хостов для любого префикса.