Поиск префикса BGP
Введите префикс (или отдельный адрес). Ответ из нашей ежедневной копии глобальной таблицы маршрутизации.
46.61.0.0/16
Анонсирован точно
- 46.61.0.0/16AS12389PJSC RostelecomRPKI Действителен46.61.0.0
- Регистратура
- RIPE NCC · Россия · 22 окт. 2010 г.
- Выделенный блок
- 46.61.0.0 – 46.61.127.255
Покрывающие маршруты
Его не покрывает ни один менее специфичный маршрут.
Более специфичные маршруты
- 46.61.0.0/18AS12389PJSC RostelecomRPKI Действителен46.61.0.0
- 46.61.0.0/19AS12389PJSC RostelecomRPKI Действителен46.61.0.0
- 46.61.32.0/19AS12389PJSC RostelecomRPKI Действителен46.61.32.0
- 46.61.64.0/19AS12389PJSC RostelecomRPKI Действителен46.61.64.0
- 46.61.96.0/19AS12389PJSC RostelecomRPKI Действителен46.61.96.0
- 46.61.128.0/17AS12389PJSC RostelecomRPKI Действителен46.61.128.0
- 46.61.131.0/24AS12389PJSC RostelecomRPKI Действителен46.61.131.0
- 46.61.137.0/24AS21403RTK-SERVICE LLCRPKI Действителен46.61.137.0
- 46.61.149.0/24AS12389PJSC RostelecomRPKI Действителен46.61.149.0
- 46.61.150.0/24AS201776Miranda-Media LtdRPKI Действителен46.61.150.0
- 46.61.163.0/24AS12389PJSC RostelecomRPKI Действителен46.61.163.0
- 46.61.179.0/24AS12389PJSC RostelecomRPKI Действителен46.61.179.0
- 46.61.181.0/24AS212732JSC TsNIIMashRPKI Действителен46.61.181.0
- 46.61.184.0/24AS205576JSC FC Spartak-MoscowRPKI Действителен46.61.184.0
- 46.61.193.0/24AS12389PJSC RostelecomRPKI Действителен46.61.193.0
- 46.61.197.0/24AS12389PJSC RostelecomRPKI Действителен46.61.197.0
- 46.61.198.0/24AS12389PJSC RostelecomRPKI Действителен46.61.198.0
- 46.61.205.0/24AS12389PJSC RostelecomRPKI Действителен46.61.205.0
- 46.61.208.0/24AS12389PJSC RostelecomRPKI Действителен46.61.208.0
- 46.61.209.0/24AS205060Departament Smolenskoy oblasti po Informatsionnym tekhnologiyamRPKI Действителен46.61.209.0
- 46.61.230.0/24AS12389PJSC RostelecomRPKI Действителен46.61.230.0
- 46.61.231.0/24AS12389PJSC RostelecomRPKI Действителен46.61.231.0
- 46.61.232.0/24AS12389PJSC RostelecomRPKI Действителен46.61.232.0
- 46.61.234.0/24AS12389PJSC RostelecomRPKI Действителен46.61.234.0
- 46.61.237.0/24AS12389PJSC RostelecomRPKI Действителен46.61.237.0
- 46.61.239.0/24AS12389PJSC RostelecomRPKI Действителен46.61.239.0
- 46.61.245.0/24AS201776Miranda-Media LtdRPKI Действителен46.61.245.0
- 46.61.247.0/24AS12389PJSC RostelecomRPKI Действителен46.61.247.0
- 46.61.248.0/24AS12389PJSC RostelecomRPKI Действителен46.61.248.0
- 46.61.251.0/24AS12389PJSC RostelecomRPKI Действителен46.61.251.0
Этот текст пока недоступен на языке «русский». До публикации перевода он показан на языке «английский».
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 144.122.0.0/16 (Middle East Technical University, AS1967). 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Сеть, широковещательный адрес, маски и число хостов для любого префикса.