21,228 outages in February - Here are the biggest:
There were 46 Zapier outages since January 2025 which are summarized below, including incident details, duration, and resolution information.
Zapier not working for you?
Zapier not working for you?
Zapier conducted a scheduled maintenance window to upgrade database security, affecting the Website component. The maintenance began at and completed at , with the Website returning to normal operation afterward. The incident included two official status updates during the window.
Zapier conducted scheduled maintenance for a database upgrade that affected the Zapier Website. The maintenance window began at and concluded at , with the Website component listed as in maintenance during the window. The incident lasted about 1 hour, and two status updates were posted during the window to communicate the ongoing upgrade and its completion, after which the Website returned to normal operation. The maintenance was planned and limited to the Website, with no wider impact indicated for other Zapier services.
Zapier conducted scheduled maintenance on the Website component to apply Database Security Upgrades. The maintenance window began at and ended at , lasting about 1 hour. During this period, access to the Zapier Website may have been unavailable or degraded as updates were applied. The status page noted the maintenance as in progress with the message "Database Security Upgrades."
Zapier's Slack-based Zaps experienced delayed processing due to a Slack outage. Slack's incident caused delays in Slack-triggered events, resulting in degraded performance for users relying on Slack as a trigger. This affected Zapier's Slack integration, causing intermittent delays across Slack-driven workflows.
The degraded period began on and continued until when the Slack incident was resolved. Slack acknowledged the incident and reported delays in Slack Trigger Processing, which Zapier's status updates documented as a prolonged degradation of Slack-triggered Zaps. The outage was global in scope, with updates issued as the situation progressed.
Zapier experienced an outage that prevented access to the Zap Editor, affecting the Website component and leaving users unable to create or edit Zaps. The incident began at and lasted until , roughly 16 hours. Zapier reported that a fix had been implemented and that monitoring was ongoing, with guidance to hard refresh if users encountered 500 errors. The provider issued two status updates during the incident as they investigated and worked to restore services.
Zapier's Jira Software Cloud integration experienced a partial outage beginning at . The issue caused delayed triggers, missing samples in the Zap editor, and timeouts in actions for Zaps relying on Jira Software Cloud. The outage lasted for roughly 44 hours, affecting automation workflows across the Jira Software Cloud app within Zapier.
Zapier documented the incident via status updates, noting monitoring and ongoing efforts to resolve the problem. The final update restored normal operation on . In total, two official status updates were issued during the incident, and the impact appeared global rather than localized to a specific region.
Looking for more Zapier outage stats?
Get real-time insights and historical data on Zapier outages.
