Source Verification: Read all 11 snapshots from sources/2026-11/net-8-and-net-9-reach-end-of-support-on-november-10-as-net-11-ships-microsofts-table-lists-november-14-2028-for-both-net-10-and-net-11/ (all HTTP 200, no archive fallback, suspicious_patterns null for all 11; snapshot hash of source-1 re-verified against the manifest). Because GitHub blob pages are rendered HTML, the dotnet/core Markdown sources were also read raw from raw.githubusercontent.com (releases.md sha256 28f82604727de966..., release-policies.md sha256 1ac8e94c454731cb..., support.md sha256 8c13a9b99adb86b8...) and GitHub issue #10448 plus its 8 comments through the GitHub API (gh api repos/dotnet/core/issues/10448 and /comments); the live raw text matched the snapshots on every point used. source-0 (Announcing .NET 11, dated November 10th, 2026): 'Today, we're excited to announce the release of .NET 11!' confirms the 'as .NET 11 ships' clause; '.NET 8 and .NET 9 reach end of support on November 10, 2026.' verbatim (the article's quote omits only the final period); 'Choose .NET 11 for the latest capabilities, or .NET 10 if its LTS lifecycle fits your requirements better.' verbatim; '.NET 11 is a Standard Term Support (STS) release with two years of support'; .NET Upgrade canvas 'gives you a visual view of a GitHub Copilot upgrade session' verbatim. source-1 (releases.md): supported table .NET 11.0 released November 10, 2026, STS, End of Support November 14, 2028; .NET 10.0 released November 11, 2025, LTS, End of Support November 14, 2028; end-of-life table .NET 9.0 released November 12, 2024, STS, final patch 9.0.23, November 10, 2026; .NET 8.0 released November 14, 2023, LTS, final patch 8.0.34, November 10, 2026. The page gives calendar dates only (no time of day or time zone), as the article states. Day counts recomputed: 8: Nov 14 2023 to Nov 10 2026 = 1,092; 9: Nov 12 2024 to Nov 10 2026 = 728; 10: Nov 11 2025 to Nov 14 2028 = 1,099; 11: Nov 10 2026 to Nov 14 2028 = 735; all four correct and labelled the Herald's count. The pairing of end dates (8 with 9, 10 with 11) is correctly labelled as the Herald's reading of the table. source-2 (11.0 README): 'will be supported on multiple operating systems for two years, from November 10, 2026, to November 14, 2028' verbatim. source-3 (release-policies.md): 'LTS and STS releases differ only by support duration' verbatim; 'Support ends for a given .NET version when its published end of support date has passed. Support typically ends on a patch day. ... There will not be any patches after that point. Continuing to use an unsupported version will expose you to security vulnerabilities.'; 'The month after a .NET version goes out of support, we mark that version as optional and out of support in Visual Studio'; '6 months after ... warning NETSDK1138'; STS two years, LTS three years. (Side note: the policy page's own sentence assigning STS to even-numbered and LTS to odd-numbered years does not match the releases table; the article does not use it.) source-4 (endoflife.date): 'Last updated on 14 October 2026'; 10 (LTS) 14 Nov 2028; 9 and 8 (LTS) 10 Nov 2026; list begins at 10 with no .NET 11 entry; the page's relative wording ('Ends today') is not reproduced in the article. source-5 (November 2026 servicing blog): 'The November 10, 2026 servicing updates for .NET 10, .NET 9, and .NET 8 include security and non-security fixes' verbatim (the same post's CVE table also covers .NET 11, which the article does not deny). source-6 (8.0.34 notes): dated November 10, 2026; source-7 (8.0.33 notes): dated October 25, 2026, out-of-band release for CVE-2026-111497 and CVE-2026-114148; the linked Herald briefing /article/2026-11/01-net-8033-... exists on main and has no corrections record. source-8 (DEVCLASS, Tim Anderson, 'tue 30 Jun 2026 // 20:16 UTC'): 'too short for upgrade and adoption cycles.' verbatim; Richard Lander described as 'program manager' by DEVCLASS; Lander said Microsoft 'had discussed longer support time frames and extended paid support offerings but has opted to continue with only the free support plan' (the article quotes only 'opted to continue with only the free support plan' and paraphrases the rest, accurately); the article's 2023 attribution matches ('A similar complaint in 2023 drew comment from program manager Richard Lander'). source-9 (issue #10448, opened by bh-sijtnic 2026-06-12T18:50:12Z, state open, 8 comments, last updated 2026-10-23): '~5 million lines of code' on .NET 8; 'LTS and STS converge on the same EOL date' verbatim; suggestions 'Longer LTS support duration' and 'Extended (possibly paid) support options' verbatim; comment by ryannewington 'I've got telemetry showing about 50% of the deployed versions of my software out there are running EOL versions' (the article's quote matches); comment by sujayvsarma 'Just because something is EOL or out of support does not mean that it stops working' verbatim; JuergenAuer 'Switching NET.8 to NET.10 - 5 minutes' (article: 'five minutes', paraphrased, accurate). Differing views are present as the article says. source-10 (support.md): Commercial support lists Canonical (on Ubuntu; '.NET 6 is supported in Ubuntu 22.04+', '.NET 8 is supported in Ubuntu 22.04+'), HeroDevs ('Never Ending Support (NES) for .NET 6+' on Windows and Linux), Microsoft, Red Hat (on RHEL) and TuxCare ('commercial support for certain out-of-support .NET versions'); no end dates or prices. One imprecision: the article says the page 'gives no support terms or end dates for these offerings', but the Canonical entry does state which .NET versions it supports on which Ubuntu releases (see corrections record, clarification). Absence and quantifier tests (jq/grep over title, summary and body): 'None of the cited sources reports Microsoft announcing paid extended support ... or a change to the three-year and two-year windows' checked against all 11 snapshots: grep for extended/paid support found only DEVCLASS's Lander passage (Microsoft declined) and the policy's generic 'extended period'; holds. 'None gives a count of applications still running .NET 8 or .NET 9': holds (only one commenter's telemetry about his own software). 'No cited independent item reports on the November 10 transition after it happened': holds for the two cited independent items (DEVCLASS June 30, endoflife.date last updated October 14). My own check of other outlets (WebSearch budget for the session was exhausted, so I fetched the outlets' current pages and feeds directly on November 10, around 17:15 UTC): InfoQ .NET news page and feed (latest .NET items: .NET 11 RC2, RC1, previews; newest feed item October 28), The Register headlines Atom feed (latest items November 10, none on .NET), DEVCLASS development section (latest .NET item is the February .NET 11 preview 1 report plus the June 30 piece), heise developer Atom feed and page (only betterCode() .NET 11.0 conference promotions), Phoronix RSS (none) and Visual Studio Magazine RSS (latest November 9, none on .NET end of support). HeroDevs's own site carries a guide titled 'The .NET Cliff: What Happens When .NET 8 and .NET 9 Stop Getting Patched', i.e. a vendor with a commercial interest, not an independent outlet and not cited. TuxCare's page returned HTTP 403 and was not read; the article makes no claim that depends on it beyond Microsoft's one-line description. Limits of this check: it covers feeds as they stood at fetch time, not an exhaustive search, and the article's absence claim is correctly scoped to the cited sources. Independent-source recount: Microsoft first-party sources = 8 of 11 (two devblogs.microsoft.com posts and six dotnet/core Markdown pages: releases, 11.0 README, release policies, support, 8.0.34 notes, 8.0.33 notes); independent of Microsoft = 2 (DEVCLASS, endoflife.date), both pre-dating the event; issue #10448 is a third-party user's text hosted in Microsoft's repository (a primary record of the complaint, not independent reporting on the transition). Not required for News (no Analysis threshold). Allowlist: devblogs.microsoft.com (line 884), github.com (line 1162), endoflife.date (line 1900), devclass.com (line 1999) all present; learn.microsoft.com is present but not cited; dotnet.microsoft.com is not cited; vendor hosts (herodevs.com, tuxcare.com) are not cited sources, only named via support.md. No allowlist additions needed. Anthropic disclosure: not required - the article is not about Anthropic or an Anthropic product, names neither in headline/summary/lead nor in any passage (no 'Anthropic' or 'Claude' in the body; the only hits in the snapshots are endoflife.date's site navigation).