Content Quality: Well-structured News piece (932 words, within the 400-1200 News range): Overview, What changed, How the tunnel works, The security model AWS describes, What we don't know. Technical mechanics (GENEVE encapsulation over UDP 6081, resource gateway address translation, AZ-overlap requirement, TCP-only traffic) are explained accurately and the 'What we don't know' section correctly flags the absence of a numeric per-VPC quota, adoption figures, and relative endpoint-type pricing. Neutral, non-promotional tone throughout.
Source Verification: All 3 source snapshots read in full from decompressed .html.gz files (sha256 verified against manifest.json: source-0 e46ca620...c4fe1, source-1 0d4d2d28...f4910, source-2 6ba36fd3...7b6a3 -- all match). (1) AWS Networking & Content Delivery blog 'Introducing tunnel endpoints...' by Bruce Pinsky and Ashish Kumar, dated '05 NOV 2026' in the byline -- matches article's Nov 5, 2026 publish-date claim. Every direct quote in the article ('to share resources with a vendor, the customer had to enumerate them individually by creating a resource configuration for each using IP address or DNS name'; 'was limiting for use cases where resources are ephemeral or aren't knowable up front'; 'represents a network segment as one or more IPv4 or IPv6 CIDR ranges'; 'the consumer and provider VPCs can use overlapping CIDR blocks'; 'Resources located outside the perimeter can't be reached by the vendor'; 'Connections (TCP SYN) can start only from the consumer VPC, not from the provider network'; 'grants access to everything the provider VPC can reach'; 'share the narrowest ranges that cover the workload(s)') was found verbatim in this snapshot. (2) AWS What's New announcement, 'Posted on: Sep 18, 2026' -- matches article's Sep 18, 2026 launch-date claim; confirms the pre-launch state was one-resource-at-a-time sharing and lists 28 regions across the Americas, Europe, Africa and Asia Pacific, consistent with the article's 'more than two dozen ... spanning the Americas, Europe, Africa and Asia Pacific.' (3) InfoQ, 'AWS PrivateLink Tunnel Endpoints Open a Whole CIDR Range to Another Account' by Steef-Jan Wiggers, dated Nov 18, 2026 -- matches article's Nov 18, 2026 coverage-date claim; the article's quoted sentence ('lets an application in one VPC reach every address in a CIDR range shared from another account, instead of one resource at a time') is verbatim from this snapshot, correctly attributed to InfoQ rather than to AWS. No hallucinated quotes, no misattribution found. Independence: sources 1-2 are AWS's own blog/announcement (not independent of the subject); source 3 (InfoQ) is independent editorial coverage -- 1 independent source. This is a News submission (3-5 sources minimum per editorial_policy.md), not Analysis, so the Analysis-only 2-independent-source requirement does not apply; the News sourcing minimum is met (3 sources). Both aws.amazon.com and infoq.com are already present in config/source_allowlist.txt -- no allowlist addition needed. Anthropic disclosure: not required - article does not mention Anthropic, Claude, or any Anthropic-operated product.
Factual Accuracy: Ran the claim-accuracy quantifier scan (absence/every/only/never/first/last etc.) against the body and checked each flagged sentence against the raw source text. All checked: the 28-region count supports 'more than two dozen'; the Sep 18/Nov 5/Nov 18, 2026 dates all match each source's own byline/posted date; all absence claims in 'What we don't know' (no numeric per-VPC quota, no adoption figures, no relative pricing across endpoint types) are confirmed true of both AWS sources. No derived/computed figures are presented as the Herald's own (the region count is AWS's own list, correctly characterized). No disagreements between sources requiring attribution. No fabricated specifics found.
Overall Assessment: Clean, accurate News submission. All three sources read and verified in full from disk; every direct quote is verbatim and correctly attributed; the central novelty claim was independently checked against all three sources (including both of AWS's own posts) and third-party commentary, and holds up as a genuine new capability rather than a rebrand. No corrections needed. Featured candidacy: 0 - solid, accurate vendor-feature coverage for a cloud-networking audience, but a routine documentation walkthrough of an already-launched (Sep 2026) feature, not a broadly significant or industry-changing story.