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.
IETF
An SRv6 Locator Lease Makes DHCPv6 Part of the Routing Control Plane
An SRv6 locator is the address-space foundation from which a segment endpoint creates SIDs. RFC 10038 allows that foundation to arrive as a DHCPv6 lease. The convenience is real, but so is the transfer of authority: pool selection, lease renewal, route installation and withdrawal…
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.
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.
Number Resource Society
An IPv4 Transfer Pre-Approval Needs a Registration-and-Expiry Ledger
An IPv4 transfer pre-approval answers a narrow question: how much address space a recipient may qualify to receive during a defined period. It does not identify a source, complete a transfer or prove that the registry has changed.
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…
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 Object, 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.
History
The Window That Closed Without Ending the Connection: TCP Persist
When a TCP receiver says it has no room left, the sender stops sending ordinary data. The harder question is how either side escapes that pause if the one message announcing new room never arrives.
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.
History
The Number Made Harder for an Off-Path Attacker to Predict: TCP Initial Sequence Numbers
A TCP connection begins by exchanging numbers. The security change was not to hide that exchange, but to stop one visible number from revealing the next connection's starting point.
Story
AFRINIC’s RDAP ipVersion Describes This Record, Not IPv6 Readiness
An IPv4 lookup naturally returns an IPv4 entity. That simple fact becomes misleading when `ipVersion: v4` is promoted from a property of one AFRINIC record into a verdict on an organisation’s entire network.
Story
RIPE’s RDAP Type Classifies a Registration, Not the Route Origin
RIPE’s RDAP Type Classifies a Registration, Not the Route Origin 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. The…
Story
AFRINIC Received 1,024 ASNs. The Public Record Separates Inventory from Allocation
IANA recorded a new 1,024-number block for AFRINIC on 25 February 2026, and AFRINIC announced the addition to its inventory on 27 March. Those records establish upstream custody, not downstream allocation of every number to operators.
Global Regional ISP Trends
A Graceful BGP Restart Can Lengthen a Blackhole
Graceful Restart is meant to keep traffic moving while a BGP process returns. Its safety depends on a fact the surviving session cannot prove by itself: whether the restarting router still has the forwarding state needed to carry packets. When a helper retains a route longer than…
Europe and Middle East Regional ISP Trends
PKP Ferrit’s registry footprint makes operator identity a due-diligence question
PKP Ferrit’s public records connect a company name, an Internet-number allocation and an observed route origin. They do not collapse those layers into proof that one organisation currently controls every operational or contractual part of the service.
IETF
The Second Address Became the Primary One: What RFC 9873 Changes in EPP Contact Data
RFC 9873 turns a contact update into a more explicit state transition: an EPP contact may carry one additional email address, and an optional `primary` attribute says which address is to be treated as primary. The protocol records that relationship; it does not certify the…
Story
APNIC’s RDAP Active Status Describes a Registry Object, Not Route Reachability
The word `active` looks like an operational verdict. In an APNIC RDAP response, however, it belongs to the registered entity—not to a live measurement of routes, packets or services.