Поиск префикса BGP
Введите префикс (или отдельный адрес). Ответ из нашей ежедневной копии глобальной таблицы маршрутизации.
210.182.0.0/16
Анонсирован точно
- 210.182.0.0/16AS3786LG DACOM CorporationRPKI Не найдено210.182.0.0
- Регистратура
- APNIC · Республика Корея · 24 нояб. 1998 г.
- Выделенный блок
- 210.182.0.0 – 210.182.255.255
Покрывающие маршруты
Его не покрывает ни один менее специфичный маршрут.
Более специфичные маршруты
- 210.182.7.0/24AS9319HCN CHUNGBUK CABLE TV SYSTEMSRPKI Не найдено210.182.7.0
- 210.182.8.0/24AS9846KPNRPKI Не найдено210.182.8.0
- 210.182.9.0/24AS10167HANVIT BANKRPKI Не найдено210.182.9.0
- 210.182.11.0/24AS17598LG HelloVision Corp.RPKI Не найдено210.182.11.0
- 210.182.15.0/24AS17598LG HelloVision Corp.RPKI Не найдено210.182.15.0
- 210.182.17.0/24AS9319HCN CHUNGBUK CABLE TV SYSTEMSRPKI Не найдено210.182.17.0
- 210.182.101.0/24AS9319HCN CHUNGBUK CABLE TV SYSTEMSRPKI Не найдено210.182.101.0
- 210.182.124.0/24AS38431KB InsuranceRPKI Не найдено210.182.124.0
- 210.182.126.0/24AS18317SHINHAN DSRPKI Не найдено210.182.126.0
- 210.182.148.0/24AS9319HCN CHUNGBUK CABLE TV SYSTEMSRPKI Не найдено210.182.148.0
- 210.182.152.0/23AS9319HCN CHUNGBUK CABLE TV SYSTEMSRPKI Не найдено210.182.152.0
- 210.182.157.0/24AS9319HCN CHUNGBUK CABLE TV SYSTEMSRPKI Не найдено210.182.157.0
- 210.182.161.0/24AS9530SHINSEGAE I C Co., Ltd.RPKI Не найдено210.182.161.0
- 210.182.168.0/24AS38421Mirae Asset Investment Management Co., Ltd.RPKI Не найдено210.182.168.0
- 210.182.170.0/24AS9784kbcardRPKI Не найдено210.182.170.0
- 210.182.179.0/24AS9319HCN CHUNGBUK CABLE TV SYSTEMSRPKI Не найдено210.182.179.0
- 210.182.190.0/24AS131878HYUNDAICARD CO.RPKI Не найдено210.182.190.0
- 210.182.226.0/24AS9690SMARTRORPKI Не найдено210.182.226.0
- 210.182.254.0/24AS17862Kangwon National UniversityRPKI Не найдено210.182.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Сеть, широковещательный адрес, маски и число хостов для любого префикса.