Courier Outage History

Courier is up right now

Courier had 29 outages in the last 2 years totaling 63h 12m of downtime — averaging 1.2 incidents per month.

There were 29 Courier outages since July 9, 2024 totaling 63h 12m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.courier.com

Minor June 18, 2026

Send Pipeline Latency

Detected by Pingoru
Jun 18, 2026, 08:11 PM UTC
Resolved
Jun 18, 2026, 10:09 PM UTC
Duration
1h 57m
Affected: API
Timeline · 5 updates
  1. identified Jun 18, 2026, 08:11 PM UTC

    The team has identified a regression causing send requests to be stuck in a queued state. We have initiated a rollback to quickly resolve the issue. More updates to follow

  2. identified Jun 18, 2026, 08:35 PM UTC

    The rollback deploy will land in about 30 minutes.

  3. identified Jun 18, 2026, 09:31 PM UTC

    The team has identified that the most recent deployment was not the cause of the regression. The team is still working on identifying the root cause. Messages will not be dropped, and they will be processed once the fix is out.

  4. monitoring Jun 18, 2026, 09:53 PM UTC

    Messages are being processed while our pipeline continues to process enqueued messages.

  5. resolved Jun 18, 2026, 10:09 PM UTC

    Send pipeline has resolved and enqueued messages are now sending properly.

Read the full incident report →

Minor May 27, 2026

Slack Deliverability Issues

Detected by Pingoru
May 27, 2026, 11:06 PM UTC
Resolved
May 27, 2026, 11:16 PM UTC
Duration
10m
Timeline · 2 updates
  1. monitoring May 27, 2026, 11:06 PM UTC

    Slack has reported messaging, and app degredation on their platform that could be impacting deliverability of Slack messages. This is a downstream provider issue and can be monitored on Slack's statuspage: https://slack-status.com/

  2. resolved May 27, 2026, 11:16 PM UTC

    Please continue to monitor Slack's statuspage for any updates related to message deliverability: https://slack-status.com/

Read the full incident report →

Minor January 29, 2026

Observability Degradation

Detected by Pingoru
Jan 29, 2026, 11:13 PM UTC
Resolved
Jan 29, 2026, 10:00 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Jan 29, 2026, 11:13 PM UTC

    The Courier team identified an issue affecting observability metrics between 21:38 UTC and 22:13 UTC, during which metrics briefly experienced an outage. A fix was released and metrics are stabilized through observability channels. Metrics received during the outage window will not be accounted for in observability dashboards.

Read the full incident report →

Minor January 14, 2026

Courier Web App Performance

Detected by Pingoru
Jan 14, 2026, 09:47 PM UTC
Resolved
Jan 15, 2026, 12:56 AM UTC
Duration
3h 9m
Affected: Web Application
Timeline · 2 updates
  1. identified Jan 14, 2026, 09:47 PM UTC

    The Courier team was alerted of a small degredation in the Courier web application. We have identified the issues and have rolled out a fix to mitigate. The current features will encounter some latency: - Audience Calculation - Audit Trail logging We will follow up with updates.

  2. resolved Jan 15, 2026, 12:56 AM UTC

    Fix is out and application is stable

Read the full incident report →

Critical October 20, 2025

All services impacted

Detected by Pingoru
Oct 20, 2025, 09:19 AM UTC
Resolved
Oct 20, 2025, 10:11 AM UTC
Duration
51m
Affected: Web ApplicationAPIAutomationsObservabilityCourier Inbox
Timeline · 4 updates
  1. identified Oct 20, 2025, 09:54 AM UTC

    An issue with our service provider, AWS, has impacted all Courier services. The engineering team is working on resolution.

  2. identified Oct 20, 2025, 09:55 AM UTC

    We are continuing to work on a fix for this issue.

  3. monitoring Oct 20, 2025, 10:02 AM UTC

    Service has been restored. Engineering is working through system review and will continue to monitor.

  4. resolved Oct 20, 2025, 10:11 AM UTC

    The incident has been resolved

Read the full incident report →

Minor October 17, 2025

Microsoft Teams Tenant Id Errors

Detected by Pingoru
Oct 17, 2025, 05:33 AM UTC
Resolved
Oct 17, 2025, 06:01 AM UTC
Duration
28m
Affected: API
Timeline · 2 updates
  1. monitoring Oct 17, 2025, 05:33 AM UTC

    The Courier team was alerted of an issue with MS Teams requests experiencing errors sending. We have identified the issue and published a fix that will land in production shortly

  2. resolved Oct 17, 2025, 06:01 AM UTC

    Release is in production and Microsoft Teams messages are passing successfully.

