Is Zapier Down?
Real-time status check for zapier.com
Checking status...
About Zapier Status
BlueMonitor checks Zapier (zapier.com) by sending automated requests to its servers. If the service responds within a normal timeframe and returns a successful status code, it's marked as operational. Response times over 3 seconds indicate the service is slow, and connection failures or server errors indicate the service may be down.
Recent Incidents
Internal Server Errors (HTTP 500) affecting Zaps
Status: Resolved We’ve resolved the issue causing intermittent Internal Server Errors (HTTP 500) for some Enterprise customers when editing Zaps that use app approvals. Our teams implemented a fix and confirmed recovery. If you continue to experience issues editing affected Zaps, please contact support. https://zapier.com/app/get-help Affected components Zap Editor (Operational)
Zaps Paused due Prior Connection Failure with Google Services
Status: Resolved We’ve resolved the issue related to Zaps that were paused during a prior authentication incident. Some Zaps were automatically paused as a protective measure during an earlier incident "an earlier incident": https://status.zapier.com/incidents/01KMZFA6V1H9WP71FD7XZ8MP4A and did not automatically resume afterward. We investigated and confirmed the scope, and provided guidance directly to affected customers on how to review and restore any impacted Zaps. If you believe you may have been impacted, please review any paused Zaps and re-enable them as appropriate. And as always, Our support team is available if you have questions or need help getting workflows running again. If this is the case, or if you have any other questions please let us know at https://zapier.com/app/get-help
Database Upgrade
Status: Resolved TLDR: A production upgrade for Monolithdb from version 8.0.40 to 8.4.8 is currently resolved now and everything is functional. All systems are back to normal
Intermittent failures across tasks due to exhausted db connections for developercli
Status: Resolved We have successfully completed the recovery process for the intermittent task failures that occurred between March 24-26, 2026. Our team replayed all affected tasks, which have been successful with no data loss. **What Happened** Between March 24 at 11:02 AM UTC and March 26 at 2:04 PM UTC, some tasks failed for customers using Zaps that depend on our developercli service. **Resolution** We fixed the underlying issue causing this failure and completed a full replay of all impacted tasks. No action is needed on your side if affected — tasks have been automatically recovered and are now running normally. Thank you for your patience while we worked through this issue. If you do have any other questions or see any issues, please reach out to our Support team at zapier.com/app/get-help "zapier.com/app/get-help": http://zapier.com/app/get-help Affected components Zap History (Operational)
Maintenance: Database Upgrade
Status: Scheduled During this maintenance window, some users may experience delays with triggers, and Zapier.com may return 502 (Bad Gateway) or 503 (Service Unavailable) errors. While we anticipate minimal disruption, downtime could last up to 30 minutes. Affected components Instant Triggers (Under maintenance) Website (Under maintenance) Polling Triggers (Under maintenance)
Payment failures for some customers
Status: Resolved Earlier, a script error unintentionally detached saved payment methods for some active customers. This caused increased payment errors and prevented some customers from completing checkout, renewing subscriptions, upgrading plans, or paying invoices. We worked with Stripe to reattach impacted customers’ payment methods in bulk, including a final batch for any remaining affected accounts. Payment processing has resumed and our monitoring indicates payment error rates and invoice processing are back to normal. If you’re still having trouble making a payment, please contact Support: https://zapier.com/app/get-help
Monitoring a publicly reported LiteLLM package issue
Status: Resolved We’ve completed our review of the publicly reported LiteLLM package issue. Zapier was not affected. Our review confirmed that the LiteLLM versions used in our environments were not among the publicly reported impacted versions, and we found no evidence of unauthorised access or impact on customer data, Zapier systems, or services. We will continue to monitor for any new information and will share updates if anything changes. If you see any further issues, please reach out to our support team at https://zapier.com/app/get-help.
MCP Servers: Issues adding/removing tools
Status: Resolved We’ve deployed a fix for the issue that prevented some users from adding or removing tools on Zapier MCP servers, and we’ve confirmed the issue is resolved. We apologize for the disruption and appreciate your patience as we got this resolved. If you see any further issues, please reach out to our support team at https://zapier.com/app/get-help Affected components MCP (Operational)
OAuth Authorization Page Is Blank
Status: Resolved Resolved - We have confirmed that the issue causing a blank OAuth Authorization page on zapier.com "zapier.com": http://zapier.com and during new connection setup has been fully resolved. If you run into any issues, please reach out to us here: https://zapier.com/app/get-help Affected components Website (Operational)
Connection Failure with Google Services
Status: Resolved We've resolved an issue causing connection/authentication failures across Google Sheets, Google Drive, and Google Docs integrations. A recent deployment introduced a change to Google authentication fields, which led to widespread refresh/stale authentication errors. This also had an impact on Agents and MCP workflows that use these Google integrations. All impacts have been mitigated, and authentication error rates have returned to baseline. If you're still seeing issues, re-check your workflows and reconnect your Google account if prompted. We also recommend reviewing your Zap history for any gaps during the incident window, especially for high-volume or business-critical workflows. If you identify missing data, you can re-process it by replaying the affected tasks in your Zap history or using Transfer to backfill: Transfer existing data using a Zap "Transfer existing data using a Zap": https://zapier.com/help/manage/history/transfer-existing-data-using-a-zap. For any other issues or questions, please reach out to our support team at https://zapier.com/app/get-help. Affected components Agents (Operational)
Frequently Asked Questions
Is Zapier down right now?
This page shows the real-time status of Zapier. The status is checked automatically by pinging Zapier's servers. If the status shows "Down", it means Zapier is currently experiencing issues.
Why is Zapier not working?
Zapier may not be working due to server outages, scheduled maintenance, network issues, or high traffic. Check the current status above for real-time information.
How do I check if Zapier is down for everyone?
BlueMonitor checks Zapier's servers from our monitoring infrastructure. If the status shows "Down" here, it's likely down for everyone. If it shows "Up" but you can't access it, the issue may be on your end.
What should I do if Zapier is down?
If Zapier is down, you can: wait a few minutes and try again, check their official social media for updates, clear your browser cache, or try using a different network connection.