Briefing Desk
Latest Briefings
Concise reporting on the developments shaping internet governance and infrastructure. Browse each area for recent news, context and watchpoints.
Coverage
Governance / ICANN
In this section: 1 briefingICANN Counted 1,616 Applications. It Had Not Added 1,616 TLDs.
Reveal Day will make the 2026 new-gTLD round visible. Visibility matters: it exposes applicants, proposed strings and collisions to scrutiny. But the number now circulating is a receipt for paid applications entering a long process, not a measure of namespaces operating in the root or choices available to users.
Coverage
Market / Trends / Asia-Pacific Trends / Asia-Pacific Cloud Services Trends
In this section: 1 briefingSingtel’s token service sells a gateway; savings remain unpriced
RE:AI promises one governed route to multiple AI models and token-based billing. The public offer explains the control layer, but not yet a comparable price, customer saving or route-by-route residency map.
Coverage
Market / Trends / North America Trends / North America Datacenter Trends
In this section: 2 briefingsCelestica’s 11.1m-share offering shifts the AI test to cash returns
Celestica’s Q2 revenue rose 62% and its 2026 outlook moved higher, but the company also completed a primary share issue of 11.13 million shares to support working capital and capital spending. With receivables and inventory expanding and three CCS customers accounting for 63% of Q2 revenue, the useful question is how much of the growth reaches cash and earnings per share—not simply whether AI demand is strong.
Quanome’s $120m shelf leaves its $18.8m GPU order’s funding open
Quanome has described a possible securities offering and a large server purchase, but the public filings do not yet connect the two: registration capacity is not cash, and the purchase agreement puts most of its price before shipment.
Coverage
Governance / RIR Watchdog / RIPE NCC / Story
In this section: 3 briefingsDFINFRA's second tier: the live routing that a frozen registry cannot see
While the RIPE objects tied to DFINFRA — the role handle DA9499-RIPE, the organisation ORG-EDG14-RIPE and the silent AS210860 — have shown no meaningful change since October 2021, the 1996 legacy address block underneath them is being routed live and stably by a different network: AS197909, registered as EDEKA-RS. This briefing examines what that operational second tier actually does, how stable its routing is, and what the split between recorded holdership and routed reality can and cannot prove about control.
RIPE NCC October 2026 General Meeting: The Board Structure Vote and What It Says About Member Control
The RIPE NCC has published a draft agenda for its October 2026 General Meeting that goes beyond routine housekeeping: alongside the 2027 budget discussion, an Arbiter Panel election and a surplus-distribution vote, members will be asked to approve Articles of Association amendments that would formally make the Chief Executive a voting member of the organisation's board. With the final agenda set on 14 October 2026 and the 395-member support threshold for member proposals still untested, the meeting is shaping up as a direct test of how RIPE NCC members exercise control over their registry's executive.
Call for Nominations to the RIPE NCC Executive Board: What the 2026 Record Actually Publishes
The RIPE NCC has run a complete Executive Board nomination cycle for its May 2026 General Meeting. Reading the registry's own instruments — the call for nominations, the candidate and nomination procedure pages, and the document submission guidelines — shows a process that is administratively open and procedurally well documented, but whose public record tells members remarkably little about who is standing, what the board does between elections, or whether an outcome was contested.
Coverage
Governance / IETF
In this section: 27 briefingsThe Reflector Returned Eight Packets. It Still Had Not Measured the Application.
RFC 10052 lets one STAMP request produce a deliberately asymmetric reply train. That gives operators a useful way to shape active probes. It does not turn those probes into the application, convert a conformance bit into a capacity verdict, or collapse requested traffic, emitted traffic, observed traffic and user outcome into one fact.
The Token Can Authorize Access. It Cannot Key the Tunnel.
A proposed network-access method has removed a key it once claimed to derive. The revision is not a retreat from authentication; it clarifies which part of the system actually supplies the link key and which part merely accepts a bearer token.
A High Rating Did Not Make the RFC More Authoritative.
RFC-Editor.org has added ratings, subscriptions, personal sets and subject tags. These are useful controls over discovery and attention. They do not alter an RFC’s stream, status, update chain, errata state or implementation evidence—and a popularity feature remains under test rather than launched.
The Consultation Opened the Door. It Did Not Set the Fee.
The IETF has asked its community to comment on a new meeting-fee schedule. That is a meaningful procedural act, but it is not the decision. The proposal, the consultation, the Executive Director’s determination, Board approval, registration and effective participation remain separate facts.
A Private Transaction ID Is Not a Private Transaction
Two services can receive tokens for the same task without seeing the same transaction identifier. That sounds like a privacy boundary. A new OAuth proposal makes it explicit—and then admits that the rest of the token and the timing of its arrival may still give the task away.
The Calendar Called Them the Owner. It Had Not Granted Control.
A portable calendar record can call a participant an owner without making that person an authorized editor. The label describes a role; the exchange protocol still decides who may reschedule the event, change its participants, or send an update in its name.
The Channel Stayed Secure. Its Attested State Did Not Stay Current
Binding fresh attestation evidence to a TLS connection closes a dangerous substitution gap at the handshake. It does not freeze the endpoint’s software, policy or authorization state for the lifetime of that connection.
The Peak Had a Timestamp. The Fifteen Minutes Still Had No Sequence
A new BMP statistics format can expose the peak that disappeared between two identical snapshots. It still cannot say whether the route surge lasted seconds, dominated the window or arrived before the collapse.
The Site Reported Zero. Its Routes Could Still Remain in BGP
A revised edge-metadata draft turns one zero-value update into a site-wide forwarding decision. The control is compact; proving which routes, routers and live flows actually obeyed it is not.
The Allowlist Could Reach Zero Errors. First the Configuration Had to Be Complete
A new IntraSAV draft replaces route inference with explicit source-prefix authorization. Its strongest promise begins where the operational proof is still missing: the completeness of the configuration installed on each interface.
The Debug Header Named Every Step. It Could Not Prove Any of Them Happened
A new DKIM2 draft gives interoperability testers a common forensic trail inside the message. Its precision is useful precisely because its authority is deliberately zero.
The Refresh Ended. The Collector Still Needed Proof It Had the Whole RIB
A new BMP proposal can repair one stale routing view without tearing down every monitored session. Its ending marker closes a replay; it does not independently certify that nothing was lost inside it.
The SID Chose the Lane. It Did Not Prove the Lane Was There
An updated Segment Routing draft gives a SID resource meaning as well as forwarding meaning. That makes a packet's intended lane legible. It does not make bandwidth, buffers, queues or an SLA materialise at every hop.
The Tree Went Silent. The Alarm Came Back on a Different Road
A new BIER Working Group draft lets an active tail report multipoint BFD failure without waiting to be asked. The alarm returns by unicast on a path deliberately separated from the multicast tree—and that separation limits what the receipt can prove.
The Link Agreed to Sleep. That Did Not Mean It Was Safe to Disappear
A new IETF draft proposes a bilateral procedure for powering down lightly used traffic-engineered resources. Its most important sentence is not a power-saving promise but an evidentiary limit: sending a sleep request is not successful completion.
The Monitoring Option That Deletes the View
A new BMP draft tries to distinguish a quiet BGP feed from one that an operator has switched off. Its answer is useful—and more consequential than the name suggests. A Disable notification would instruct the collector to purge a scoped RIB view immediately, turning telemetry metadata into a remote deletion command.
The Configuration Succeeded. Its Trace Began Again
A device can accept a management change after rejecting the identifier meant to follow that change across the control stack. Two current IETF drafts make that split explicit—and force operators to decide how they will prove an action whose observability chain starts halfway through.
The Old Mechanism Was Deprecated. The Link Had Not Migrated.
One sentence in a new Internet-Draft can change the preferred future of a protocol. It cannot change the packet a router will accept tonight. The first draft to deprecate IPsec AH for OSPFv3 exposes the gap between standards direction and a live link: every attached router must cross the authentication boundary in a safe order, or the routing adjacency becomes the migration test.
The Route Was Installed. The Next Hop Did Not Understand Its Source Constraint.
The change record showed a clean install: destination, source prefix, next hop, metric. One hop later, the source qualifier had vanished from the forwarding decision. Revision 06 of an IETF routing draft turns that quiet compatibility gap into a leadership problem: the same route can be precise on one box and dangerous at the boundary of a mixed network.
A Healthy RadSec Proxy Could Not Prove the Home Realm
The access controller had a protected RadSec connection, a valid peer certificate and a prompt `Status-Server` reply. One customer realm still timed out. Nothing in those observations is contradictory: each belongs to a different hop, and revision 18 of the RadSec draft makes the jurisdiction of the green light unusually precise.
The Dashboard Still Showed 10,000 Valid Routes. They Were Not the Same 10,000.
The number survived the maintenance window without moving. That looked reassuring—until the operators compared the routes behind it. A new IETF YANG draft makes several RPKI validation totals observable across the BGP pipeline. It also makes clear why a total, detached from its stage, policy and route identities, is a dangerously incomplete receipt.
The Collector Counted CE. It Could Not Tell Which Service Was Marked
A dashboard reports 12,000 Congestion Experienced packets and divides them by the ECT(1) total. The percentage looks exact enough to justify a change to the low-latency service. Yet the packets now carrying CE no longer say whether they arrived at the marker as ECT(1) or ECT(0). The arithmetic can be flawless while the classification join beneath it is missing.
The Voucher Promised Another Voucher. Renewal Had Not Happened.
ANIMA's current onboarding draft gives a MASA room to project how long it expects to renew a device Voucher. Revision 36 also makes the later gates clearer. The projected date is still not a replacement artifact, a service-availability receipt or proof that the device completed onboarding.
The Draft Removed Two HPKE Modes. Running Code Did Not Disappear.
The proposed HPKE replacement reserves the two mode values that RFC 9180 used for Auth and AuthPSK. That is a clear standards decision; it is not an inventory of libraries, profiles, stored objects or counterparties that may still depend on the older compatibility set.
The Proxy Authenticated the User. It Did Not Authenticate the Source MAC
A green tunnel indicator can be perfectly accurate and still conceal the most important unresolved question: which Layer 2 identities may the authenticated user introduce into the remote broadcast domain? CONNECT-ETHERNET draws that boundary sharply. HTTP can establish the protected link; the operator must separately govern every Ethernet claim carried inside it.
The Server Returned the Old Object. It Did Not Return an Audit Trail.
JMAP Object History proposes a practical way to recover previous and destroyed object versions. Its own rules also explain why retained snapshots cannot prove every change, its actor, its authority or its outcome.
The Client Named a Trust Anchor. It Did Not Promise to Trust It
A server can follow a client's certificate-path hint exactly, send the path that the hint appears to request, and still watch the handshake fail. That is not a contradiction in the proposed TLS trust-anchor negotiation. It is the design's most important boundary: the client is helping the server choose what to present, not surrendering its authority to decide what to accept.
Coverage
Market / Companies / Global Companies / Global Cloud Services
In this section: 2 briefingsNovaCloud-Hosting's registry administration is split across three maintainers: who actually runs the operator's record?
NovaCloud-Hosting, the hosting brand of the Portuguese company Tech Tide Portugal Unipessoal LDA, operates its own autonomous system, AS209874. Previous BTW coverage mapped the routing footprint, the aftermath of the 19-day Frankfurt FFM2 outage of July 2026, and the fact that the brand sits under two distinct RIPE organisation handles [https://btw.media/en/novacloud-admin-registry-accountability]. What none of that reporting examined is the delegation layer beneath the organisations: who maintains and administers the operator's registry objects in practice. A direct read of public whois and RDAP mirrors on 1 October 2026 shows the answer is not one party but three — the operator's own maintainer, a German network company, and a UK sponsoring LIR — each with its own contact route, while the operator's commercial imprint presents a single unified surface.
One operator, two RIPE organisations: the administrative layer BTW had not yet mapped
Prior BTW coverage of NovaCloud-Hosting — the Portuguese-registered host operating under AS209874 — has tracked the gap between what the operator announces and what its network can actually deliver: five routing mirrors disagreeing on prefix counts, a registered /24 invisible in the global routing table, and the contradictory status pages surrounding the 19-day FFM2 outage of July 2026. What none of that reporting examined is the layer beneath the routing: who, in the RIPE registry, actually administers the operator's objects. A direct read of the registry record on 1 October 2026 shows an administrative footprint split across two distinct RIPE organisation identities, two different maintainer accounts and two different abuse routes — a structure the operator's own legal imprint does not disclose.
Coverage
Market / Trends / North America Trends / North America National Telecom Trends
In this section: 1 briefingThree carriers agree a satellite JV; existing deals stay separate
AT&T, T-Mobile and Verizon now have a joint-venture agreement and a founder-representative board. Yet the companies say their existing carrier-satellite agreements will remain in place, leaving the route from governance to one customer-facing platform open.
Coverage
Market / Trends / North America Trends / North America Cloud Services Trends
In this section: 1 briefingThryv’s 76% SaaS share still turns on a 24-month print clock
Thryv’s software now supplies most reported revenue, but the 76% headline is a mix ratio—not a growth rate. SaaS dollars were nearly flat in Q2 2026 as legacy marketing revenue collapsed; print-directory delivery timing moves that denominator, while normalized directory economics and a lower-margin customer migration show why the transition is more than accounting noise.
Coverage
Market / Trends / Global Trends / Global National Telecom Trends
In this section: 1 briefingBandwidth’s Salesforce deal sells the carrier side of a native contact center
Salesforce can make the agent’s workspace native to its CRM, but an international call still needs a number, a carrier and a route. Bandwidth’s planned 25-plus-country integration may package that side of the service; it does not yet prove that global voice has become a Salesforce feature everywhere.
Coverage
Market / Companies / Europe and Middle East Companies / Europe and Middle East Cloud Services
In this section: 2 briefingsA Price List Built on Peering It Cannot Show: Auditing almazcloud.network's Commercial Catalog Against AS210328's Measured Footprint
The operator behind the DIAMOND brand sells direct physical connections to some of the largest networks in Russia. Its own routing record lists no peers at all.
NovaCloud-Hosting one month on: PletX still listed, Trustpilot still closed
A month after NovaCloud-Hosting's own status pages declared the 19-day July 2026 Frankfurt outage resolved, the public record around the operator still points in several directions at once. The storefront advertises; a review platform declares the website closed; the operator's incident record blames one upstream while its network page still lists that same upstream as active. This briefing reads those sources directly as of 1 October 2026 and tests whether the gap between what is announced and what is operable — documented in prior coverage — has closed or widened.
Coverage
Market / Companies / Asia-Pacific Companies / Asia-Pacific Cloud Services
In this section: 2 briefingsRegistered but Not Routed: What DESEN Network Technology's APNIC Records Actually Show
Public registry data describes DESEN NETWORK TECHNOLOGY COMPANY LIMITED as an APNIC member holding a Hong Kong autonomous system and a portable /23. Routing data shows neither asset operating under the company's own control. A briefing on the gap between what a registry records and what a routing table observes.
AS142207: A Registry Record That Stays Active While the Routes Go Quiet
APNIC still lists WJY (Shanghai) Technology Co., Ltd. as the registrant of AS142207, but publicly observed routing for the autonomous system went quiet after early July 2026, and the website the network itself declares in PeeringDB names a different legal entity in Hong Kong. BTW's directory entry for the organisation has drawn reader questions because its slug contains the word "administrator" — that word denotes an APNIC registration role object, not a court-appointed insolvency administrator. This briefing separates what each layer of the public record actually establishes, and what it does not; BTW's own directory entry for the registrant collects the same layers at https://btw.media/en/directory/wjy-shanghai-technology-co-ltd .
Coverage
Market / Companies / Global Companies / Global Regional ISP
In this section: 2 briefingsShijiazhuang XuDing Technology Company Ltd: a Chinese-registered company inside RIPE NCC's registry, operating the CoreLink routing brand
Shijiazhuang XuDing Technology Company Ltd is registered in China, yet it is a Local Internet Registry of RIPE NCC, the European regional registry, and it operates AS42962 under the CLE-COMM name with the public brand CoreLink. Public routing data shows its own address allocations announced largely by other autonomous systems, and public sources disagree sharply about how many prefixes the network actually carries. This briefing maps the registration footprint, the routing evidence, and the open questions that remain.
Three Clocks, One Handle: What the ACSK-RIPE Record Does and Does Not Settle
When BTW last examined ACSK-RIPE, in August 2026, the question was what a contact handle in the RIPE Database can prove. A month later, the more interesting finding is not about the handle at all. It is that the three layers of the public record around ACSK-RIPE and AS210263 are moving on three different clocks — one frozen since 2018, one modified as recently as May 2026, and one silent since 2022 — and that none of them, read together, names an attributable operating party.
Coverage
Governance / CASE FILE
In this section: 3 briefingsTideo Administration: The Registry Record That Refused to Move
Nearly six months after AS210972 disappeared from the global routing table, the RIPE objects behind it — the aut-num, the organisation, and the role object "Tideo Administration" — remain exactly where they were in 2021 and 2023. Nothing was terminated, transferred or updated. This briefing documents that stillness and what it means for accountability.
Three Months After the Fine: No Follow-Up, No Appeal, No Documented Remedy for Svea Bank
On 17 December 2025, Sweden's financial supervisor Finansinspektionen (FI) gave Svea Bank AB (org. no. 556158-7634) a formal remark (anmärkning) and a sanction fee of SEK 170 million for breaches of core anti-money-laundering rules (https://www.fi.se/sv/publicerat/sanktioner/finansiella-foretag/2025/svea-bank-far-en-anmarkning-och-en-sanktionsavgift/). The decision, FI dnr 23-13249, contains exactly two operative points — the remark and the fee — with no remediation order (föreläggande) and no reporting obligation (https://www.fi.se/contentassets/d388bf1d1d1c47a1ac5dff513567510c/beslut-svea.pdf). Three months later, the public record shows what has and has not happened since: no FI follow-up against Svea, no appeal by Svea of this decision, and no independent, documented remediation from either of the two accountability channels that surround the bank — the regulator's sanction and the RIPE registry's annually validated abuse contact on the legacy netblock 193.105.138.0/24. Both channels verify signals. Neither yet proves that anything was repaired.
The Mailbox That Exists Only in the Registry: Svea's Abuse Contact and the Limits of "Valid"
When Svea Ekonomi AB merged into Svea Bank AB on 3 January 2022, the group's abuse-contact surface in the RIPE registry did not follow the merger. Nearly four years later, the routed legacy netblock 193.105.138.0/24 still presents a mailbox on a third party's domain — [email protected] — as its abuse contact on every independent mirror checked for this briefing. The same address appears as the abuse contact for netblocks belonging to Moore Europe Capital Management, IP-Only Networks AB and Rackspace Ltd., none of which have any connection to Svea. That pattern, and the fact that RIPE's required validation tests only technical deliverability, raises the question this briefing pursues: is this a functioning prevention and detection channel, or a contact that exists in the registry but operates nowhere?
Coverage
Governance / Number Resource Society
In this section: 2 briefingsThe October 2025 RIPE NCC General Meeting Had No Executive Board Election — and the Record Proves It
The RIPE NCC's General Meeting of 22–24 October 2025 in Bucharest was billed alongside RIPE 91 as a major governance gathering, but the registry's own agenda, minutes and voting report show a meeting with a single resolution and no Executive Board election at all. The one nomination call attached to the October cycle was for a seat on the Number Resource Organization Number Council — a different body entirely. Reading the October record closely tells members precisely which governance authority was, and was not, up for renewal.
The nomination funnel behind RIPE NCC's Executive Board election: what the May 2025 record actually shows
Every three years, the RIPE NCC membership nominates, supports and elects the people who sit on the body that governs the world's largest regional internet registry by membership count. The May 2025 election left a complete public record: a call for nominations under Article 9.1 of the Articles of Association, a list of verified nominees, a voting report, official results and meeting minutes. Read together, these documents reconstruct how an open nomination gate narrowed into a three-candidate, two-seat contest — and where that record stops short.