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
Maintenance: Scheduled: Permissions Service Maintenance
Status: Scheduled During this window, we will be upgrading the infrastructure behind our permissions service. You may see two short blips where saves, edits, and other permission-dependent actions briefly error out. During each blip, saves and edits to Zaps, Folders, Agents, MCP, Templates, and Knowledge Sources may error; retrying should succeed. No action needed from your end. Questions? Contact Zapier Support: https://zapier.com/app/get-help. Affected components Website (Under maintenance)
Maintenance: Scheduled: Infrastructure Maintenance
Status: Scheduled During this window, Zaps with polling-based triggers will pause briefly and resume automatically. Your Zaps stay “On”, and the next poll picks up any items missed. There is no action required on your end. Questions? Contact Zapier Support: https://zapier.com/app/get-help. Affected components Polling Triggers (Under maintenance)
Facebook Lead Ads Error: "Unsuported get request. Object with ID "..." does not exist, cannot be loaded due to missing permissions or does not support this operation"
Status: Resolved Between approximately 1:20 AM UTC and 10:38 AM UTC on May 13, 2026, Zaps using Facebook Lead Ads experienced failures due to an upstream issue with Meta’s Facebook Lead Ads API. During this time, Facebook Lead Ads Zaps were unable to process new leads. Some Zaps may have been automatically turned off due to repeated errors. Meta has resolved the issue on their end, and error rates have returned to normal. Your Zaps should now be functioning as expected, and new leads from Facebook will resume flowing through normally. Zaps that were automatically turned off have been re-enabled, and failed runs have been replayed. If you’re still experiencing issues, contact Support: https://zapier.com/app/get-help
Errors when creating or reconnecting app connections
Status: Resolved Our Engineering team has monitored our backend for any spikes in errors after the fix was released, and we're happy to see that we're at normal operation and no longer seeing errors. As such, the incident is now considered resolved. Please reach out to our Support team if you continue to see issues or have questions about the incident.
High Latency is impacting hook ingestion
Status: Resolved The issue has been resolved, and all systems are back to normal.
Google SSO Login Failures
Status: Resolved Our team has confirmed that since 21:14 UTC all customers logging into Zapier via Google SSO can do so successfully. If you are still running into any issues, please contact our support team for assistance: https://zapier.com/app/get-help Affected components Login (Operational)
Zap error notifications
Status: Resolved The issue causing incorrect “High Error Ratio” notifications has been resolved. Impact Some users received an email titled “High Error Ratio” indicating their Zap would be switched off. In certain cases, this did not reflect actual Zap performance, and some Zaps may have been paused incorrectly as a result. Resolution We implemented a fix and confirmed that notifications and Zap status are now behaving as expected. If you are still experiencing this issue causing your Zaps to turn off, you can reach out to our team at: https://zapier.com/app/get-help. Affected components Zap History (Operational)
Session initialization failed error when trying to connect apps
Status: Resolved We’ve resolved an issue where some users could see a “Session initialization failed” error when creating new app connections. The issue was caused by an unintended staged rollout configuration and was mitigated by rolling back the rollout. Existing Zaps and workflows were not impacted. If you saw a failed connection attempt during the incident window, please retry creating the connection now. If you’re still experiencing issues creating new app connections, please contact Zapier Support.
Errors related to Klaviyo app integration
Status: Resolved The issue causing 522 timeout errors with the Klaviyo app integration has been resolved. This was related to an upstream service disruption on Klaviyo's side: https://status.klaviyo.com/incidents/yyh7s59brj67 Zaps using Klaviyo should now be functioning as expected. No data loss occurred — any Zap runs that failed during the incident can be replayed from Zap History. If you are still experiencing issues with your Klaviyo integration, please contact Support: https://zapier.com/app/get-help Thank you for your patience.
Incoming webhooks — some requests not processed (encoding in Content-Type)
Status: Resolved We've implemented an update so webhooks sent with a Content-Type header that specified a non-UTF-8 character set will trigger your Zaps.
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.