LaunchNotes status history
Current state: operational — “All Systems Operational” per https://status.launchnotes.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do LaunchNotes incidents last?
From 3 incidents with a vendor-posted start and resolve time. Longest on record: Services are unresponsive — 5.0 h (2025-09-04 16:51 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.
Incidents on record (3)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-05-04 19:23 UTC | Notifications sent using the LaunchNotes email service provider may not be delivered on time | resolved | major | 3 h 56 min |
| 2025-11-04 16:21 UTC | Announcement content changes not persisting | resolved | minor | 3 h 01 min |
| 2025-09-04 16:51 UTC | Services are unresponsive | resolved | critical | 5 h 01 min |
Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).
Watch LaunchNotes with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"launchnotes"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}
