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.
History
India Funded NIXI in 2003. By 2007, 27 of 135 ISPs Had Joined Its Nodes
India Funded NIXI in 2003. By 2007, 27 of 135 ISPs Had Joined Its Nodes intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that may follow.…
Story
LACNIC links an operator’s ASN to the freedom to change providers
LACNIC links an operator’s ASN to the freedom to change providers intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that may follow. The…
Story
RPKI-Linked BGP Updates Stay Below 1% at RIPE RIS RRC00
An eleven-year study finds a small but rising share of BGP updates associated with RPKI events. Its reassuring number belongs to one unusually diverse RIPE RIS collector, not to an Internet-wide census.
History
TANet’s No-Transit Boundary: ISP Interconnection Rules, 1996–2006
Taiwan’s education network allowed commercial providers to interconnect on conditions that kept its own backbone and international circuits outside their carriage plans. The surviving versions show how that boundary was reviewed, measured and revised.
History
When the Exchange Became a Service: JPIX and Japan’s Commercial Peering Turn, 1997
Japan’s first commercial exchange was announced with an unusual promise: reliability would be built into a company, a customer service and a second site, while the experimental network it followed would remain a partner. JPIX’s founding shows how the Internet’s shared…
Global Institutional Trends
The IXP Is Still There; the Local Interconnection Ecosystem Is the Test
Internet Society’s revised policy brief moves the question from whether an exchange exists to whether local participation can endure. Its own caveats point to a harder scorecard than traffic totals.
North America National Telecom Trends
Chicago’s second exchange is growing. Are the paths independent?
DE-CIX says its Chicago exchange has nearly quadrupled its traffic and become the city’s second-largest exchange. The more useful question for network operators is what the growth figures can prove about their own routes—and what remains hidden behind a larger footprint.
Europe and Middle East Datacenter
InterLAN-IX: one exchange, two sets of numbers
Romania's domestic peering fabric is operated by InterLAN Internet Exchange SRL, a Bucharest-headquartered company whose own published figures and the Romanian Network Operators Group's description of the same platform do not reconcile on members, locations or traffic. For an…
Africa Datacenter Trends
ANGONIX: Angola's internet exchange and the Atlantic cable layer
Angola's national internet exchange has operated since 16 March 2015 as a neutral platform run by Angola Cables and hosted at the AngoNAP Luanda data centre. Its operator's submarine cable layer is moving toward services of up to 800 Gb/s, while the exchange's own interconnection…
SANOG
Bhutan Internet Exchange: membership, peering and the resource footprint behind national interconnection
Bhutan Internet Exchange: membership, peering and the resource footprint behind national interconnection intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the…
Asia-Pacific Institutional
HyderabadIX: A non-profit exchange point that the public record identifies but cannot yet account for
A non-profit internet exchange point is registered to Hyderabad, India, and appears across public registry, routing and lookup sources. What those same sources will not tell you — and what every operator, investor and regulator in the city should notice — is whether it is still…
History
MAE-East Was a Room, Not a Policy: The Early Internet’s Shared Exchange
A shared Ethernet made it easier for early providers to meet in northern Virginia. It did not make them exchange routes. MAE-East shows why a common physical point and a common network policy are different things.
History
A Mailbox, a Route and a Country Code: Kazakhstan’s Internet, 1991–96
Kazakhstan’s early network story has several dates that are each defensible when attached to the right layer. A mail node, a persistent Internet route, a root-zone delegation and a commercial service did not arrive at the same moment.
History
The Backbone Had a Closing Date, Not a Single Switch: NSFNET, 1995
NSFNET’s backbone service ended on a date fixed in advance. The network’s own termination notice shows why that date should not be mistaken for a single nationwide cutover: many users already relied on another network for their primary path.
Leaders
A Contact Was Not a Peer: William B. Norton’s Peering Personals
A private contact list and a conference-room introduction could make the first peering conversation easier to start. They could not make two networks agree to connect.
History
KIXP Went Local, Then Closed: Kenya’s Internet Exchange, 2000–02
Kenya’s first Internet exchange began carrying local traffic in November 2000, then was ordered shut a month later. Its 2002 return shows how a simple peering function depended on permission and access to the incumbent’s underlying lines.
History
Two Links, Three Networks: Taiwan’s 1994 Internet Peerings
In 1994, Taiwan’s academic backbone acquired two distinct domestic links: a T1 connection to HiNet early in the year and a 10 Mbps Ethernet interconnection with SeedNet in June. The surviving chronology shows a shift from one academic network toward a three-network landscape…
History
The Exchange Came Before the Association: AMS-IX’s Two-Stage Start
Amsterdam’s Internet exchange was already joining networks before its entities turned the service into a member-governed association. Its 1994–97 history shows why a shared switching fabric and the institution that runs it are separate parts of Internet infrastructure.
Story
Why the IXP Ranking Counts São Paulo, Rio and Fortaleza Separately
Gael Hernandez’s PeeringDB-based ranking is a useful view of recorded capacity at individual exchange entries. Its three IX.br city rows should not be read as three independent operator systems: the same study counts a much broader, multi-country NL-IX footprint as one entry.
History
At the Router, Membership Became a Route: CIX's 1994 Filter
In 1994, a shared router made it easy for CIX members to exchange traffic without a per-byte bill. Then the association tied route advertisement at that router to a US$7,500 annual membership—and pointed providers toward private links that could carry the exchange elsewhere.