Поиск префикса BGP
Введите префикс (или отдельный адрес). Ответ из нашей ежедневной копии глобальной таблицы маршрутизации.
203.238.0.0/17
Анонсирован точно
- 203.238.0.0/17AS9848SEJONG NETWORKSRPKI Не найдено203.238.0.0
- Регистратура
- APNIC · Республика Корея · 29 сент. 1996 г.
- Выделенный блок
- 203.238.0.0 – 203.238.127.255
Покрывающие маршруты
Его не покрывает ни один менее специфичный маршрут.
Более специфичные маршруты
- 203.238.13.0/24AS131866Digital Edge KoreaRPKI Не найдено203.238.13.0
- 203.238.14.0/24AS131866Digital Edge KoreaRPKI Не найдено203.238.14.0
- 203.238.15.0/24AS131866Digital Edge KoreaRPKI Не найдено203.238.15.0
- 203.238.16.0/24AS131866Digital Edge KoreaRPKI Не найдено203.238.16.0
- 203.238.36.0/24AS17837NHN KCP Corp.RPKI Не найдено203.238.36.0
- 203.238.37.0/24AS9571INICIS Co., LtdRPKI Не найдено203.238.37.0
- 203.238.38.0/23AS9848SEJONG NETWORKSRPKI Не найдено203.238.38.0
- 203.238.38.0/24AS4670ShinbiroRPKI Не найдено203.238.38.0
- 203.238.39.0/24AS4670ShinbiroRPKI Не найдено203.238.39.0
- 203.238.56.0/22AS23584PUSAN CABLE TV SYSTEM CO., LTD.RPKI Не найдено203.238.56.0
- 203.238.56.0/24AS9492Maeil Business NewspaperRPKI Не найдено203.238.56.0
- 203.238.57.0/24AS9492Maeil Business NewspaperRPKI Не найдено203.238.57.0
- 203.238.58.0/24AS9492Maeil Business NewspaperRPKI Не найдено203.238.58.0
- 203.238.59.0/24AS9492Maeil Business NewspaperRPKI Не найдено203.238.59.0
- 203.238.60.0/22AS23584PUSAN CABLE TV SYSTEM CO., LTD.RPKI Не найдено203.238.60.0
- 203.238.84.0/23AS23584PUSAN CABLE TV SYSTEM CO., LTD.RPKI Не найдено203.238.84.0
- 203.238.84.0/24AS23584PUSAN CABLE TV SYSTEM CO., LTD.RPKI Не найдено203.238.84.0
- 203.238.85.0/24AS23584PUSAN CABLE TV SYSTEM CO., LTD.RPKI Не найдено203.238.85.0
- 203.238.86.0/24AS23584PUSAN CABLE TV SYSTEM CO., LTD.RPKI Не найдено203.238.86.0
- 203.238.106.0/24AS9973BSITCRPKI Не найдено203.238.106.0
- 203.238.107.0/24AS9973BSITCRPKI Не найдено203.238.107.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Сеть, широковещательный адрес, маски и число хостов для любого префикса.