Поиск префикса BGP
Введите префикс (или отдельный адрес). Ответ из нашей ежедневной копии глобальной таблицы маршрутизации.
82.119.192.0/19
Анонсирован точно
- 82.119.192.0/19AS3257GTT Communications Inc.RPKI Действителен82.119.192.0
- Регистратура
- RIPE NCC · Италия · 17 февр. 2004 г.
- Выделенный блок
- 82.119.192.0 – 82.119.223.255
Покрывающие маршруты
Его не покрывает ни один менее специфичный маршрут.
Более специфичные маршруты
- 82.119.197.0/24AS5065Bunny CommunicationsRPKI Действителен82.119.197.0
- 82.119.200.0/24AS9009M247 Europe SRLRPKI Действителен82.119.200.0
- 82.119.201.0/24AS30058FDCservers.netRPKI Действителен82.119.201.0
- 82.119.202.0/24AS9009M247 Europe SRLRPKI Действителен82.119.202.0
- 82.119.203.0/24AS150423Server Galactic Private LimitedRPKI Действителен82.119.203.0
- 82.119.204.0/24AS13537Mega Colocation, Inc.RPKI Действителен82.119.204.0
- 82.119.207.0/24AS203410COLOBIX LTDRPKI Действителен82.119.207.0
- 82.119.208.0/23AS30058FDCservers.netRPKI Действителен82.119.208.0
- 82.119.210.0/23AS812Rogers Communications Canada Inc.RPKI Действителен82.119.210.0
- 82.119.212.0/23AS812Rogers Communications Canada Inc.RPKI Действителен82.119.212.0
- 82.119.214.0/23AS812Rogers Communications Canada Inc.RPKI Действителен82.119.214.0
- 82.119.216.0/23AS55470Cyfuture India Pvt. Ltd.RPKI Действителен82.119.216.0
- 82.119.218.0/23AS812Rogers Communications Canada Inc.RPKI Действителен82.119.218.0
- 82.119.220.0/23AS3320Deutsche Telekom AGRPKI Действителен82.119.220.0
- 82.119.222.0/23AS55470Cyfuture India Pvt. Ltd.RPKI Действителен82.119.222.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Сеть, широковещательный адрес, маски и число хостов для любого префикса.