Company Logo

Is there an Courier outage?

Courier status: Systems Active

Last checked: 8 minutes ago

Get notified about any outages, downtime or incidents for Courier and 1800+ other cloud vendors. Monitor 10 companies, for free.

Subscribe for updates

Courier outages and incidents

Outage and incident data over the last 30 days for Courier.

There have been 0 outages or incidents for Courier in the last 30 days.

Severity Breakdown:

Tired of searching for status updates?

Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!

Sign Up Now

Components and Services Monitored for Courier

Outlogger tracks the status of these components for Xero:

API Active
Automations Active
Courier Inbox Active
Observability Active
Web Application Active
AWS dynamodb-us-east-1 Active
AWS elasticsearch-us-east-1 Active
AWS kinesis-us-east-1 Active
AWS lambda-us-east-1 Active
AWS sqs-us-east-1 Active
Segment Destinations Active
Mailgun API Active
Mailgun Outbound Delivery Active
Mailjet REST API Active
Mailjet SEND API Active
Nexmo Outbound SMS Active
Plivo SMS API Active
Segment Cloud Sources Active
Segment Data Ingestion (Tracking) API Active
SendGrid API Active
SendGrid SMTP Active
Slack Apps/Integrations/APIs Active
SparkPost SMTP API - EUROPE Active
SparkPost SMTP API - USA Active
SparkPost SMTP Delivery - EUROPE Active
SparkPost SMTP Delivery - USA Maintenance
Twilio AUTOPILOT Active
Twilio SMS Active
Component Status
Active
API Active
Automations Active
Courier Inbox Active
Observability Active
Web Application Active
Active
AWS dynamodb-us-east-1 Active
AWS elasticsearch-us-east-1 Active
AWS kinesis-us-east-1 Active
AWS lambda-us-east-1 Active
AWS sqs-us-east-1 Active
Active
Segment Destinations Active
Maintenance
Mailgun API Active
Mailgun Outbound Delivery Active
Mailjet REST API Active
Mailjet SEND API Active
Nexmo Outbound SMS Active
Plivo SMS API Active
Segment Cloud Sources Active
Segment Data Ingestion (Tracking) API Active
SendGrid API Active
SendGrid SMTP Active
Slack Apps/Integrations/APIs Active
SparkPost SMTP API - EUROPE Active
SparkPost SMTP API - USA Active
SparkPost SMTP Delivery - EUROPE Active
SparkPost SMTP Delivery - USA Maintenance
Twilio AUTOPILOT Active
Twilio SMS Active

Latest Courier outages and incidents.

View the latest incidents for Courier and check for official updates:

Updates:

  • Time: July 26, 2022, 5:16 a.m.
    Status: Resolved
    Update: We have finished measuring the impact and will be reaching out to affected customers.
  • Time: July 25, 2022, 11:42 p.m.
    Status: Monitoring
    Update: We have confirmed our deployed fix has resolved the issue for new incoming events. We are continue to work on resolution for historical segment events that did not trigger message sends.
  • Time: July 25, 2022, 11:38 p.m.
    Status: Monitoring
    Update: We have released a fix for new incoming Segment events. We are monitoring to confirm send volume for Segment to Send returns to normal.
  • Time: July 25, 2022, 11:26 p.m.
    Status: Identified
    Update: We are continuing to work on a fix for this issue.
  • Time: July 25, 2022, 11:24 p.m.
    Status: Identified
    Update: We have identified the issue and are preparing a release that will resolve it for new incoming Segment events. We are working to identify historical segment events that should have triggered sends that were impacted.
  • Time: July 25, 2022, 11:05 p.m.
    Status: Investigating
    Update: We are currently investigating an issue where Send messages triggered by the Segment Event track/ integration are not being sent. Customers using the Segment Event track/ integration with Automations appear not to be impacted.

Updates:

  • Time: July 19, 2022, 4:53 p.m.
    Status: Postmortem
    Update: ### Impact Courier experienced delayed message delivery in its send pipeline impacting 0.1% of messages from 12:50pm to 21:50pm PT on 7/14. No messages were dropped as a result of the incident. 99.9% of send calls experienced no delivery delay. The average message send delay was 3 hours and 20 minutes for impacted messages. #### Root Cause Courier uses feature flags to safely roll out new features. Due to a misconfiguration of a flag, a larger than expected volume of send requests were included in a validation experiment meant to verify a refactor of the send pipeline was safe to rollout. These requests added significant additional load on key stages of the send pipeline, and caused non-validation related requests to queue. #### Remediation Courier incrementally scaled up processing capacity in the send pipeline to work through the large accumulated backlog of messages. Additionally, a hotfix release was pushed to production in order to drop validation messages that had already entered the send pipeline. #### Follow up actions * Courier has established a process to better validate flag configuration in the future, as well as made changes to its feature flag helper library to make use less error-prone. * Courier has created an incident playbook to guide on-call engineers through options to quickly scale up message processing in the send pipeline.
  • Time: July 15, 2022, 5:06 a.m.
    Status: Resolved
    Update: The incident has been resolved.
  • Time: July 15, 2022, 4:49 a.m.
    Status: Monitoring
    Update: A fix has been implemented and we are monitoring system health. All backlogged messages are being processed.
  • Time: July 15, 2022, 1:26 a.m.
    Status: Identified
    Update: We are continuing to work towards resolution of the issue. We currently are seeing delays of approximately 2 hours for some message delivery
  • Time: July 14, 2022, 10:50 p.m.
    Status: Identified
    Update: The issue has been identified and a resolution is being deployed to our production services.
  • Time: July 14, 2022, 9:34 p.m.
    Status: Investigating
    Update: We are currently investigating an issue that is affecting send times for some messages.

