Content Type
Research
Within the Content Type facet, Research 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.
Story
The Svea Abuse-Role Record: Validated Contactability, No Documented Processing
The abuse contact recorded and mirrored for Svea's legacy netblock 193.105.138.0/24 is a carrier-era inherited mailbox on the Verizon Business/UUNET lineage — registry-validated for technical deliverability but never documented to have received, answered, escalated or remediated…
History
The Parser Could Skip the Chunk. It Could Not Know What It Meant: RFC 3072
RFC 3072 made an unfamiliar SDXF chunk traversable by giving it a boundary a reader could locate. But reaching the next chunk is not the same as understanding what was skipped—or knowing whether an application can safely ignore it.
Asia-Pacific Institutional
The Small Autonomous System: FPT Software and What AS131402 Actually Does
The Small Autonomous System: FPT Software and What AS131402 Actually Does 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…
History
The Label Was a Country Code. The Registry Could Still Be Generic: RFC 3071
In 2001, John Klensin argued that two characters could identify a country-code namespace without telling readers how its registry actually behaved. RFC 3071’s proposed categories followed operating practice—not the shape of the label—and stopped short of asking DNS administrators…
ICANN
If JPRS Fails, Who Keeps .jp Running? Reading the Successor Machinery in the .jp Record
Japan Registry Services Co., Ltd. (JPRS) has operated .jp since 1 April 2002 under an unusually public set of governing instruments. But the question of what happens if JPRS itself fails — bankruptcy, insolvency, or a decided re-transfer — has not previously been the subject of…
History
The Mask Promised a Neighbor. The VLAN Required a Router: RFC 3069
RFC 3069 saved IPv4 addresses by giving separated customer networks one shared prefix. But a host’s idea of “on-link” did not create a shared link: an upstream router had to answer, bind and forward.
History
The Tunnel Was Media-Independent. Its Circuit Was Not: RFC 3070
RFC 3070 made L2TP portable across a Frame Relay network, but portability did not make the bearer disappear. The tunnel still depended on a virtual circuit with its own endpoints, framing identifier, setup rules, packet-size limit and unresolved questions of service quality and…
Asia-Pacific Regional ISP
One Network That Moves Traffic, Two That Never Did: Inside NEXGENET COMPANY LIMITED's Operating Record
One Network That Moves Traffic, Two That Never Did: Inside NEXGENET COMPANY LIMITED's Operating Record intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the…
Story
Control Split: Who Held Prevention and Detection on the Svea Abuse-Contact Surface
Svea Ekonomi AB merged into Svea Bank AB on 3 January 2022, but the RIPE registry entities that describe the group's abuse-contact surface have barely moved since 2021 and 2022. A timestamp-by-timestamp reading shows that recent maintenance in this chain fell almost entirely on…
Europe and Middle East Institutional
Allianz Technology's Network Estate: Steady State for Some, Retrenchment for Others
The global SD-WAN programme that Allianz Technology SE announced in 2022 no longer appears in public records as a buildout. What the 2025–2026 record shows instead is an insourced service running in a steady operating rhythm inside Allianz Services, an unresolved datacenter count…
Afrinic SAGA
The Treaty That Says Nothing About the Registry: Inside Smart Africa's AFRINIC Authority Gap
Smart Africa's public engagement in AFRINIC governance runs on an internal board resolution and a series of statements, while its founding treaty — signed in Kigali, gazetted by Rwanda in 2023 — contains no provision mentioning AFRINIC or delegating any registry competence.…
CASE FILE
The Architecture of No Recourse: RIPE's Formal Abuse-Escalation Map
Every abuse complaint in the RIPE service region ends in a mailbox the registry validates for deliverability — and in an escalation architecture that, on the published record, offers the reporter no route into any binding mechanism. This investigation reconstructs that…
Global Cloud Services
Five prefixes, five answers: what AS210973's mirror disagreement teaches about trusting the record
Every monitor that watches the routing table tells a slightly different story about the small Vienna network operated by DATAMATIX Datensysteme GmbH. Reading those differences carefully — rather than averaging them away — is the fastest way to learn which layers of the internet's…
History
A Common Incident Object Was Not a Common Verdict: RFC 3067
RFC 3067 imagined a security-incident report that could cross organisational and national boundaries without losing the distinctions needed to act. Its strongest insight was not that every response team should reach the same conclusion. It was that they needed a common entity…
History
The Tag Named the Content. It Could Not Certify Understanding: RFC 3066
In January 2001, RFC 3066 gave Internet protocols a compact way to say which human language an information entity used. It also drew a line that systems still cross too casually: a valid label can guide selection and processing, but it cannot testify that a person will understand…
Number Resource Society
The Recognition Side of the Draft RIR Governance Document: Six Criteria, One Pipeline, and a Two-Thirds Gate
Before anyone can join the club, the club must first define who counts as a member, what a candidate must prove, who examines the proof, and who holds the final veto. That is precisely what Article 3 of the *Governance Document for the Recognition, Operation, and Derecognition of…
Global Institutional
DFINFRA and AS210860: When the Verification Layer Contradicts Itself
DFINFRA and AS210860: When the Verification Layer Contradicts Itself 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
The Ladder That Has Not Fired: What the Public Record Shows About Enforcement on the Svea Abuse-Contact Surface
When Svea Ekonomi AB merged into Svea Bank AB on 3 January 2022, the RIPE Database inherited a problem that no merger clause can settle by itself: the group's registered abuse-contact surface. Nearly four years later, that surface still carries the dissolved company's identity in…
Number Resource Society
Inside Article 6: How the Draft RIR Governance Document Would Make Derecognition Possible — and Unilateral Removal Impossible
The Governance Document for the Recognition, Operation, and Derecognition of Regional Internet Registries, delivered to the NRO Executive Council as a recommended draft on 28 July 2026, is best read not as a charter for expanding ICANN's power but as a procedure whose every step…
History
The Gateway Owned the Milliseconds. The Call Agent Still Owned the Call: RFC 3064
When circuit telephony met packet control, distance became a design constraint. RFC 3064 put reactions measured in tens of milliseconds beside the wire, inside the media gateway. It did not surrender the larger decision: the Call Agent still decided what the call meant, and a…