Поиск префикса BGP
Введите префикс (или отдельный адрес). Ответ из нашей ежедневной копии глобальной таблицы маршрутизации.
77.79.192.0/18
Анонсирован точно
- 77.79.192.0/18AS15694Atman Sp. z o.o.RPKI Действителен77.79.192.0
- Регистратура
- RIPE NCC · Польша · 14 мар. 2007 г.
- Выделенный блок
- 77.79.192.0 – 77.79.255.255
Покрывающие маршруты
Его не покрывает ни один менее специфичный маршрут.
Более специфичные маршруты
- 77.79.198.0/24AS24723Atman Sp. z o.o.RPKI Действителен77.79.198.0
- 77.79.200.0/24AS15694Atman Sp. z o.o.RPKI Действителен77.79.200.0
- 77.79.204.0/24AS201615ARISE Services S.A.RPKI Действителен77.79.204.0
- 77.79.205.0/24AS41097CENTRUM ELEKTRONICZNYCH USLUG PLATNICZYCH "ESERVICE" SARPKI Действителен77.79.205.0
- 77.79.207.0/24AS202904Softman S.A.RPKI Действителен77.79.207.0
- 77.79.210.0/24AS15694Atman Sp. z o.o.RPKI Действителен77.79.210.0
- 77.79.215.0/24AS15694Atman Sp. z o.o.RPKI Действителен77.79.215.0
- 77.79.221.0/24AS15694Atman Sp. z o.o.RPKI Действителен77.79.221.0
- 77.79.226.0/24AS28893Trecom-ASRPKI Действителен77.79.226.0
- 77.79.227.0/24AS57367Atman Sp. z o.o.RPKI Действителен77.79.227.0
- 77.79.230.0/23AS197474ASECUREXRPKI Действителен77.79.230.0
- 77.79.237.0/24AS24929IT arte Sp. z o.o.RPKI Действителен77.79.237.0
- 77.79.243.0/24AS207206DATAART POLAND SPOLKA Z OGRANICZONA ODPOWIEDZIALNOSCIARPKI Действителен77.79.243.0
- 77.79.244.0/22AS34342Atman Sp. z o.o.RPKI Действителен77.79.244.0
- 77.79.248.0/24AS57367Atman Sp. z o.o.RPKI Действителен77.79.248.0
- 77.79.249.0/24AS202081GOG sp. z o.oRPKI Действителен77.79.249.0
- 77.79.250.0/24AS57367Atman Sp. z o.o.RPKI Действителен77.79.250.0
- 77.79.253.0/24AS197722IBK Bank Polska S.A.RPKI Действителен77.79.253.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Сеть, широковещательный адрес, маски и число хостов для любого префикса.