Read the full incident report →

Notice October 13, 2025

Mailgun Message Delivery Latency

Detected by Pingoru
Oct 13, 2025, 04:19 PM UTC
Resolved
Oct 13, 2025, 04:19 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Oct 13, 2025, 04:19 PM UTC

    Courier experienced a slowdown in message delivery with Mailgun providers around 2AM PST. Our monitoring systems caught the spike in the bottleneck, which eventually stabilized. Our infrastructure team is actively monitoring.

Read the full incident report →

Notice October 8, 2025

Message Delivery Latency

Detected by Pingoru
Oct 08, 2025, 03:16 PM UTC
Resolved
Oct 08, 2025, 09:00 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Oct 08, 2025, 03:16 PM UTC

    Courier's delivery platform experienced significant latency around 1am PST. Our platform team managed to resolve the issue and is actively monitoring for any potential issues.

Read the full incident report →

Minor July 7, 2025

Webapp HTTP Interaction Issues

Detected by Pingoru
Jul 07, 2025, 09:10 PM UTC
Resolved
Jul 07, 2025, 09:28 PM UTC
Duration
18m
Affected: Web Application
Timeline · 2 updates
  1. identified Jul 07, 2025, 09:10 PM UTC

    An issue with logging in to the Courier platform and overall app performance was identified by our team and a revert of the offending release has been deployed. The estimated time for the release to land is 45 minutes.

  2. resolved Jul 07, 2025, 09:28 PM UTC

    Revert has landed and webapp is operational.

Read the full incident report →

Minor June 12, 2025

Cloudflare Outage Possible Okta SSO Impact

Detected by Pingoru
Jun 12, 2025, 07:30 PM UTC
Resolved
Jun 12, 2025, 08:36 PM UTC
Duration
1h 5m
Affected: Web Application
Timeline · 2 updates
  1. monitoring Jun 12, 2025, 07:30 PM UTC

    Cloudflare has reported an outage that will impact SSO features provided by WorkOS. Customers with Okta SSO might experience some degradation when signing in. Our team is monitoring the status for both Cloudflare and WorkOS. WorkOS status: https://status.workos.com/incidents/k9s870cktcsf Cloudflare Status: https://www.cloudflarestatus.com/incidents/25r9t0vz99rp

  2. resolved Jun 12, 2025, 08:36 PM UTC

    WorkOS systems are back to normal.

Read the full incident report →

Minor June 5, 2025

Message Delays on Send Pipeline

Detected by Pingoru
Jun 05, 2025, 06:51 PM UTC
Resolved
Jun 05, 2025, 08:08 PM UTC
Duration
1h 17m
Affected: API
Timeline · 5 updates
  1. investigating Jun 05, 2025, 06:51 PM UTC

    The Courier team has identified an issue where there are significant delays of up to 10 minutes for messages. We are currently investigating and looking for a root cause to mitigate. Updates will follow.

  2. identified Jun 05, 2025, 07:04 PM UTC

    Backed-up messages were caused by a bottleneck in our system, which has started to catch up. Messages will stabilize as the bottleneck clears.

  3. monitoring Jun 05, 2025, 07:14 PM UTC

    Message bottleneck has cleared and the queue has stabilized. We will continue to monitor.

  4. monitoring Jun 05, 2025, 07:19 PM UTC

    Messages have stabilized but we will continue to monitor.

  5. resolved Jun 05, 2025, 08:08 PM UTC

    Messages have recovered and pipeline is stable again.

Read the full incident report →

Notice May 16, 2025

EU Region – Notifications Stuck in “Queued” State

Detected by Pingoru
May 16, 2025, 02:28 PM UTC
Resolved
May 16, 2025, 09:02 PM UTC
Duration
6h 34m
Timeline · 3 updates
  1. investigating May 16, 2025, 02:28 PM UTC

    We are currently investigating an issue where EU workspace notifications appear to remain in the “queued” state.

  2. identified May 16, 2025, 02:53 PM UTC

    The issue has been identified and a fix is being implemented.

  3. resolved May 16, 2025, 09:02 PM UTC

    The issue has been resolved. The root cause was purely a logging issue, notifications were still sent but showing up in logs as queued. All logs have been rehydrated

Read the full incident report →

Minor April 30, 2025

AWS SES Failures

