Letterhead Incident History
Letterhead is currently operational with all systems functioning normally.
Incident History
Showing incidents from the last 15 days
Report: "Shared Pool Delivery Delays"
Last updateThis incident has been resolved.
Delays are reducing in number and we are continuing to monitor.
We've identified the underlying issue and we are actively noodling. Thanks for your patience.
We are seeing elevated system reports of delivery delays, which may result in an email arriving in someone's inbox later than expected.
Report: "Reports of Automations Disabling without Notification"
Last updateThis incident has been resolved.
We're investigating reports of Automations disabling without notification. The specific instances have been on July 11th, during which there was a saving-while-scheduling error (reported on this status page). We're looking to see whether there were downstream side effects, as well as other alternatives.
Report: "[Resolved] Sent Newsletters Still Reporting as "Sending""
Last updateThis incident has been resolved.
This has been resolved but we'll continue monitoring for awhile.
We have identified and are addressing a display turnover issue where newsletters that are "Sending" have actually already been sent, but Letterhead hasn't updated the status. This prevents users from seeing their metrics.
Report: "[Resolved] Errors Saving While Scheduling"
Last updateThis incident has been resolved.
We are no longer seeing these elevated errors and thing things look hunky dory. We'll monitor for awhile longer.
This issue remains intermittently rearing its head, we are still actively triaging. Don't hesitate to reach out to us through chat as needed.
We've identified errors while trying to save while scheduling, which is related to a client-side date validation misstep that is interfering with people's writing. A patch is already in progress.
Report: "Elevated Caching and Queuing Error Signals"
Last updateJust a squall. No downstream issues.
We are seeing an elevated number of errors with regard to our caching and queuing infrastructure. Although users and our other monitoring tools suggest that things are copacetic, we just want to be proactive about alerting you to the potential downstream issues.
Report: "Elevated Caching and Queuing Error Signals"
Last updateJust a squall. No downstream issues.
We are seeing an elevated number of errors with regard to our caching and queuing infrastructure. Although users and our other monitoring tools suggest that things are copacetic, we just want to be proactive about alerting you to the potential downstream issues.