Skip to main content

Topic

Peering and Transit

Within the Topic facet, Peering and Transit topic intelligence connects articles that share a specific subject, signal focus, or monitoring theme. The page gives readers a richer path through related reporting, source evidence, market actors, and infrastructure implications, with enough context to understand why the topic matters across company movements, governance decisions, regional exposure, and operational risk. Readers can compare recurring signals, affected organisations, public evidence, market context, service continuity, procurement, competition, compliance, and strategic planning questions behind the subject instead of stopping at a thin list of matching articles. It explains what the topic covers, which infrastructure actors or policies are involved, what evidence supports the coverage, and why the subject may matter for operators, customers, investors, and policy readers.

Anonymous engineer viewed from behind studying abstract network topology diagrams on unbranded monitors.

Leaders

John Moy and the Operational Record Behind OSPF State and Graceful Restart

John Moy's documented OSPF work offers a restrained account of routing reliability: topology state has to be explicit and synchronized, protocol cost has to be measured, standardization has to rest on implementation experience, and forwarding continuity during restart has to end…

Aug 2, 2026
Wide documentary-style view of a generic network operations facility representing prefix-state reconciliation and route reachability

Global Cloud Services

Cloudflare's 2026 BYOIP Outage Made Prefix-State Control an Accountability Test

A control-plane change withdrew customer-owned prefixes and exposed why address authority, service bindings, route intent, deployed configuration and public reachability need separate, continuously reconciled evidence.

Aug 2, 2026
Anonymous network engineer reviewing abstract routing and label-switching paths in an unbranded operations workspace.

Leaders

Ross Callon and the Operational Transition from Dual Routing to MPLS Labels

Ross Callon's dated standards record shows that network transitions endure when capabilities, compatibility, and forwarding identity are made explicit, first for IP and OSI coexistence and later for traffic classes bound to locally meaningful MPLS labels.

Aug 2, 2026
Wide documentary-style view of a generic network operations room representing root DNS telemetry, anycast routing and cross-operator continuity

Global Institutional

The 2015 Root DNS Flood Made Cross-Operator Telemetry an Accountability Test

Two concentrated query floods exposed the difference between root-system continuity and localized saturation, making shared, layer-specific telemetry the basis for judging operator preparedness and response.

Aug 2, 2026
Wide documentary-style view of generic DNS and network operations equipment representing resolver, routing and interconnection accountability

Europe and Middle East Institutional

Spamhaus's 2013 DDoS Made Open DNS Recursion a Network Accountability Test

The March 2013 campaign showed how exposed recursive DNS, source-address spoofing and shared interconnection paths could turn individually small configuration failures into a large external cost. Accountability depends on proving which operator controlled each executable step and…

Aug 2, 2026
Anonymous network engineer viewed from behind studying abstract routing identity and forwarding-state paths in an unbranded workspace.

Leaders

Dave Oran and the Operational Boundaries from IS-IS to IP Anycast

Dave Oran’s shared technical record shows how dependable forwarding begins with a clear account of identity: which routing domain, service instance, name, or piece of state a system is actually using, and where continuity can break when that identity changes.

Aug 2, 2026
Anonymous engineer viewed from behind studying abstract link-state path alternatives on unbranded screens.

Leaders

Peter Psenak and the Link-State Decisions Behind Segment Routing and Flexible Algorithms

Peter Psenak's attributed IETF record offers a practical way to examine how routing policy becomes operational state. The relevant standards do not promise an automatically optimal network. They define identities, constraints, participation rules, forwarding bindings, and failure…

Aug 2, 2026
Most cyan network paths cross an abstract Istanbul edge chamber while a limited amber subset slows or stops beside an unlabeled short-interval ring.

Global Cloud Services Trends

Cloudflare’s 15-minute Istanbul network incident left a precise window but almost no diagnosis

Cloudflare says elevated latency and connection errors affected Istanbul for 15 minutes on 1 August. The unusually exact interval is the firmest part of a record that identifies no product, route, cause or scale—and whose only visible notice appeared after the reported impact had…

Aug 2, 2026
Anonymous routing engineer reviewing abstract link-state records in an unbranded workspace

Leaders

Hannes Gredler and the Failure Boundaries Behind IS-IS and BGP-LS

Hannes Gredler’s co-authored standards work offers a practical lesson in routing automation: useful decisions begin with records that identify topology precisely, state their scope, and remain honest about what they cannot authorize or prove.

Aug 2, 2026
Network operator inspecting generic carrier routing equipment and fiber patching in an unbranded telecom facility

Asia-Pacific National Telecom

KT's 2021 Routing Error Made Protocol-Boundary Validation a National Network Accountability Test

