Courier status history
Current state: operational — “All Systems Operational” per https://status.courier.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Courier incidents last?
From 9 incidents with a vendor-posted start and resolve time. Longest on record: Courier Web App Performance — 3.1 h (2026-01-14 21:47 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 (9)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-06-18 20:11 UTC | Send Pipeline Latency | resolved | minor | 1 h 57 min |
| 2026-05-27 23:06 UTC | Slack Deliverability Issues | resolved | minor | 10 min |
| 2026-02-02 20:07 UTC | Courier Multi Service Outage | postmortem | critical | 3 h 06 min |
| 2026-01-29 10:00 UTC | Observability Degradation | resolved | minor | 0 min |
| 2026-01-14 21:47 UTC | Courier Web App Performance | resolved | minor | 3 h 09 min |
| 2025-10-20 09:19 UTC | All services impacted | resolved | critical | 51 min |
| 2025-10-17 05:33 UTC | Microsoft Teams Tenant Id Errors | resolved | minor | 28 min |
| 2025-10-13 16:19 UTC | Mailgun Message Delivery Latency | resolved | none | 0 min |
| 2025-10-08 09:00 UTC | Message Delivery Latency | resolved | none | 0 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 Courier with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"courier"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}
