Skip to main content

Lead Report / Asia-Pacific Cloud Services

Conceptual illustration contrasting a suspended primary cloud operations room, a separated backup vault, and an alternate compute hall.
The ransomware incident at IDC Frontier did not prove that IDCF Cloud Backup failed. It did expose a more useful market question: when the ordinary cloud console is stopped, who can reach a copy, authorize its use and supply somewhere to run the restored service?

IDCF’s outage put the recovery control plane in view

The ransomware incident at IDC Frontier did not prove that IDCF Cloud Backup failed. It did expose a more useful market question: when the ordinary cloud console is stopped, who can reach a copy, authorize its use and supply somewhere to run the restored service?

  1. At dusk, a street-side fibre cabinet splits one illuminated trunk into several connections beside residential buildings.

    FiberCop’s fibre gains still need to earn their way into cash

    FTTH lines rose 26% year over year and FiberCop took 66% of first-quarter net additions, yet first-half revenue and organic EBITDAaL both slipped. The test is whether more coverage becomes paying wholesale use before the build consumes another round of capital.

  2. AI editorial illustration of distinct critical-infrastructure sectors feeding evidence through ministry review to a national evaluation, without a single score.

    Japan’s Critical-Infrastructure Standard Needs Comparable Evidence Across 16 Sectors

    Japan has put a common review cycle around cybersecurity measures for critical infrastructure. The test will be whether its first evaluation shows what was measured, who was covered and how evidence changed government plans—without pretending that hospitals, ports, railways and telecoms face one interchangeable risk.

  3. A sealed software-update capsule follows a blue route beside an amber diversion while a terminal prints one blank local receipt.

    LACNIC’s BGP Case Counts 368 Route Peers. The Vendor Could Not Produce a Definitive Installation List.

    LACNIC’s latest routing-security case is unusually rich in network evidence and unusually poor in application evidence. The route, certificate and attack window can be reconstructed in detail; the vendor still cannot say which installations accepted the malicious update. That gap is not a reason to distrust the routing record. It is a reason to demand a different receipt.

Member Access

Your daily intelligence edge starts here

Strategic Circle turns infrastructure moves, policy shifts and market signals into a concise briefing in your chosen language—plus the research library and member forum—for USD 20/month.

  • 01Daily intelligence brief
  • 02Governance + market + RIR
  • 03Preference control anytime

BTW Media on Air

Selected briefings, interviews, and live sessions from the BTW intelligence team, focused on internet infrastructure, governance, and market signals.

View All

Inside iFX EXPO Asia 2026: Trading and Fintech Converge in Hong Kong

Why This Backup Route Had to Stay Hidden

Equifax Had the Patch. Why Did the Breach Last 76 Days?

23andMe: How 14,000 Accounts Exposed Millions

You Clicked Revoke. Why Does Access Still Work?

NVIDIA Agreed to Buy Hugging Face. Will It Stay Open?

What’s Inside AI’s $2.67T Forecast?

37 Million T-Mobile Accounts Exposed—What Could Attackers Actually Do?

AI Answered Your Call. Did It Solve Anything?

Your Account Was Hacked. Why Didn’t Reporting It Fix Anything?

Can Your AI Search Give Away Your Plans?

How a Cyberattack Became a Gas Shortage | Colonial Pipeline Explained

16 Kbps on Paper. Just 80 bps in Practice.

Factory Reset: 100% Complete. Still Offline?

One Dot Sent Cookies to the Wrong Website | curl Bug Explained

Two identical cyan algorithm tokens resolve into different amber and magenta routing-policy chambers, each paired with a sealed evidence capsule.

Governance

The Route Policy Can Change While Its SR-Algorithm Number Stays the Same

RFC 9933 lets a path request name an SR-Algorithm. For a Flexible Algorithm, however, the number is only a handle: the policy that actually selects a route lives in a winning definition, a metric dictionary, a topology snapshot and an ordered evaluator that can all change underneath it.

Adrian Farrel before an abstract network where a luminous computed route fades before a darker device layer.

