Topic
Network-resource Evidence
Within the Topic facet, Network-resource Evidence topic intelligence connects articles that share a specific subject, signal focus, or monitoring theme. The page gives readers a richer path through related reporting, source evidence, market actors, and infrastructure implications, with enough context to understand why the topic matters across company movements, governance decisions, regional exposure, and operational risk. Readers can compare recurring signals, affected organisations, public evidence, market context, service continuity, procurement, competition, compliance, and strategic planning questions behind the subject instead of stopping at a thin list of matching articles. It explains what the topic covers, which infrastructure actors or policies are involved, what evidence supports the coverage, and why the subject may matter for operators, customers, investors, and policy readers.
Story
RIPE’s New IP Family Tree Has One Useful Rule: Odd Is Not Broken
An address hierarchy can look untidy for perfectly ordinary reasons. RIPE NCC’s new resource checks are most useful when they show what they found before announcing what an operator should fix.
Leaders
Cathy Aronson Was Asked Which Stranger’s /8 an ISP Could Borrow
The question arrived as if the Internet had a spare key under the mat. A large ISP wanted more internal IPv4 space and asked Cathy Aronson whether 22.0.0.0/8 or 30.0.0.0/8 was safer to use. She checked the premise before answering. The numbers already belonged to someone else's…
Leaders
Adiel Akplogan Got Africa's IP Address Desk Running Before the Final Vote
The letter asking ICANN to recognize AfriNIC as a regional registry arrived after its staff had begun handling African number-resource requests. Akplogan's case was built with a database, trained hostmasters and a borrowed second opinion.
Story
ARIN wants a five-year IPv6 plan. The next block still waits on 75%.
ARIN’s draft swaps several utilization tests for a network plan, then makes that same plan the clock on an LIR’s next request. The percentage sounds familiar. Its denominator is new—and the draft leaves one piece of the arithmetic on the table.
Leaders
Robert Kisteleki Put a Clock on the Internet Archive
RIPE Atlas and RIS keep extraordinary histories. Kisteleki asked the awkward question every archive eventually meets: who pays for a fast door into old data?
Story
Publishing ASPA Is the Easy Part. Getting It Into a Router Is the Plot.
LACNIC has put ASPA creation in MiLACNIC and validation in FORT. The interesting handoff comes next: a valid object still has to travel through a validator, a router protocol and a local routing policy before it can change a decision.
CASE FILE
The cable is fixed. The number is not.
Hawaiki has carried commercial traffic across the Pacific since July 2018 on the same three fibre pairs, over the same roughly 15,000 kilometres, between the same five landing points. Its published design capacity, depending on which document you open, is either 43.8 Tbps or 67…
CASE FILE
One Bad BGP UPDATE. Four Possible Fates.
BGP’s old emergency response had the charm of a fire alarm with one button: a malformed UPDATE could bring down the whole session. Draft -03 of the revised BGP-4 specification puts four levels of response into the base text, from ending a peering to dropping one harmless…
Story
The RIPE Atlas Heat Map Can Turn an Outage Green. Start the Clock Earlier.
RIPE Atlas added a useful view of anchor-to-anchor delay and loss. Its green tiles answer a narrower question than most readers expect: how much slower is this bucket than the fastest one in the window you chose?
Story
REGULATEL Has the Working Group. LACNIC Has the MOU. Give Them a Job.
LACNIC and REGULATEL have signed a broad cooperation pact. REGULATEL already has an Internet Affairs group with a remit for technical and governance work. Put the agreement there and ask for an output with a date.
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.
History
The Capture File Looked Immaculate. The Packets Had Other Plans.
A saved trace can give an incident meeting the reassuring weight of a physical entity. RFC 1761 put a label on what that entity actually contains—and on several things it might have missed.
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.
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.