Поиск префикса BGP
Введите префикс (или отдельный адрес). Ответ из нашей ежедневной копии глобальной таблицы маршрутизации.
203.231.224.0/19
Анонсирован точно
- 203.231.224.0/19AS9848SEJONG NETWORKSRPKI Не найдено203.231.224.0
- Регистратура
- APNIC · Республика Корея · 23 апр. 1996 г.
- Выделенный блок
- 203.231.0.0 – 203.231.255.255
Покрывающие маршруты
- 203.231.0.0/16AS9848SEJONG NETWORKSRPKI Не найдено203.231.0.0
Более специфичные маршруты
- 203.231.224.0/24AS17881Inet Hosting, Inc.RPKI Не найдено203.231.224.0
- 203.231.225.0/24AS17881Inet Hosting, Inc.RPKI Не найдено203.231.225.0
- 203.231.226.0/24AS17881Inet Hosting, Inc.RPKI Не найдено203.231.226.0
- 203.231.227.0/24AS17881Inet Hosting, Inc.RPKI Не найдено203.231.227.0
- 203.231.228.0/24AS17881Inet Hosting, Inc.RPKI Не найдено203.231.228.0
- 203.231.229.0/24AS17881Inet Hosting, Inc.RPKI Не найдено203.231.229.0
- 203.231.230.0/24AS17881Inet Hosting, Inc.RPKI Не найдено203.231.230.0
- 203.231.231.0/24AS17881Inet Hosting, Inc.RPKI Не найдено203.231.231.0
- 203.231.232.0/24AS17881Inet Hosting, Inc.RPKI Не найдено203.231.232.0
- 203.231.233.0/24AS17881Inet Hosting, Inc.RPKI Не найдено203.231.233.0
- 203.231.234.0/24AS17881Inet Hosting, Inc.RPKI Не найдено203.231.234.0
- 203.231.235.0/24AS17881Inet Hosting, Inc.RPKI Не найдено203.231.235.0
- 203.231.236.0/24AS17881Inet Hosting, Inc.RPKI Не найдено203.231.236.0
- 203.231.237.0/24AS17881Inet Hosting, Inc.RPKI Не найдено203.231.237.0
- 203.231.238.0/24AS17881Inet Hosting, Inc.RPKI Не найдено203.231.238.0
- 203.231.239.0/24AS17881Inet Hosting, Inc.RPKI Не найдено203.231.239.0
- 203.231.242.0/24AS9848SEJONG NETWORKSRPKI Не найдено203.231.242.0
- 203.231.254.0/24AS9848SEJONG NETWORKSRPKI Не найдено203.231.254.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Сеть, широковещательный адрес, маски и число хостов для любого префикса.