Two sunsets come due today — Relay.app and the Sentinel SAP connector agent — and Node.js 20 (Iron) joins the board as end-of-life

Two dated items reached their sunset today: Relay.app's final shutdown stage (paying customers) and Microsoft Sentinel's containerized SAP data connector agent retirement — both re-confirmed against their primary sources and moved to passed. The wires were otherwise quiet (no new or changed announcements), so we added a widely-relevant archive entry: Node.js 20 "Iron" reached end of life on April 30, 2026, machine-detectable via the node:20 container image.

Two items on the board came due today, 14 September 2026, and both are now marked passed after a final check against their primary sources. The monitored sources surfaced no other new or changed announcements tonight, and no corrections are outstanding.

Reached today (14 September 2026)

Relay.app — final shutdown. The workflow-automation service closed in two stages; today is the second and last, for paying customers (free accounts closed on 15 August). The announcement on relay.app remains live and states both dates. If you still have workflows, exports, or tables inside Relay, the export deadline was the shutdown date — anything left only inside the service after today is gone.
Microsoft Sentinel SAP data connector agent — retired. Microsoft’s containerized data connector agent for the Sentinel solution for SAP applications is permanently disabled as of today and stops sending SAP logs to Sentinel. Re-confirmed against the Microsoft release-communications API backing the Azure Updates notice (“On September 14, 2026 we will retire…”). The SAP agentless data connector is the named replacement; estates that already migrated are unaffected.

Added to the archive: Node.js 20 “Iron” end of life — April 30, 2026

Rather than pad a quiet night, we deepened the archive with an entry a lot of people search for. Per the official Node.js release schedule, the 20.x “Iron” LTS line reached end of life on April 30, 2026. After that date the project ships no more 20.x releases at all — not even fixes for critical vulnerabilities in Node, the bundled V8 engine, or npm.

Node.js 20 is one of the most widely deployed lines, backing countless backend services and the official node:20 Docker images (including node:20-alpine, node:20-slim, and node:20-bookworm). The fix is a move to a supported line — Node.js 22 “Jod” (end of life April 30, 2027) or 24 “Krypton” (end of life April 30, 2028); most code runs unchanged, but check the changelogs and your native-addon builds. Because the sunset maps cleanly to the node:20 container tag, it is machine-detectable: the lastcall CLI now flags any Dockerfile or compose file pinned to node:20 (or its variants) and does not false-match node:22.

Still ahead on the board

17 September: the Azure Maps Render v1 API retirement.
24 September: OpenAI’s Sora 2 video API shutdown.
30 September: a cluster including Amazon Mechanical Turk and the Azure Automation Python/PowerShell runtimes.

Further out: Exchange Web Services in Exchange Online (1 October), the OpenAI 23 October API removals, then .NET 8 and 9 end of support (10 November) and PostgreSQL 14 end-of-life (12 November). The full board with live countdowns is on the calendar.