All Systems Operational

Uptime over the past 90 days. View historical uptime.
API Operational
90 days ago
100.0 % uptime
Today
Curations API Operational
90 days ago
100.0 % uptime
Today
Marketing API Operational
90 days ago
100.0 % uptime
Today
Applications Operational
90 days ago
99.98 % uptime
Today
Archives Operational
90 days ago
100.0 % uptime
Today
Audience Operational
90 days ago
100.0 % uptime
Today
Composer Operational
90 days ago
100.0 % uptime
Today
Dashboards Operational
90 days ago
100.0 % uptime
Today
Newsletters Operational
90 days ago
99.89 % uptime
Today
Promotions Operational
90 days ago
100.0 % uptime
Today
Delivery Operational
90 days ago
100.0 % uptime
Today
Outbound Email Deliverability (Shared Pools) Operational
90 days ago
100.0 % uptime
Today
Services Operational
90 days ago
99.96 % uptime
Today
Authorization Operational
90 days ago
100.0 % uptime
Today
Automation Operational
90 days ago
99.89 % uptime
Today
Curation Operational
90 days ago
99.97 % uptime
Today
Documentation Operational
90 days ago
100.0 % uptime
Today
Email Service Provider Operational
90 days ago
99.89 % uptime
Today
Metrics Operational
90 days ago
100.0 % uptime
Today
Notifications Operational
90 days ago
100.0 % uptime
Today
Webhooks Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Jan 12, 2026

No incidents reported today.

Jan 11, 2026

No incidents reported.

Jan 10, 2026

No incidents reported.

Jan 9, 2026
[Resolved] Elevated Delays
Postmortem - Read details
Jan 10, 00:09 EST
Resolved - This incident has been resolved.
Jan 9, 23:51 EST
Update - All of the affected newsletters on dedicated pools have been successfully delivered.
Jan 9, 23:40 EST
Update - All of the affected newsletters on our shared pools have been delivered successfully.
Jan 9, 23:03 EST
Update - We are confirming our outbound email deliverability - that an email sent from Letterhead is reaching its inbox - is in good shape. We had marked it "degraded performance" at the beginning of this incident, before we had identified the underlying problem, but want to confirm it is not nor was at issue.

Fundamentally, the problem was with our error monitoring. Generally, failure here and there is common, and Letterhead recovers from those failures automatically. In the event it doesn't, someone is always around to intervene. This evening there was a monitoring failure that resulted in a small bug related to email-reputational silos we call "subaccounts," but because our system (dubbed the "dead letter office") wasn't aware, this issue cascaded until an unrelated memory-usage threshold monitor rung alarm bells. This coincided with reports to our customer support team.

Consequently, a small-potatoes error resulted in a pretty severe throttle of our newsletter transmissions pipeline. When a transmission fails for any reason, it will retry after a delay. This built-in delay is designed to help avoid a traffic jam. This is what happened - a lot.

We are presently still evening out.

To reiterate: a newsletter sent now shouldn't be delayed. The newsletters affected appear to have been sent between 3:00 p.m. EST until about 8:30 p.m. EST.

We very much apologize for the inconvenience. Our team is monitoring through the night.
Jan 9, 22:21 EST
Update - We are continuing to see improved performance. We are confident your emails will reach their audience, even though some may be delayed. Newsletters sent any time in the last couple of hours do not seem to be delayed, which is good. We apologize for the hassle and we will resolve this status only when everything has returned to normal with a full post-mortem.
Jan 9, 21:48 EST
Monitoring - Newsletters are sending at volume and our queues are slowly returning to normalcy. Delays are still elevated. We have confirmed that the underlying issue is resolved, but the sheer volume of our system will take time to even out.
Jan 9, 20:40 EST
Identified - We appreciate your patience and we believe we traced the issue that was creating a queuing bottleneck. We are seeing queues return to normal, but delays are still elevated and it will take time to normalize.
Jan 9, 19:54 EST
Update - We appreciate your patience.
Jan 9, 19:22 EST
Investigating - We are seeing an elevated number of sending delays. Our team is currently investigating the situation.
Jan 9, 19:04 EST
[Resolved] Legacy RSS Composer Block Issues
Resolved - This incident has been resolved.
Jan 9, 10:29 EST
Monitoring - The underlying issues are addressed, and we're now ensuring impacted users are all set and ready to go.
Jan 9, 09:56 EST
Identified - We have identified and are addressing issues reported about the use of our Legacy RSS Block, which is resulting in empty content sections. Note: this doesn't affect anyone using Curations or the current RSS Block - just the block marked "Legacy."
Jan 9, 08:16 EST
Jan 8, 2026

No incidents reported.

Jan 7, 2026

No incidents reported.

Jan 6, 2026

No incidents reported.

Jan 5, 2026

No incidents reported.

Jan 4, 2026

No incidents reported.

Jan 3, 2026

No incidents reported.

Jan 2, 2026
[Resolved] Elevated errors creating organization promotions
Resolved - This incident has been resolved.
Jan 2, 15:21 EST
Update - That looks like it did the trick. Upgrading the status of organization promotions to "operational." We'll continue monitoring.
Jan 2, 14:48 EST
Monitoring - Our patch is in effect and we are now monitoring for further errors.
Jan 2, 14:46 EST
Identified - We've identified the underlying problem and we're now applying a patch.
Jan 2, 14:19 EST
Investigating - We are observing in our logs elevated errors when some users are creating organization-level promotions, and we are currently investigating the issue. Apologies for any hassle.
Jan 2, 14:11 EST
Jan 1, 2026

No incidents reported.

Dec 31, 2025

No incidents reported.

Dec 30, 2025

No incidents reported.

Dec 29, 2025

No incidents reported.

← Incident History Powered by Atlassian Statuspage