Detected by Pingoru
Apr 30, 2025, 10:39 PM UTC
Resolved
May 01, 2025, 04:58 AM UTC
Duration
6h 19m
Affected: API
Timeline · 5 updates
  1. identified Apr 30, 2025, 10:39 PM UTC

    The Courier team has identified an issue with a recent deployment that is impacting AWS SES integrations. We have found the root cause and have reverted the changes. The team is gathering impact.

  2. identified Apr 30, 2025, 10:47 PM UTC

    The reverted changes will land in production in around one hour. The team will investigate the impact and handle message retries accordingly.

  3. monitoring Apr 30, 2025, 11:26 PM UTC

    Fix has landed and the team is monitoring progress. Messages sent to AWS SES are sending normally. The team will reprocess impacted messages.

  4. monitoring May 01, 2025, 01:06 AM UTC

    The team is still working through the reprocessing for impacted messages. Confirmation of all impacted messages reprocessed will be updated here.

  5. resolved May 01, 2025, 04:58 AM UTC

    All impacted messages have been reprocessed.

Read the full incident report →

Minor February 28, 2025

Internal Courier Error Issue

Detected by Pingoru
Feb 28, 2025, 04:48 PM UTC
Resolved
Mar 01, 2025, 04:11 AM UTC
Duration
11h 22m
Affected: API
Timeline · 7 updates
  1. identified Feb 28, 2025, 04:48 PM UTC

    The Courier team has identified an issue where messages fail due to an "Internal Courier Error" in the test environment. Our team found the root cause and are working to mitigate the issue.

  2. identified Feb 28, 2025, 05:14 PM UTC

    We have tested the fix for "Internal Courier Error" and will be releasing it to production soon.

  3. identified Feb 28, 2025, 05:36 PM UTC

    A fix has been merged and will fully deploy within the next hour. Updates to follow.

  4. monitoring Feb 28, 2025, 06:40 PM UTC

    The fix has landed in production and we will be monitoring for any more "Internal Courier Errors". We will be working on reprocessing any dropped messages caused by this issue.

  5. monitoring Feb 28, 2025, 06:57 PM UTC

    Messages with tags are no longer impacted, and error has been resolved. The team is working on reprocessing dropped messages.

  6. monitoring Feb 28, 2025, 07:52 PM UTC

    The team is still working on reprocessing dropped messages caused by this issue. Send pipeline is operational.

  7. resolved Mar 01, 2025, 04:11 AM UTC

    All impacted messages have been reprocessed.

Read the full incident report →

Minor February 21, 2025

Segment Event Processing Slowdowns

Detected by Pingoru
Feb 21, 2025, 03:55 PM UTC
Resolved
Feb 21, 2025, 05:10 PM UTC
Duration
1h 15m
Affected: Automations
Timeline · 2 updates
  1. monitoring Feb 21, 2025, 03:55 PM UTC

    The Courier team has identified a slowdown in Segment event processing. There will be a slight delay for messages triggered by incoming Segment triggers. We estimate the queue to normalize soon and are monitoring.

  2. resolved Feb 21, 2025, 05:10 PM UTC

    Segment event processing stream has resolved.

Read the full incident report →

Minor February 18, 2025

Significant Notification Event Latency

Detected by Pingoru
Feb 18, 2025, 02:22 PM UTC
Resolved
Feb 18, 2025, 02:47 PM UTC
Duration
24m
Affected: API
Timeline · 3 updates
  1. identified Feb 18, 2025, 02:22 PM UTC

    The Courier team identified a delay in message processing and event updating. The pipeline queue for message delivery has normalized, however significant slowdowns in message events are still processing.

  2. monitoring Feb 18, 2025, 02:29 PM UTC

    We're monitoring our processing pipeline as messages are flowing normally. There is a slight delay in event processing which will also impact outbound webhooks.

  3. resolved Feb 18, 2025, 02:47 PM UTC

    Message sends are flowing normally, and events are caught up without delays.

Read the full incident report →

Minor February 13, 2025

Courier Send and Message Event Slowdown

Detected by Pingoru
Feb 13, 2025, 10:32 PM UTC
Resolved
Feb 13, 2025, 11:09 PM UTC
Duration
36m
Affected: API
Timeline · 3 updates
  1. identified Feb 13, 2025, 10:32 PM UTC

    The Courier team has identified a slowdown in sending notifications. This issue has been identified by our team and is closely monitoring. We do not expect any messages to drop. We will continue to monitor and update accordingly.

  2. monitoring Feb 13, 2025, 10:51 PM UTC

    Our team has identified a bottleneck in our system caused by timeouts on our sendworker. Our exponential backoff has caught up and messages are starting to go through.

  3. resolved Feb 13, 2025, 11:09 PM UTC

    The team has identified the issue related to network connections on AWS which resulted in a backup of messages on our pipeline. Messages are flowing through as expected, and the stream has caught up.