Market

Adrian Farrel and the Path That Exists Only on the Controller

A positive PCEP reply can put a clean route on an operator's screen before any router has accepted it. Adrian Farrel's PCE architecture matters because it lets us say exactly what has happened—and what has not.

Conceptual illustration of the completed BT–TalkTalk operating transfer: connected UK homes continue beside a separate desk representing pending competition and public-interest review.

Market / Trends

BT bought continuity before clearance; the costs are still being counted

BT has taken TalkTalk’s consumer business and PlatformX out of administration to keep 2.5 million retail and wholesale connections operating. That closes one clock—the risk of an abrupt service break—while opening another: whether a completed rescue acquisition should remain in place after competition and public-interest review.

Conceptual diagram of Cloudflare R2 object storage, an outward file-transfer route and a separate workspace for inspecting replacement application components.

Market / Companies

Cloudflare R2’s zero-egress price is not a zero-cost exit

Cloudflare lists no charge for outbound transfer from R2 and documents a way to copy objects out. The remaining economic question is what customers must spend—and successfully operate—to turn that export into a working replacement.

Three conference microphones stand apart from an organised production desk in a quiet Pokhara meeting room.

Governance / NOGS

Who opens the room? What npNOG-10's welcome order can—and cannot—prove

The first twenty minutes of a conference can reveal institutional relationships. They cannot, without supporting records, tell us who held the decisive authority.

Editorial position

Why BTW Media exists

  • Reality over advocacy
  • Evidence over sentiment
  • Systems over noise

Internet governance is too often described as theory, consensus, or institutional comfort while operators live with the consequences of structure, scarcity, jurisdiction, and incentives.

BTW shows how the system works when assumptions are tested: clear, uncomfortable, evidence-led reporting that keeps attention on structure rather than drama. Public reporting is published to travel: it may be indexed, quoted, translated, used in search and AI answers, and used to train models so the evidence can shape how infrastructure questions are understood.

Core Architecture

Governance, market, and membership branches operating in one integrated intelligence model.

Governance

  1. Immutable to the Client Is Not Immutable in Time
  2. Neal Cardwell and the Loss Detector That Trusted Time Over Duplicate ACKs
  3. The New Reverse Tree Existed Before the Old One Disappeared: RFC 3152
  4. RFC 9945’s Moderator Team Is Not Its Activation Receipt
  5. The Network Agreed the Root Was Down. It Did Not Prove a Crash: RFC 9866
  6. The IPv6 Prefix Changed. The Identifier Stayed: RFC 3041
  7. Lixia Zhang and the Reservation That Expired Without a Refresh
  8. The Route Stopped Flapping. Its Penalty Had Not: RFC 2439
  9. RFC 9707: Being Connected Is Not Access—and a Workshop Report Is Not a Mandate
  10. Craig Partridge and the Gigabit That Did Not Need a New Internet
View Governance

Market

  1. Japan’s virtual hyperscaler still has to become a service
  2. PowerCompute’s 11 MW contract firms only 300 kW at peak
  3. Nick McKeown and the Barrier Reply That Never Saw a Packet
  4. The 2.1-gigawatt promise sits outside Black Hills’ wires
  5. William B. Norton and the Metric That Could Not Price a Peer
  6. Kodiak’s 76 MW deal names the load, not its credit
  7. OVHcloud’s IPv4 fee makes the address visible—not market-priced
  8. Forum’s AI revenue forecast is a commissioning calendar, not a run rate
  9. Fiberhost’s open-access promise is the real test of Telekom’s Polish deal
  10. After the WTO Moratorium Lapsed, Three Tracks Claimed Different Mandates
View Market

