Content Type
Briefing
Within the Content Type facet, Briefing intelligence gathers BTW.MEDIA articles that share the same editorial format, helping readers compare briefings, profiles, risk notes, market analysis, and event coverage without mixing different kinds of evidence. The page explains how this content type frames internet infrastructure events, company movements, governance decisions, operational signals, and public evidence across the site. Readers can compare which actors or infrastructure systems appear most often, how source quality changes interpretation, and whether the material is a durable profile, a time-sensitive event, a strategic market signal, or a governance development. The result is a useful search page for operators, investors, customers, analysts, and policy stakeholders who need to understand the consequence, timing, and evidence behind similar article formats.
North America Datacenter Trends
ChronoScale plans 50MW Microsoft AI deployment for Q1 2027
ChronoScale plans a 50MW NVIDIA GB300 deployment for Microsoft in North America, with completion targeted for the first quarter of 2027.
Europe and Middle East Institutional
Haffner launches biomass power-and-cooling offer for data centres
Haffner Energy has launched a modular biomass system that combines onsite power generation with cooling for data centres operating alongside the grid.
Europe and Middle East National Telecom Trends
An alternate coordination room is not a local continuity site until access, data, call routing and staffing are exercised
An address on a continuity plan does not prove that an alternate coordination room can take over. The capability begins only when authorised people can enter, receive the right calls and data, recover the current incident picture and accept command responsibility under controlled…
Europe and Middle East Datacenter Trends
Telehouse opens 5.4MW Building N in Frankfurt
Telehouse has opened Building N in Frankfurt, adding 5.4MW of live capacity at its established Kleyerstraße data-centre campus.
NANOG
What NANOG's Public Record Says—and Does Not Say—About Recusal
Technical peer review works because reviewers know the field. That is also why conflicts cannot be treated as an exotic exception. NANOG's Program Committee evaluates proposed talks. As a bounded governance premise, any specialised technical committee may bring reviewers and…
North America Datacenter Trends
Gradiant wins West Texas AI data-centre water contract
Gradiant will supply potable-water and wastewater systems for an unnamed hyperscale AI data-centre campus under development in West Texas.
Story
ARIN's RDAP Transition Needs Evidence at Three Different Exit Gates
ARIN wants one standardized directory protocol in place of three older services. The destination is coherent; the operational test is whether Whois-RWS, RWhois and Port 43 can each leave on evidence suited to the users and dependencies they actually carry.
Story
RIPE NCC’s RDAP Country Code Does Not Geolocate the Network
A two-letter country code looks ready for a map. In a RIPE NCC RDAP network entity, however, it is a registration field—not a set of coordinates and not live evidence of where routers, users, traffic or services are located.
Global Cloud Services Trends
A QUIC Connection ID Is Not a Subscriber Identity
A QUIC connection can survive a change from Wi-Fi to mobile access. The identifier that helps packets find that connection is transport state, not proof of who holds the handset, which account is active, or whether an application action remains authorised.
North America Regional ISP Trends
Plus Analytics: what an invisible route can and cannot prove about a VPN
Plus Analytics presents privacy as a service outcome. Its public number-resource record presents a different entity: administrative control. The gap between them is where a buyer’s diligence should begin, not where a verdict about the service should end.
Story
APNIC’s RDAP objectClassName Defines a Schema Class, Not a Network Role
The label `ip network` appears near the top of an APNIC RDAP response. It is easy to read it as a description of what an organisation does. Its real purpose is narrower and more useful: it tells software which RDAP entity schema it is processing.
Story
APNIC prop-170 Must Price the Space Between IPv6 Need and Nibble Alignment
A technically valid IPv6 prefix is not always an easy unit to operate. APNIC prop-170 would let an LIR request the smallest nibble-aligned allocation that satisfies an already validated need. The proposal promises cleaner plans without abandoning needs-based allocation; its…
NANOG
Membership Is a Mandate With Edges
NANOG membership creates real authority inside the association. It does not turn a corporate electorate into every network operator in North America.
Number Resource Society
A Number-Resource Policy Decision Needs an Adoption-and-Implementation Ledger
A consensus announcement is useful evidence, but it is not by itself a complete answer to what text applies or when an operational change took effect.
Europe and Middle East Regional ISP Trends
PLAZMATELEKOM's 20,000-subscriber claim still leaves the last mile to verify
PLAZMATELEKOM presents itself as a regional network with 20,000 active subscribers, 120 connected settlements and fibre across Ingushetia's larger population centres. The useful question is not whether those figures sound substantial, but what they mean at a specific address when…
Story
ARIN’s RDAP Remarks Qualify This Entity, Not Every Registry Record
Human-readable text inside an RDAP response can look like a general registry instruction. Its location matters. In ARIN’s live entity response, Registration Comments sit inside a particular entity entity, while service terms and reporting notices occupy the response’s top level.
Global Cloud Services Trends
A Fast 0-RTT Handshake Is Not a Once-Only Transaction
TLS 1.3 and QUIC can remove a round trip from a resumed connection. That is a latency result, not a receipt that a state-changing request reached the application once, was committed once, and will never be replayed elsewhere.
CASE FILE
The Certificate Challenge Crossed the Delay. Authority Did Not: RFC 9891
RFC 9891 carries an ACME proof through a delay-tolerant network, but it carefully stops the proof at control of a Node ID during one policy-bound exchange. Everything beyond that boundary still needs its own evidence.
Europe and Middle East Regional ISP Trends
Platon's 99.9% uptime promise leaves the failure boundary to verify
Platon Technologies presents a compact hosting proposition: its own infrastructure, a stated availability guarantee and two optical routes to the exchange SIX. The useful diligence question is not whether those claims sound reassuring, but where each promise begins and ends.
Story
LACNIC’s RDAP Self Link Locates the Record, Not the Network’s Serving Infrastructure
A URL inside a registry response can look like an infrastructure clue. In LACNIC’s RDAP output, however, `rel: self` tells a client where to retrieve the registration entity; it does not say where the registered network’s traffic, applications or authoritative services run.