Read the full incident report →

Minor February 11, 2025

Delay in Message Sends and Processing

Detected by Pingoru
Feb 11, 2025, 10:15 PM UTC
Resolved
Feb 11, 2025, 11:08 PM UTC
Duration
53m
Affected: API
Timeline · 3 updates
  1. identified Feb 11, 2025, 10:15 PM UTC

    The Courier team has identified a slowdown in our pipeline. The queue has backed up but no messages have been dropped at the moment. We will continue to update as we monitor our pipeline.

  2. monitoring Feb 11, 2025, 10:34 PM UTC

    The team has identified the cause of message sends and slowdowns to be related to an AWS service. Messages that were stuck in a queued state are slowly passing through. The team will continue to monitor and update.

  3. resolved Feb 11, 2025, 11:08 PM UTC

    The send stream has caught up, all messages have been sent and the issue appears to be fully resolved.

Read the full incident report →

Minor January 11, 2025

Automation Delay Processing Issues

Detected by Pingoru
Jan 11, 2025, 01:23 AM UTC
Resolved
Jan 11, 2025, 04:25 AM UTC
Duration
3h 2m
Affected: Automations
Timeline · 3 updates
  1. identified Jan 11, 2025, 01:23 AM UTC

    We are currently experiencing an issue affecting automation workflows that include delay steps. Some customers may encounter failures when attempting to execute automations with scheduled delays. Our engineering team has identified the root cause and is implementing a fix. We expect the service to be fully restored in a short while.

  2. monitoring Jan 11, 2025, 02:19 AM UTC

    We have deployed a fix for the earlier issue affecting automation workflows with delay steps. New automation workflows are now executing successfully. However, automations that failed during the incident period (approximately 3:20 PM PT - 6:05 PM PT) have not yet been automatically retried. Our engineering team is monitoring the recovery and evaluating a plan to process these backlogged automations.

  3. resolved Jan 11, 2025, 04:25 AM UTC

    The service issue affecting automation workflows with delay steps has been partially resolved. New automation workflows started after 6:05 PM PT are executing successfully. However, we have determined that automations that failed during the incident period (approximately 3:20 PM PT - 6:05 PM PT) cannot be automatically retried at this time due to technical limitations. If your business was impacted by failed automation runs during this incident, please contact our support team and we will work directly with you to address your concerns. We sincerely apologize for this disruption to your workflows.

Read the full incident report →

Major October 24, 2024

Delayed Message Processing

Detected by Pingoru
Oct 24, 2024, 10:38 PM UTC
Resolved
Oct 25, 2024, 02:48 AM UTC
Duration
4h 10m
Affected: API
Timeline · 8 updates
  1. investigating Oct 24, 2024, 10:38 PM UTC

    Courier has identified a delay in message processing for the messages API. We are currently investigating the root cause and will update you periodically.

  2. investigating Oct 24, 2024, 11:01 PM UTC

    We are continuing to monitor the root cause of the delayed message processing.

  3. investigating Oct 24, 2024, 11:29 PM UTC

    The team is still investigating and discussing the root cause internally. Messages are experiencing longer than normal processing times.

  4. identified Oct 25, 2024, 12:00 AM UTC

    The team has identified the issue and is rolling out a fix for the message delays.

  5. identified Oct 25, 2024, 12:40 AM UTC

    Fix has been deployed and will be live in around 1hr.

  6. identified Oct 25, 2024, 01:31 AM UTC

    The team identified an issue with the latest fix and reverted it. A new fix has been published to mitigate the message delay issue. ETA to land in production ~45 minutes.

  7. monitoring Oct 25, 2024, 02:43 AM UTC

    A fix has been implemented and delivery times are beginning to returning to expected levels. The team will continue to monitor.

  8. resolved Oct 25, 2024, 02:48 AM UTC

    This incident has been resolved

Read the full incident report →

Minor October 21, 2024

Message Logs Delays