Membership

  1. A Join Priority Is Not an Enrollment Decision Record
  2. Equal Cost Did Not Make the Paths Interchangeable: RFC 2991 and the Price of Stable Multipath
  3. A Signed Transaction Token Does Not Attest Every Claim
  4. The First NAPTR in the Packet Was Not the First Rule: RFC 3403
  5. One Path, Four Algebras, and One Contagious Unknown: RFC 2215
  6. RFC 9019: A Signed Firmware Manifest Is Not Installation Authority
  7. The Highest-CoS Probe Does Not Measure Every BIER Service
  8. An RPKI Validator Needs an Audit Trail, Not Just a Green Cache
  9. RFC 9810: The Certificate Was Granted, but Not as Requested
  10. The Coalition Clause: What the Empowered Community's June–July 2026 Instruments Certified — and Refused
View Membership

Number Resource Society

Reporting on address stewardship, representation, and the institutions shaping number-resource governance.

View Number Resource Society
  1. A Trust Anchor Rollover Needs an Acceptance Ledger
  2. A Member Logo Is Not a Live Power of Attorney
  3. A Country Field Is Not an RIR Mandate
  4. An ASN Transfer Needs a Routing-Identity Handover Ledger
  5. A ROA Change Needs an Authorization-and-Withdrawal Ledger
  6. An Unanswered Profile Needs a Reply-State Ledger
  7. The FAQ Answer Needs a Version Date
  8. A RIR Representation Mandate Needs a Scope-and-Revocation Ledger
  9. When One Corporate Group Casts Twenty Registry Votes
  10. Digital Identity Requirements at the Registry Gate

RIR Watchdog

Five regional sessions: ARIN, RIPE NCC, APNIC, AFRINIC, and LACNIC.

Network Operator Group (NOGs)

Operational intelligence from the communities where routing, peering, resilience, and deployment practice are tested.

View Network Operator Groups

History of the Internet

The Address Was Borrowed. The Route Was Never Included: RFC 2008

In 1996, an organisation could keep the same prefix after leaving a provider and still become unreachable from part of the Internet. RFC 2008 explained why: the registry record, two providers’ cooperation and the rest of the world’s routing decisions were three different promises.

An amber address token leaves one 1990s provider system for another while its thin route crosses independent green and red filter gates beside a paper allocation ledger and a teal aggregate.

The Address Was Borrowed. The Route Was Never Included: RFC 2008

In 1996, an organisation could keep the same prefix after leaving a provider and still become unreachable from part of the Internet. RFC 2008 explained why: the registry record, two providers’ cooperation and the rest of the world’s routing decisions were three different promises.

  1. The State Table Was Also a Kill Switch: RFC 2012
  2. A Legitimate Packet Can Still Fail the Filter: RFC 3704
  3. BCP Marked the Control Frame. It Had Not Proved the Spanning Tree Safe: RFC 3518
Open History Session

Leadership Alliance

Tim Bruijnzeels and the RPKI Overclaim That No Longer Invalidated the Whole Subtree

A certificate can be wrong in one place without being worthless everywhere. That proposition sounds modest, yet it changed the failure geometry of the Resource Public Key Infrastructure. In RFC 8360, Tim Bruijnzeels and five co-authors replaced one all-or-nothing consequence with a verified intersection: an RPKI certificate may overstate its resources, but the excess gains no authority and need not erase every legitimate object beneath it.

AI editorial portrait of Tim Bruijnzeels beside an RPKI certificate tree whose verified branch continues while an overclaimed resource is clipped at the validation boundary

Tim Bruijnzeels and the RPKI Overclaim That No Longer Invalidated the Whole Subtree

A certificate can be wrong in one place without being worthless everywhere. That proposition sounds modest, yet it changed the failure geometry of the Resource Public Key Infrastructure. In RFC 8360, Tim Bruijnzeels and five co-authors replaced one all-or-nothing consequence with a verified intersection: an RPKI certificate may overstate its resources, but the excess gains no authority and need not erase every legitimate object beneath it.

  1. Remco van Mook and the IPv4 Gateway That Has No IPv4 Neighbour
  2. RFC 9947 Keeps the Packets In. The Evidence Still Has to Leave
  3. The Grant Was Automatic. The Boundary Was Not: RFC 1988
Open Alliance Session