AS8315
Автономная система. Кто держит, что анонсирует и с кем связан.
Точки обмена трафиком источник не ответил
- ошибка
- www.peeringdb.com ответил HTTP 429
Соседи по BGP
Анонсы
- IPv4 префиксов
- 84
- IPv6 префиксов
- 14
- транзитом
- v4 20, v6 2
Полный список: bgp.tools · bgp.he.net
Кто это RIPEstat
- владелец
- WORLDSTREAM WorldStream B.V.
- анонсирует
- да
- блок ASN
- 8192-9215, Assigned by RIPE NCC
Whois и регистратор RIPEstat
- организация
- ORG-WA106-RIPE
- RIR
- RIPE NCC
- abuse
- abuse@worldstream.nl
Сырой whois
aut-num 8315 as-name WORLDSTREAM remarks Worldstream remarks https://www.worldstream.com remarks ============================================================== remarks Please find our peering details at remarks http://as8315.peeringdb.com/ remarks ============================================================== remarks We have an open peering policy and would like to peer with remarks you. Please send requests to noc@worldstream.com remarks ============================================================== remarks NOC: noc@worldstream.com remarks Abuse: abuse@worldstream.com remarks ============================================================== remarks We share the view that for many networks ( including ours:-) ) remarks only some abstraction of the actual routing policy should/can remarks be published in the IRR. remarks Right now we are abstracting to a very essential minimum. remarks the most important and helpful use of the IRR is remarks to publish what a network will announce to peers and upstream remarks we are providing that by means of the AS-set AS8315:AS-WORLDSTREAM remarks which we have been keeping up to date all the time remarks we encourage all our neighbors to define and maintain an remarks AS-set to describe their announcements, and to register remarks all the routes (and have their customers do so as well) import from AS-ANY accept ANY remarks we maintain a list of what our neighbors have told us remarks about their announcements towards AS8315 - in terms of remarks AS-set (preferred), AS number, route-set remarks (and the IRR database used to publish) remarks in fact we apply route filters based on this remarks for all neighbors - as far as feasible remarks for data published through the RIPE routing registry remarks we generate filters automatically remarks we consider the integration of RIR and routing registry data remarks and the application of RPSS authorization a great feature remarks of the RIPE routing registry remarks unfortunately this benefit is not available with any remarks other IRR database that we know of... remarks and some of the IRR databases allow essentially any garbage remarks to be registered without any control - making those databases remarks quite useless... export to AS8315:AS-ACNBB announce ANY export to AS-ANY announce AS8315:AS-ACNBB remarks customers are strongly encouraged to define and maintain remarks an AS-set that we will include in the definition remarks of AS8315:AS-ACNBB (if we are told the name) remarks this will be sufficient to have our peers accept the routes remarks in any case peers - and any network in the Internet - remarks is free to apply some selective policy (e.g. prefix remarks length based) remarks but we do not think that any such selective policy remarks will be based on details of our routing policy omitted remarks from this aut-num: object remarks unfortunately some customers do not provide usable IRR data; remarks we will NOT add to the uncontrolled garbage in the IRR by remarks proxy registering in some database that requires no remarks authorization remarks we advise customers that routes without IRR registration remarks and not covered by AS8315:AS-ACNBB may receive less than remarks full support by some of our peer networks and other remarks parts of the Internet remarks ============================================================== remarks IPv6 we do/publish essentially the same like for IPv4 mp-import afi ipv6.unicast from AS-ANY accept ANY mp-export afi ipv6.unicast to AS8315:AS-ACNBB announce ANY mp-export afi ipv6.unicast to AS-ANY announce AS8315:AS-ACNBB remarks ============================================================== org ORG-WA106-RIPE admin-c SK16894-RIPE tech-c SK16894-RIPE status ASSIGNED mnt-by RIPE-NCC-END-MNT mnt-by MNT-WORLDSTREAM created 2006-01-05T09:59:28Z last-modified 2026-03-30T13:09:31Z source RIPE
Карта связности 249 маршрутов RIS, 7 AS
Напрямую к Tier 1: 2, плюс 1 транзитных провайдеров. Нормальная связность для хостера среднего размера. Наведи на AS, чтобы подсветить её связи, кликни, чтобы открыть досье. Толщина линии — доля маршрутов.
Что тут вообще нарисовано
Origin — сеть, которая анонсирует префикс в BGP. Транзит — провайдер, которому origin платит за доставку трафика во весь интернет. Tier 1 — полтора десятка магистральных сетей (Lumen, Arelion, Cogent, NTT и компания), которые сами никому за транзит не платят: весь интернет они видят через бесплатный пиринг друг с другом. Многие маршруты доходят до кого-то из них, но не все: часть путей идёт через пиринг и региональные транзиты без Tier 1. На карте показаны только те пути, что доходят до Tier 1, или, если таких нет, первые четыре хопа.
Линии построены по реальным AS-путям, которые видят сотни BGP-пиров RIPE RIS по всему миру: от origin до первой Tier 1 на пути. Чем больше апстримов и чем толще связи с разными Tier 1, тем устойчивее сеть к падению одного провайдера. Российские сети часто выходят в мир через Ростелеком, ТТК, RETN или МегаФон, а не напрямую к Tier 1.
Смотреть там же: bgp.tools · bgp.he.net · PeeringDB · Cloudflare Radar · RIPEstat