Is Courier Down?
- Courier's status page
- Operational · no open incidents
- FlareWarden checks
- Website reachable · 8 of 8 regions · 235 ms
Right now
The verdict is the worse of these two. How we decide
Courier's status page
status.courier.com · read · checked every 3 minutes
| Component | Status |
|---|---|
| Web Application | Operational |
| API | Operational |
| Automations | Operational |
| Observability | Operational |
| Courier Inbox | Operational |
FlareWarden checks
courier.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours
- Regions up
- 8 of 8
- Response
- 235 ms
- Checked
By region
- Ashburn reachable, 133 ms
- Chicago reachable, 267 ms
- Johannesburg reachable, 88 ms
- London reachable, 194 ms
- Los Angeles reachable, 302 ms
- San Jose reachable, 163 ms
- Singapore reachable, 430 ms
- Tokyo reachable, 305 ms
Timing by region
| Region | DNS | TCP | TLS | TTFB |
|---|---|---|---|---|
| Ashburn | 71 ms | 2 ms | 10 ms | 114 ms |
| Chicago | 194 ms | 3 ms | 19 ms | 237 ms |
| Johannesburg | 35 ms | 1 ms | 12 ms | 67 ms |
| London | 109 ms | 3 ms | 11 ms | 162 ms |
| Los Angeles | 183 ms | 3 ms | 13 ms | 272 ms |
| San Jose | 104 ms | 3 ms | 10 ms | 140 ms |
| Singapore | 361 ms | 2 ms | 10 ms | 413 ms |
| Tokyo | 250 ms | 1 ms | 8 ms | 290 ms |
History
Incidents Courier reported
Since Oct 31, 6 days · from status.courier.com
- Incidents
- 0
- Major or critical
- 0
- Median to resolve
- —
No incidents reported in this window.
Courier website availability
Measured by FlareWarden · courier.com
- Last 7 days
- 100%
- Last 30 days
- —
- Last 90 days
- —
- Avg response, 30 days
- —
Last 30 days
6-day clean streakMeasured by FlareWarden's own checks of courier.com from multiple regions every 6 hours. Courier's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 6 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.
What Courier does
Courier is a messaging platform that product teams use to send notifications across email, push, SMS, Slack and other channels through one API, with automations, user preferences and an in-app inbox built in. It sits between an application and the email, SMS and chat providers it sends through, so when Courier fails, those notifications do not go out.
What an outage looks like
Messages queue and go out late rather than failing, as twice on October 9, 2026, or send requests stick in a queued state after a bad release (June 18, about two hours). On February 2, 2026 a deployment made backend services unavailable: API calls returned errors, so messages, automations, webhooks and tracking links failed for 2 hours 17 minutes in the US region and 2 hours 42 minutes in Ireland.
What to do about it
Check status.courier.com, linked from courier.com, which lists the web application, API, automations, observability and Courier Inbox. Queued messages go out once the queue clears, so do not resend them. Requests that returned errors were never accepted (Courier said so of the February 2026 outage) and need sending again. A provider can be the cause: in a May 2026 incident Courier pointed users to Slack's own status page.
Is it down for everyone, or just you?
If this page says Courier is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.
Related services
Courier outage FAQ
Is Courier down or is it my email or SMS provider?
Will Courier send queued messages after an outage?
What happened in the February 2026 Courier outage?
How long do Courier incidents last?
How we measure this
- We request Courier's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
- A region counts as down only when it gets no usable HTTP response. A
403or429means the origin answered and refused us, which we report as blocked, never as an outage. - A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
- Response times average only the regions that actually served the page, so a timeout never inflates the number.
- Where Courier publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of Courier itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.
Get alerted when Courier goes down
We check Courier every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.
Start Free Monitoring