Detected by Pingoru
Oct 21, 2024, 03:56 PM UTC
Resolved
Oct 21, 2024, 06:51 PM UTC
Duration
2h 55m
Affected: Observability
Timeline · 6 updates
  1. investigating Oct 21, 2024, 03:56 PM UTC

    The Courier team is investigating an issue with the event logger for message event logs hitting a bottleneck. The team is actively investigating. Messages are still sending.

  2. investigating Oct 21, 2024, 03:56 PM UTC

    We are continuing to investigate this issue.

  3. identified Oct 21, 2024, 04:07 PM UTC

    The team is testing out a fix to reduce the bottlenecked log lines before releasing to production.

  4. identified Oct 21, 2024, 05:19 PM UTC

    The team encountered an issue with testing the fix and reverted the update. We are publishing a new update that should resolve the backlogged message logs.

  5. monitoring Oct 21, 2024, 06:30 PM UTC

    The fix has landed in production and the team is monitoring the message log queue. Message event logs should be flowing normally.

  6. resolved Oct 21, 2024, 06:51 PM UTC

    The data stream is unblocked, and the message logs queue is resolved and flowing normally.

Read the full incident report →

Major October 10, 2024

Courier Inbox FetchMessages Connectivity Issues

Detected by Pingoru
Oct 10, 2024, 04:46 PM UTC
Resolved
Oct 11, 2024, 02:33 AM UTC
Duration
9h 46m
Affected: Courier Inbox
Timeline · 8 updates
  1. investigating Oct 10, 2024, 03:38 PM UTC

    The Courier Team is investigating an issue related to Inbox fetching messages in the component.

  2. identified Oct 10, 2024, 04:30 PM UTC

    The team has identified the issue and will be rolling out a fix. The team will reprocess the impacted messages that were not fetched.

  3. monitoring Oct 10, 2024, 04:46 PM UTC

    Inbox connectivity for fetching messages has been reestablished. The team is monitoring closely, and working on retroactively processing impacted messages to Inbox

  4. monitoring Oct 10, 2024, 05:50 PM UTC

    We are continuing to gather a list of impacted messages to backfill impacted Inbox components.

  5. monitoring Oct 10, 2024, 06:06 PM UTC

    We are continuing to monitor for any further issues.

  6. monitoring Oct 10, 2024, 07:07 PM UTC

    The team has gathered impacted messages and is running tests before a release.

  7. monitoring Oct 10, 2024, 08:51 PM UTC

    The team has initiated backlogging the impacted Inbox messages.

  8. resolved Oct 11, 2024, 02:33 AM UTC

    Inbox connectivity issues resolved.

Read the full incident report →

Minor September 6, 2024

Send Pipeline and Event Status Slowdowns

Detected by Pingoru
Sep 06, 2024, 04:35 PM UTC
Resolved
Sep 06, 2024, 04:59 PM UTC
Duration
23m
Affected: APIObservability
Timeline · 5 updates
  1. identified Sep 06, 2024, 04:35 PM UTC

    The Courier team has identified an issue with the send pipeline and event status updates causing queued messages and delayed webhook events. The Courier team will monitor the bottleneck and adjust message batching necessary to flow messages normally.

  2. identified Sep 06, 2024, 04:39 PM UTC

    The team has increased our processing to help with the bottleneck.

  3. monitoring Sep 06, 2024, 04:44 PM UTC

    The team has increased the send pipeline worker and messages are clearing the bottleneck.

  4. monitoring Sep 06, 2024, 04:52 PM UTC

    Corrective actions have cleared the bottleneck and messages and events should be flowing normally.

  5. resolved Sep 06, 2024, 04:59 PM UTC

    Bottleneck has cleared for messages and event statuses.

Read the full incident report →

Major August 19, 2024

Delay in Message Processing

Detected by Pingoru
Aug 19, 2024, 06:32 PM UTC
Resolved
Aug 19, 2024, 09:35 PM UTC
Duration
3h 3m
Affected: Web ApplicationAPIObservability
Timeline · 6 updates
  1. identified Aug 19, 2024, 06:32 PM UTC

    The Courier team identified an issue in our health monitoring involving our message event processing. The issue has been identified and a revert is in place.

  2. monitoring Aug 19, 2024, 06:48 PM UTC

    Our team has released a revert to address the regression and it's in the process of merging.

  3. monitoring Aug 19, 2024, 06:50 PM UTC

    The release is live, and the team is monitoring it.

  4. monitoring Aug 19, 2024, 06:56 PM UTC

    Release is published and building to production. ETA ~45 minutes.

  5. monitoring Aug 19, 2024, 08:02 PM UTC

    Fix has been deployed, and enqueued messages have started to go through slowly. Once the bottleneck clears, messages should start to flow normally.

  6. resolved Aug 19, 2024, 09:35 PM UTC

    The general pipeline has recovered.

Read the full incident report →