KT's nationwide Internet disruption showed why a carrier cannot treat an approved maintenance plan or two layers of manual review as proof that a live routing change is safe: accountability depends on the exact commands routers execute, the protocol boundaries they preserve, the…

Aug 1, 2026
Engineers inspecting fiber cross-connects and network aggregation equipment in an unbranded interconnection room

Global Cloud Services

GitHub's 2015 Great Cannon DDoS Made On-Path Code Injection a Network Accountability Test

The 2015 attack on GitHub showed that network accountability begins with the bytes a user actually receives, not merely the address, certificate, contract or status page associated with a service.

Aug 1, 2026
An anonymous network engineer examines abstract routing-policy and address-scope relationships on unlabelled screens.

Leaders

Yakov Rekhter and the Operational Boundaries Built into BGP and Private Addressing

Yakov Rekhter's public standards record shows how inter-domain routing and address scope became manageable through explicit permissions, visible protocol state, bounded uniqueness, and honest accounting for the cost of later change.

Aug 1, 2026
Representative Internet exchange operations room with carrier routers, structured fibre paths and one isolated maintenance path

Europe and Middle East National Telecom

LINX's 2023 LON2 Incidents Made Lab-to-Production Network State an Accountability Test

When a router moves from a laboratory into a live Internet exchange, a clean configuration file is not enough. LINX's public account of its 2023 LON2 incidents shows why operators must verify the identity and forwarding state that the device is actually running, especially when a…

Aug 1, 2026
Representative distributed edge network operations room with routing, capacity and failover monitoring

Global Cloud Services

Akamai's 2004 Network Attack Made Distributed Edge Failover an Accountability Test

Akamai's bounded account of a 2004 denial-of-service incident shows why a distributed edge network must prove customer impact, destination capacity and failover behavior from the running network rather than architecture claims alone.

Aug 1, 2026
Most cyan request packets cross a bounded cloud-edge chamber while a restrained amber subset fragments and an unlabeled timeline sits behind the restored flow.

Global Cloud Services Trends

Cloudflare’s IAD 5XX episode lasted 256 minutes but was disclosed in one retrospective update

Cloudflare says an increased level of HTTP 5XX errors affected Ashburn, US (IAD), from 18:45 to 23:01 UTC on 31 July. Yet the public incident contains only one visible update, timestamped more than two hours after that interval ended. The fault is closed; the operational…

Aug 1, 2026
Most cyan web requests cross a regional cloud boundary while intermittent amber requests fragment before a repair module restores stable flow.

Global Cloud Services Trends

Cloudflare’s us-east-1-aws path returned intermittent 5xx errors for 138 minutes

Cloudflare resolved a minor incident involving intermittent HTTP 5xx responses for customers using the label us-east-1-aws at 04:19:32.991 UTC on 31 July. A fix had entered monitoring 10 minutes and 51.068 seconds earlier. The operator disclosed the request outcome and…

Aug 1, 2026
A translucent surveyed submarine ring route hovers above the Caribbean seabed between two landing zones, with a ghosted cable drum showing that construction is still planned.

Global National Telecom Trends

Fénix promises a 14 Tbps Venezuela–Curaçao ring, but the cable is still an announced project

Liberty Networks and CANTV announced Fénix on 31 July as a 378-kilometre submarine cable system between Camuri in Venezuela and Willemstad in Curaçao, with a stated minimum ring capacity of 14 Tbps. The design would connect Venezuela to a broader Caribbean hub. The release is…

Aug 1, 2026
Generic data-centre network aisle with carrier-grade routing equipment and redundant fiber paths

Global Cloud Services

OVH's 2016 Mirai Attack Made DDoS Scrubbing Capacity an Accountability Test

OVHcloud's report of traffic above one terabit per second during the first Mirai wave turned a spectacular attack number into a practical network question: could a hosting operator measure the flood, activate mitigation, preserve clean traffic and show customers that the service…

Aug 1, 2026
An unbranded network operator facing dense routing and mitigation equipment in a generic operations room

Global Cloud Services

GitHub's 2018 Memcached Attack Made Anti-Spoofing and Mitigation Handoff an Accountability Test

GitHub's response to a 1.35-terabit-per-second attack showed that DDoS resilience depends on more than buying bandwidth: operators must detect abnormal traffic, move routing authority safely, preserve clean delivery and reduce the spoofing conditions that make reflection…

Jul 31, 2026
Most blue request paths continue across an abstract London network while a small amber subset is examined by diagnostic rings.

Europe and Middle East Cloud Services Trends

Cloudflare’s London HTTP-error incident was still at the first diagnostic stage

Cloudflare opened a minor incident at 19:06:19.068 UTC on 31 July after detecting increased HTTP errors affecting a subset of customers. Fourteen minutes later, at the Wave 46 cutoff, the public record still said only that the company was investigating, analysing and mitigating…

Jul 31, 2026