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.

Global Regional ISP Trends
A Completed Route Refresh Is Not a Policy Reconciliation
Route Refresh lets a network replay BGP reachability without resetting the session. The exchange can finish perfectly while the operational question remains open: did the intended policy revision reach the right routers, act in the right direction and produce the expected…

IETF
A QUIC Stateless Reset Proves a Token Match, Not Why State Was Lost
A client can recognize that its peer no longer has usable QUIC connection state without learning which machine, deployment or routing decision made that state disappear.

Europe and Middle East Regional ISP Trends
Professional Programming Company: when a registry-linked address block is not proof of delivery
Professional Programming Company Ltd. markets connectivity, cloud and managed IT services in Saudi Arabia. RIPE links an ALLOCATED PA /22 entity to its organisation record, yet RIPEstat saw no public origin for that block on 5 September 2026. The gap is not an outage verdict. It…

History
The Translator That Changed the Authenticated Connection: TCP-AO and NAT
A middlebox can change a packet without changing its route. TCP-AO made the consequences depend on what changed: rewriting a TCP option could be accommodated by authenticating fewer fields, but rewriting an address or port changed the identity of the protected connection itself.
Story
LACNIC’s measurement commons turns regional latency into operating evidence
A latency chart is not a verdict on a country’s Internet. It becomes useful when operators can see the probes, time window and comparison behind it—and when the result leads to a question that can be tested again.

Story
AFRINIC Reported Unauthorised Routes from Reserved IPv4 Space. Full Withdrawal Was Not Yet Confirmed
AFRINIC described route announcements involving parts of 102.224.0.0/12 and several response actions; its notice did not close the record on full withdrawal.

IETF
The New IETF Steering Draft Says Drop. A Legacy Headend May Still Redirect
A failed steering instruction can now produce two opposite-looking outcomes. Revision 18 tells a supporting headend not to fall back to ordinary IP redirection when explicit Segment Routing intent is incomplete or unresolved; it must drop the matching traffic or use a declared…

History
The Reset That Could Not Be Trusted: TCP-AO After a Peer Reboot
TCP normally has a blunt way to tell a peer that an old connection no longer exists: send a reset. TCP-AO makes that answer harder to trust on purpose. When a protected peer reboots and forgets its connection state, the reset it can still send may be precisely the reset the…

Story
AFRINIC's Monitoring Button Is Deployed and Disabled
AFRINIC's deployment monitor contains the control announced in its August release, but not the address that would make the control usable. The public code handles that absence carefully: it leaves the button hidden. That is good failure behaviour. It is also evidence that a…
Story
LACNIC’s RPKI controls make route origin authority operable
LACNIC’s RPKI controls make route origin authority operable 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…

Number Resource Society
An ASPA Is Not a Complete AS-Path Attestation
An ASPA can help an operator test whether an AS path is consistent with published customer-to-provider authorizations. That is valuable route-leak evidence. It is not a signature over every hop, a proof of route origin, a commercial contract, or a guarantee that the published…

Global Regional ISP Trends
When RPKI Validators Disagree, Redundancy Becomes a Policy Choice
Two healthy validators can give different answers about the same prefix. The moment an operator chooses which answer reaches a router, validator redundancy stops being a box-counting exercise and becomes a routing-policy decision.

Europe and Middle East Regional ISP Trends
DORIS: what a detailed routing policy proves when no routes are visible
DORIS: what a detailed routing policy proves when no routes are visible 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.…

IETF
QUIC Migration Can Fail Before the Connection Does
A QUIC connection can remain cryptographically alive while becoming unable to use a new path. The missing resource may be neither keys nor congestion window, but an unused connection ID supplied by the peer.

Number Resource Society
An RPKI Cache Serial Is Not a Freshness Timestamp
Two RPKI caches can report perfectly accurate serial numbers and still tell an operator nothing about which cache holds newer global data. RFC 8210 scopes a serial to one cache session and protocol version. Treating the larger number as the fresher view manufactures a chronology…

History
The Segment That Returned to the Same Number: TCP-AO's Sequence Number Extension
A TCP sequence number can come back during one long-lived connection. TCP-AO had to ensure that the repeated 32-bit value did not also repeat the evidence presented to its authenticator.

Europe and Middle East Regional ISP Trends
Farlep-Invest: the missing fault map behind a 100-hour continuity claim
Farlep-Invest says Vodafone Gigabit Net home-internet customers can remain online for more than 100 hours during central-power outages. The number is striking. Its real value, however, depends on a fault map the public filing does not provide: which network segments are…
CASE FILE
The Notification Arrived. One Backend Still Had Nothing to Serve
The IETF is asking for final comments on a proposed operating guide for RPKI publication services. Its sharpest rule is also the easiest to violate during a routine rollout: do not expose the new notification until every snapshot and delta it names is already available. An index…

IETF
QUIC's Three-Times Limit Is an Address-Validation Budget, Not DDoS Protection
A QUIC server can have the next handshake bytes ready and still be forbidden to send them. Before it knows that a client can receive packets at its claimed address, every received byte grants only a bounded amount of transmission credit.

Global Regional ISP Trends
A QUIC Connection ID Is Not a Durable Principal
A connection identifier can keep a QUIC session reachable while the network path changes. That continuity is operationally useful, but it does not turn the identifier into an account, a subscriber or a durable statement about who is authorised now.
