Current status
Related networks
2The entity sits in the centre; its customers fan out to the left and its upstream providers to the right (arrows show transit direction). Scroll or use the buttons to zoom · drag the background to pan · click a node to open it in the directory.
Data as of 2026-06
The entity sits on the left and its connections fan out by role on the right; the graph shows each group’s most confident connections, and the full list below carries every relationship.
Full list
People & contacts
1Related research
15- C-Root's 2024 Stale Zone Made Publication Freshness a Root-Server Accountability Test
C-Root kept answering DNS queries while serving an old root-zone view for several days. The incident showed why root-service accountability must measure the freshness of authoritative state, not only whether a server responds.
Primary articlePublished 2026-07-31 - The 2005 Cogent-Level 3 Depeering Made Full-Internet Reachability a Transit Accountability Test
When Cogent and Level 3 stopped exchanging traffic directly in October 2005, some dependent customers discovered that an Internet contract and a registered prefix did not guarantee a working path. The accountable control was the route actually exchanged, the alternate path actually available and the evidence that restoration reached users rather than only the carriers' edge routers.
Primary articlePublished 2026-07-29 - Box Broadband Limited
Box Broadband's impact comes from an access-ISP and fibre-network role: it originates customer-facing address space, chooses upstream and peering paths, and participates in UK exchange infrastructure, so changes in routing policy, geofeed accuracy, RPKI/IRR hygiene, peering status, or Community Fibre integration can affect reachability, latency, content/CDN handoff, geolocation behavior, and service continuity for users and businesses in its footprint.
Mentioned articlePublished 2026-06-14 - AvatradeNet AVA TRADE IRELAND LIMITED
Ava Trade Ireland Limited’s ASN gives analysts a direct attribution point for the company’s internet footprint. Changes to the RIPE entities, route policies, or prefix announcements serve as concrete, observable signals of operational shifts that could affect reachability, dependency mapping, and incident triage for services using that address space. The narrow footprint makes the signal high-value for targeted monitoring of the AvaTrade operating environment.
Mentioned articlePublished 2026-06-02 - ISRcomunicaciones Telnetia S.L. trading as ISR comunicaciones
This entity bridges local retail telecom services and RIPE internet number resource administration. Monitoring AS210741's registry record and future BGP activity is relevant for dependency mapping, abuse contact paths, and connectivity analysis in the Valencia region.
Mentioned articlePublished 2026-06-02 - MEGABYTE-AS Megabyte IKE
Shifts in Megabyte IKE’s routing posture, registry records, or upstream dependencies could affect connectivity for 768 IPv4 addresses and alter abuse-handling pathways. For analysts mapping Greek network infrastructure or investigating routing anomalies, this operator represents an observable node. The absence of IPv6 and independent corporate data makes any registry change a significant signal for service continuity or expansion.
Mentioned articlePublished 2026-06-02 - CAPITAL OUTSOURCING SAL
Any change to AS210318's registration, upstream connectivity, or prefix announcements could introduce new routing dependencies in Lebanon and the Eastern Mediterranean. Even without active prefixes, the ASN represents a latent network origin in a geopolitically sensitive region, and its activation would require a reassessment of regional transit dynamics.
Mentioned articlePublished 2026-06-02 - Babbar SAS
Babbar’s dual role as an SEO analytics provider and an internet-scale crawler operator matters because changes in its routing, IP ranges, or platform coverage directly influence both web traffic attribution and the quality of SEO intelligence sold to customers. Site operators and security teams must be able to identify and govern Barkrowler traffic.
Mentioned articlePublished 2026-06-02 - A zona raiz desatualizada do C-Root em 2024 transformou a atualidade da publicação em um teste de responsabilização dos servidores raiz
O C-Root continuou respondendo a consultas DNS enquanto oferecia uma visão antiga da zona raiz por vários dias. O episódio mostrou por que a responsabilização de um operador de servidor raiz precisa abranger a atualidade do estado autoritativo, e não apenas a disponibilidade de uma resposta.
Primary articlePublished 2026-07-31 - عندما جعلت منطقة C-Root المتقادمة في 2024 حداثة النشر اختباراً لمساءلة خوادم الجذر
ظلّت C-Root تجيب عن استعلامات نظام أسماء النطاقات، لكنّها قدّمت لعدة أيام نسخة قديمة من منطقة الجذر. تكشف الحادثة أن مساءلة خدمة الجذر لا تُقاس بمجرد وصول الحزم وعودة الإجابات، بل بقدرة المشغّل على إثبات أن الحالة السلطوية التي يقدّمها حديثة ومتسقة ويمكن رصد انحرافها بصورة مستقلة.
Primary articlePublished 2026-07-31 - C-Roots veraltete Root-Zone von 2024 machte Publikationsfrische zum Prüfstein für Rechenschaft
C-Root blieb im Mai 2024 für DNS-Anfragen erreichbar, lieferte jedoch über mehrere Tage eine nicht mehr aktuelle Sicht auf die Root-Zone. Der Vorfall zeigt, warum die Verantwortung eines Root-Server-Betreibers nicht mit Verfügbarkeit endet: Entscheidend ist auch, ob die tatsächlich ausgelieferten autoritativen Daten nachweislich dem aktuellen Veröffentlichungsstand entsprechen.
Primary articlePublished 2026-07-31 - C-Rootの2024年ルートゾーン停滞が突き付けた「公開鮮度」という説明責任
C-RootはDNS問い合わせに応答し続けていた。しかし、そこで返されるルートゾーンは数日にわたり更新されなかった。2024年5月の事案が示したのは、ルートサービスの健全性を稼働率だけで判定してはならないということだ。権威データが現在の状態を反映しているか、その事実を独立した観測で証明できるかまでが、ネットワーク基盤を運用する者の説明責任に含まれる。
Primary articlePublished 2026-07-31 - C-Root 2024 年根区陈旧事件：把发布新鲜度纳入根服务器问责
C-Root 在数日内仍能回答 DNS 查询，却没有跟上根区的新版本。这个看似矛盾的状态揭示了一条基础设施治理底线：权威服务是否“在线”，不能只看它有没有回应，还要看它实际提供的权威数据是否仍然新鲜、准确且可被独立验证。
Primary articlePublished 2026-07-31 - La zona raíz desfasada de C-Root en 2024 convirtió la vigencia de publicación en una prueba de rendición de cuentas
C-Root siguió contestando consultas DNS mientras ofrecía durante varios días una versión anterior de la zona raíz. El episodio mostró que la responsabilidad de un operador raíz no se agota en mantener el servicio accesible: también exige demostrar que el estado autoritativo servido es vigente, verificable y observable desde rutas independientes.
Primary articlePublished 2026-07-31 - En 2024, la zone racine périmée de C-Root a fait de la fraîcheur de publication un test de responsabilité
C-Root a continué de répondre aux requêtes DNS tout en présentant pendant plusieurs jours une version ancienne de la zone racine. Cet incident montre qu’un service racine ne peut pas être jugé uniquement sur sa disponibilité : il doit aussi démontrer que l’état faisant autorité qu’il sert est actuel.
Primary articlePublished 2026-07-31