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.
Story
ARIN moved a mountain of legacy addresses in one quarter. The rocks left are large
A newly disclosed 2025 agreement surge dwarfs the later remaining stock. The next cases look less like a bulk move and more like a hard address book.
Story
RIPE built a dashboard that has to learn when to shut up
Its new resource checks can spot useful anomalies. The more revealing design choice is how the registry labels an unchecked branch or an odd but valid route.
Story
RIPE put a diff on the registry. Mind the missing pages
The new comparison view makes a resource record's edits easier to see. Its blind spots deserve the same attention as the bright lines.
Asia-Pacific National Telecom Trends
A Spectrum Licence Goes First. The Transmitter Still Has Homework.
ACMA will license an area and frequency range before it coordinates the transmitter that might use them. The map can be approved while the antenna is still filling out forms.
Story
RIPE threw out the database cookie. The maintainer still holds the pen
A new login at the registry door is live. The useful question is what happens after the door opens.
Story
The customer left. RIPE's sponsorship bill needs a form
A dissolved customer agreement does not update the registry. RIPE NCC says sponsoring LIRs need one specific request before the year-end fee snapshot.
Story
RIPE's year-end exit has an IPv6 question hiding in the box
A member closing its LIR before the 2027 billing cycle has paperwork to finish and one resource decision to make: does that IPv6 allocation still have a job?
Story
ARIN's IPv4 transfer clock is filed under “source”. Recipients miss it
An IPv4 transfer can close today while the date of the next one is already being set. ARIN tells recipients about the wait, but its policy manual posts the clock under their future role.
Story
ARIN put IPv4 fraud on its IPv6 slide. Show the bill
An IPv6 pitch now includes the price of chasing dodgy IPv4 claims. The registry has described the chase, but left the price tag off the slide.
Story
RIPE's address book has IANA on 166 lines. Time to find the real contacts
The registry says it will contact users about 166 database entities pointing at its IANA role. A valid handle is a poor substitute for the person who can pick up the phone.
Story
RIPE shut the extra-account door. The IPv4 queue added 20
Weeks after the registry restricted extra LIR accounts, its published IPv4 queue got longer. The two numbers belong on the same desk, even though different hands control them.
Story
ARIN's fee scale: 1,644 big accounts balance 23,124 small ones
The registry's September fee snapshot looks like a balance scale with a tiny pan and a crowded pan. They carry almost the same annual revenue run rate. That is a useful picture of whose holdings make ARIN's budget move.
Story
Port 43 got 43 comments. Twenty-four told ARIN to slow down
ARIN planned a tidy retirement for old-fashioned Whois. Its own meeting slides reveal an untidy guest list: most substantive commenters pushed back, and the busiest apparent users hide behind cloud-provider addresses.
Story
Five registries walk into an ASPA chart. One brings zero
ARIN's routing-security slide counts 3,389 signed provider statements across the RIRs. RIPE NCC holds the largest pile; AFRINIC's column is empty. A shared tool is arriving in five very different starting positions.
Story
LACNIC Wants 80% ROA Coverage. Its Evidence Counts Something Else.
A LACNIC proposal would make valid ROA coverage a condition for an organization’s next resource allocation. The 80% threshold is crisp; the evidence cited for it measures regional route validity, a different quantity.
Story
AFRINIC’s Policy Digest Has a 20-Message Door Policy
A new proposal repairs broken email threads, then hands digest access to a traffic counter.
Story
Four blocks on the slide, one in your hand: ARIN's waitlist math
ARIN's own example puts four separate /24 blocks on the table. Its current rules let a qualifying applicant take one. The question is whether neat routing still deserves the last word on a scarce address queue.
Story
RIPE opened the BGPsec key desk. The routers are still catching up
AS holders can now manage router key certificates through RIPE NCC's RPKI API. The issuing desk is ready; path validation still depends on the equipment at each end.
Story
RIPE's duplicate records have two exit doors—and one arithmetic trap
RIPE NCC wants to retire redundant entries from its non-authoritative routing database. The proposed tests sound simple until their totals are added together.
Story
IPv6’s Rulebook Is Adding the Audit Chapter It Forgot to Label
RIPE’s open proposal would give IPv6 policy an explicit route to audit and LIR-closure procedures already named in IPv4 policy and the member agreement. The new heading matters because a rule is easier to operate when the reader can find the machinery behind it.