<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>LaunchNotes incidents — Vendor Status Watch</title><link>https://approjects-vendor-status-watch.static.hf.space/v/launchnotes.html</link><description>Incidents from LaunchNotes's public status page, polled daily.</description><lastBuildDate>Wed, 16 Sep 2026 12:28:20 +0000</lastBuildDate><item><title>Notifications sent using the LaunchNotes email service provider may not be delivered on time [resolved]</title><link>https://status.launchnotes.com</link><guid isPermaLink="false">launchnotes:2026-05-04T19:23:13Z</guid><pubDate>Mon, 04 May 2026 19:23:13 +0000</pubDate><description>Sending has been restored.</description></item><item><title>Announcement content changes not persisting [resolved]</title><link>https://status.launchnotes.com</link><guid isPermaLink="false">launchnotes:2025-11-04T16:21:00Z</guid><pubDate>Tue, 04 Nov 2025 16:21:00 +0000</pubDate><description>We recently made changes to our GitOps process to further improve how we deliver software. As part of that change, we introduced a small bug that broke name resolution between our core service and our content service. This resulted in content changes not showing on our public pages.  We implemented and deployed a fix and have confirmed all content persistence and caching is functioning correctly.</description></item><item><title>Services are unresponsive [resolved]</title><link>https://status.launchnotes.com</link><guid isPermaLink="false">launchnotes:2025-09-04T16:51:01Z</guid><pubDate>Thu, 04 Sep 2025 16:51:01 +0000</pubDate><description>Our database experienced an increased write load which brought several services off line.  We identified the problem and implemented a fix to resolve the immediate outage and prevent this class of incident from happening again in the future.</description></item></channel></rss>