Updates:

  • Time: July 19, 2022, 4:53 p.m.
    Status: Postmortem
    Update: ### Impact Courier experienced delayed message delivery in its send pipeline impacting 0.1% of messages from 12:50pm to 21:50pm PT on 7/14. No messages were dropped as a result of the incident. 99.9% of send calls experienced no delivery delay. The average message send delay was 3 hours and 20 minutes for impacted messages. #### Root Cause Courier uses feature flags to safely roll out new features. Due to a misconfiguration of a flag, a larger than expected volume of send requests were included in a validation experiment meant to verify a refactor of the send pipeline was safe to rollout. These requests added significant additional load on key stages of the send pipeline, and caused non-validation related requests to queue. #### Remediation Courier incrementally scaled up processing capacity in the send pipeline to work through the large accumulated backlog of messages. Additionally, a hotfix release was pushed to production in order to drop validation messages that had already entered the send pipeline. #### Follow up actions * Courier has established a process to better validate flag configuration in the future, as well as made changes to its feature flag helper library to make use less error-prone. * Courier has created an incident playbook to guide on-call engineers through options to quickly scale up message processing in the send pipeline.
  • Time: July 15, 2022, 5:06 a.m.
    Status: Resolved
    Update: The incident has been resolved.
  • Time: July 15, 2022, 4:49 a.m.
    Status: Monitoring
    Update: A fix has been implemented and we are monitoring system health. All backlogged messages are being processed.
  • Time: July 15, 2022, 1:26 a.m.
    Status: Identified
    Update: We are continuing to work towards resolution of the issue. We currently are seeing delays of approximately 2 hours for some message delivery
  • Time: July 14, 2022, 10:50 p.m.
    Status: Identified
    Update: The issue has been identified and a resolution is being deployed to our production services.
  • Time: July 14, 2022, 9:34 p.m.
    Status: Investigating
    Update: We are currently investigating an issue that is affecting send times for some messages.

Updates:

  • Time: June 22, 2022, 1:58 a.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: June 21, 2022, 11:40 p.m.
    Status: Monitoring
    Update: A fix has been deployed and we are monitoring system health
  • Time: June 21, 2022, 11:40 p.m.
    Status: Monitoring
    Update: A fix has been deployed and we are monitoring system health
  • Time: June 21, 2022, 11:05 p.m.
    Status: Identified
    Update: We have identified the issue and are working on a resolution
  • Time: June 21, 2022, 11:05 p.m.
    Status: Identified
    Update: We have identified the issue and are working on a resolution
  • Time: June 21, 2022, 10:41 p.m.
    Status: Investigating
    Update: We are currently investigating delays in message processing due to provider timeouts.
  • Time: June 21, 2022, 10:41 p.m.
    Status: Investigating
    Update: We are currently investigating delays in message processing due to provider timeouts.

Updates:

  • Time: June 10, 2022, 5:08 a.m.
    Status: Resolved
    Update: AWS issue has been resolved with services operating normally. Courier systems are operational and healthy.
  • Time: June 10, 2022, 4:18 a.m.
    Status: Monitoring
    Update: AWS is seeing a reduction in error rates and latencies. We are continuing to monitor the issue and health of the system.
  • Time: June 10, 2022, 3:59 a.m.
    Status: Monitoring
    Update: We're monitoring the AWS ongoing issue.
  • Time: June 10, 2022, 3:58 a.m.
    Status: Investigating
    Update: AWS is experiencing elevated error rates and latencies for services that affect Courier. As a result, users may see increased errors and delays within Courier APIs. So far the impact remains low and our reprocessing infrastructure is operational. We'll be monitoring this incident closely and continue to post updates.

Check the status of similar companies and alternatives to Courier

Hudl
Hudl

Systems Active

OutSystems
OutSystems

Systems Active

Postman
Postman

Systems Active

Mendix
Mendix

Systems Active

DigitalOcean
DigitalOcean

Issues Detected

Bandwidth
Bandwidth

Issues Detected

DataRobot
DataRobot

Systems Active

Grafana Cloud
Grafana Cloud

Systems Active

SmartBear Software
SmartBear Software

Systems Active

Test IO
Test IO

Systems Active

Copado Solutions
Copado Solutions

Systems Active

CircleCI
CircleCI

Systems Active

Frequently Asked Questions - Courier

Is there a Courier outage?
The current status of Courier is: Systems Active
Where can I find the official status page of Courier?
The official status page for Courier is here
How can I get notified if Courier is down or experiencing an outage?
To get notified of any status changes to Courier, simply sign up to OutLogger's free monitoring service. OutLogger checks the official status of Courier every few minutes and will notify you of any changes. You can veiw the status of all your cloud vendors in one dashboard. Sign up here
What does Courier do?
Courier is an API that allows developers to design notifications once and deliver them through various channels, including email, Slack, SMS, and push notifications.

Start monitoring now!

Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.

Get Started for Free