Zapier service status
Check whether the provider lists a problem with the feature you use. Look at the update time and any affected regions.
Live Domain Check
Is Zapier Down? Check zapier.com Status and Outages
Run a live reachability check for zapier.com. Compare the regional responses with the problem you see in Zapier.
Find Zapier help and reporting links, specific checks, and step-by-step guidance below the live result.
Ready
Running automatic check…
Checking reachability from multiple regions.
Checked-
Verdict-
Response Time-
Final URL-
Regional checks
Is Zapier working for you?
Share a quick update and see what other visitors are experiencing.
What’s happening? Choose one to send your report.
Loading community reports…
—problem reports
—working reports
Past 24 hours15-minute totals · current interval in progress
Most reported problems
No problems reported in this period.
Visitor reports are separate from our automated checks and don’t confirm an outage. How reports work · Privacy
Understanding Zapier connection and service problems
Zapier editor access, trigger polling and actions at a connected service are separate stages.
The checker above requests zapier.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual Zapier action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
Looking for another service? Browse work app checks.
Zapier status information and official help
Zapier help and reporting
Use the Zap/run and failing connected-app step; preserve side-effecting run state.
Open zapier.com
Open the website in your browser and compare it with the result above.
Where to report problems with Zapier
Open Zapier help / reporting. Use the provider's customer-service or account-help route for the affected product. Sign-in may be required for private account questions.
Details to include in your report
Zap/run identifier, trigger/action app, failed step, response and event time without connected-account secrets.
Attach the checker’s downloaded JSON if it helps show the hostname, regional responses and original timestamps. Describe what happened in your browser or app as well. A report sent to WebsiteDown.org is not automatically forwarded to Zapier.
What to check when Zapier is not working
These are troubleshooting comparisons, not claims that Zapier is currently experiencing a particular incident.
Start with the action that failed
Inspect one Zap run to find the first failed step and whether the trigger event was received.
Narrow down the affected service
Check Zapier and the connected provider's status before replaying a run that could send messages or create records.
Read the actual checker response
A 403 Forbidden or 429 Too Many Requests means the host answered but refused or limited that request. A timeout gives no HTTP response. Keep those outcomes separate and check the available-region count before treating the result as broad evidence.
How to check if Zapier is down
- Save the error. Note what you were doing and when it failed. Save unfinished work before refreshing.
- Run the zapier.com check. Look at the regional results and when they were checked. Checking again may return a cached result.
- Check for a service notice. Open Zapier status and check whether the named service and incident time fit your error.
- Try another browser or network. Use the specific checks above to narrow down the problem. If it continues, send the error and time through the official help link.
If Zapier Is Not Working Only For You, Start Here
Use these local troubleshooting steps after the down-check workflow when Zapier seems broken only for you. This section focuses on app, browser, account, and network fixes.
1. Compare browser sessions
Open zapier.com in your current browser, then test in a private window or second browser. If only one session fails, compare its account, cookie and extension context before assuming the entire service is unavailable.
2. Preserve a working account session
Keep an existing working session and preserve unsaved work. For a sign-in failure, use the official account-help route. Avoid repeated password or security resets until you confirm this is not a broader Zapier issue.
3. Try another network
If possible, compare Wi-Fi with mobile data and note which one fails. Leave any required work VPN or security settings in place.
4. Capture support-ready evidence
Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting Zapier support.
Frequently asked questions about Zapier problems
Is Zapier down, or is the problem limited to one feature?
Run the zapier.com check and compare its original timestamps and responses with your actual error. Zapier editor access, trigger polling and actions at a connected service are separate stages.
Where can I report a problem with Zapier?
Use the community buttons on this page to share whether the service works for you. For help from Zapier, use the official help/reporting resource linked above. Use the Zap/run and failing connected-app step; preserve side-effecting run state.
What should I check first when Zapier is not working?
Inspect one Zap run to find the first failed step and whether the trigger event was received. Check Zapier and the connected provider's status before replaying a run that could send messages or create records.
What information helps Zapier support investigate?
Zap/run identifier, trigger/action app, failed step, response and event time without connected-account secrets.