All Systems Operational

About This Site

Welcome to Mailbutler's status page. Here you can always check for the key vitals of our system, from the main servers, through payment subsystems to auxiliary services.

Uptime over the past 90 days. View historical uptime.
Ecosystem Operational
Backend Operational
Worker Queue Operational
Database Operational
Cloud Infrastructure Operational
Database Operational
Auxiliary APIs Operational
Application Servers Operational
File Storage Operational
Payments & Subscriptions Operational
Payment Processing Operational
Synchronization of Subscriptions Operational
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.

Oct 16, 2026

No incidents reported today.

Oct 15, 2026

No incidents reported.

Oct 14, 2026

No incidents reported.

Oct 13, 2026

Scheduled database maintenance
Completed - The scheduled maintenance has been completed.
Oct 13, 11:00 CEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 13, 10:00 CEST
Scheduled - We’re upgrading our database servers to add capacity and improve response times. During this window Mailbutler features that sync with our servers (tracking, scheduled sending, notes, tasks and the sidebar) may be unavailable for up to 15 minutes. Emails scheduled for sending during the window will go out shortly after it ends. No action is needed on your side.
Oct 12, 14:03 CEST

Oct 12, 2026

No incidents reported.

Oct 11, 2026

No incidents reported.

Oct 10, 2026

No incidents reported.

Oct 9, 2026

No incidents reported.

Oct 8, 2026

No incidents reported.

Oct 7, 2026

Service disruption due to a database storage issue
Resolved - On October 7, between 20:55 and 21:40 CEST, our primary database ran out of storage space. During this time, many requests to Mailbutler failed, particularly saving data, and features such as signatures, tracking, notes, and tasks were unavailable or returned errors in all clients. We increased storage capacity, and the service was fully restored at 21:40 CEST. Scheduled emails and other background jobs that queued up during the disruption were processed by 22:05 CEST, so some of them went out with a delay.

The cause was an internal data processing component that stopped working the day before and kept database storage reserved without releasing it. Our monitoring should have alerted us much earlier but didn't, due to a configuration error in our notification setup. We have fixed the alerting, capped how much storage this component can use, and added dedicated monitoring for it. No customer data was lost. We apologize for the disruption.
Oct 7, 21:00 CEST

Oct 6, 2026

No incidents reported.

Oct 5, 2026

No incidents reported.

Oct 4, 2026

No incidents reported.

Oct 3, 2026

No incidents reported.

Oct 2, 2026

No incidents reported.

Incident History Powered by Atlassian Statuspage