Zapier Outage History

Started May 19, 2026, 11:23 PM UTC· resolved May 20, 2026, 12:11 AM UTC

1. monitoring May 19, 2026, 11:23 PM UTC

   Our Engineering team is currently monitoring reports indicating that Enterprise users with a high number of app restrictions (over 100) are unable to modify or manage custom actions. Affected users will see the following error when viewing custom actions. We couldn't determine whether this app is restricted. Please try again in a moment. We'll continue to keep our customers informed as we identify the root cause and resolve the issue.

2. resolved May 20, 2026, 12:11 AM UTC

   The issue preventing some enterprise customers from managing custom actions has been resolved. Customers with over 100 app restrictions were unable to paginate through their custom actions due to a URL formatting issue in our system. This has been corrected and all affected pages now load as expected. No data was lost and no customer action is required. If you're still experiencing issues, contact Support: https://zapier.com/app/get-help Thank you for your patience.

Read the full incident report →

Started May 13, 2026, 03:55 AM UTC· resolved May 13, 2026, 03:49 PM UTC

1. investigating May 13, 2026, 03:55 AM UTC

   We are currently investigating a spike in errors affecting Facebook Lead Ads integrations. Users may experience failures when running Zaps connected to Facebook Lead Ads, with errors related to missing permissions or unsupported requests. Our integrations team is actively investigating the root cause and working toward a resolution. We will provide updates as soon as we have more information.

2. identified May 13, 2026, 05:53 AM UTC

   We have identified the cause of the issue affecting Zaps connected to Facebook Lead Ads. Our investigation confirms this is due to an upstream issue with Meta's API — specifically, requests to Facebook Lead Ads are returning permission or access errors that originate on Meta's side. At this stage, it does not appear that the Zapier product or Integration changes are contributing to this incident. Users with Zaps that include Facebook Lead Ads steps may experience failures or see that new leads are not appearing in Zapier as expected. We've reported the issue to Meta and are actively monitoring the situation, and will provide updates as the situation develops. Thank you for your patience.

3. identified May 13, 2026, 07:48 AM UTC

   We've identified the issue as an upstream outage impacting the Facebook Lead Ads API. This is causing failures for Facebook Lead Ads Zaps, including errors during lead hydration and missing leads. What you may be experiencing: • Your Facebook Lead Ads Zaps are failing to run • Some Zaps may have been automatically paused due to repeated errors What we recommend: • Do not manually turn off your Facebook Lead Ads Zaps • If your Zap has been automatically paused, please leave it as-is for now, as it may automatically turn off again • Once the upstream Facebook issue is resolved, we will work to replay the missed leads Our team has submitted a bug report to Facebook and is actively monitoring the situation. We are also identifying all affected Zaps so we can support recovery as quickly as possible once Facebook restores the service. We will post another update when the situation changes or when we have more information to share.

4. identified May 13, 2026, 01:21 PM UTC

   We're now seeing a significant decrease in errors related to Facebook Lead Ads, indicating that Meta has begun mitigating the upstream issue affecting lead retrieval. Current Status: Error rates are dropping, and we're confirming that leads are beginning to flow through again for affected Zaps. We're actively monitoring the situation to ensure full recovery. Next Steps: Our team is now working on replaying the leads that failed to process during the incident window. We'll have more details on timing and any customer actions needed in our next update. Thank you for your patience as we work through this with Meta. We'll continue to post updates as the situation progresses.

5. monitoring May 13, 2026, 02:10 PM UTC

   Facebook has mitigated the upstream issue affecting Facebook Lead Ads lead retrieval. The incident began at approximately 1:20am UTC on May 13, 2026 and was resolved at 10:38am UTC on May 13, 2026. Your Zaps should now be functioning as expected, and new leads from Facebook should resume flowing through normally. We’ll continue monitoring and will share another update if anything changes.

6. resolved May 13, 2026, 03:49 PM UTC

   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

Read the full incident report →

Started May 08, 2026, 09:02 PM UTC· resolved May 08, 2026, 10:11 PM UTC

1. investigating May 08, 2026, 09:02 PM UTC

   We are currently investigating an issue where users may encounter the following error when creating a new connection or reconnecting an app: "Failed to execute 'removeChild' on 'Node': parameter 1 is not of type 'Node'. Uh oh, something is not quite right!" Our team is actively working to identify the root cause. We’ll provide updates as soon as more information is available.

2. identified May 08, 2026, 09:26 PM UTC

   We’ve identified the root cause of the issue causing errors when creating or reconnecting app connections, including the message: "Failed to execute 'removeChild' on 'Node': parameter 1 is not of type 'Node'. Uh oh, something is not quite right!" Our team is working on implementing a fix. We’ll share another update as soon as more information is available.

3. monitoring May 08, 2026, 09:33 PM UTC

   We’ve rolled back a recent change that was identified as the cause of errors when creating or reconnecting app connections. We are seeing signs of recovery and are continuing to monitor performance closely to ensure the issue is fully resolved. We’ll provide another update once monitoring is complete.

4. resolved May 08, 2026, 10:11 PM UTC

   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.

Read the full incident report →

Started May 08, 2026, 08:32 PM UTC· resolved May 08, 2026, 09:34 PM UTC

1. investigating May 08, 2026, 08:32 PM UTC

   We are currently investigating an issue causing elevated latency in hook ingestion and event processing. As a result, some customers may experience delays of approximately 30–40 minutes before events are processed. Our team is actively working on the fix.We appreciate your patience and understanding while we work to resolve this issue.

2. resolved May 08, 2026, 09:34 PM UTC

   The issue has been resolved, and all systems are back to normal.

Read the full incident report →

Started May 06, 2026, 08:57 PM UTC· resolved May 06, 2026, 11:18 PM UTC

1. investigating May 06, 2026, 08:57 PM UTC

   We are currently investigating an issue impacting Google single sign-on (SSO). Users attempting to log in to their zapier.com account using Google SSO may be unable to authenticate at this time. Impact All users are affected when using Google SSO. Login via username and password remains available, and users with active sessions are not impacted. Running automations continue to operate normally. Current Status Our engineering team is actively investigating the root cause. Initial efforts are focused on reviewing Google SSO configuration, credentials, and related environment variables. Relevant teams have been engaged and are working to identify and resolve the issue as quickly as possible. We will provide further updates as more information becomes available.

2. monitoring May 06, 2026, 09:20 PM UTC

   Monitoring: Google SSO Login Failures We have identified the issue impacting Google single sign-on (SSO) and have rolled back a recent website update as part of our mitigation efforts. Impact Users may have experienced failures when attempting to log in with Google SSO. Login via username and password remained available, and users with active sessions were not impacted. Running automations continued to operate normally. Current Status We are now monitoring the results of the rollback and are seeing signs of recovery. Our team will continue to observe system performance to ensure stability. We will provide further updates if any additional issues arise or once the incident is fully resolved.

3. resolved May 06, 2026, 11:18 PM UTC

   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

Read the full incident report →

Started May 06, 2026, 05:13 PM UTC· resolved May 07, 2026, 04:49 PM UTC

1. investigating May 06, 2026, 05:13 PM UTC

   We’re investigating an issue affecting some Zaps that use error handling. You may have received an email titled “High Error Ratio” explaining that your Zap would be switched off. In some cases, that may not have matched what you see in normal use, and your Zap may have been paused as a result. We’re working on a fix to prevent this from happening again. If that happened to your Zap, you can turn it back on from your Zapier dashboard. We’ll post another update here when we have more to share.

2. monitoring May 06, 2026, 07:35 PM UTC

   We’ve deployed a fix for an issue affecting some Zaps that use error handling. You may have received an email titled “High Error Ratio” explaining that your Zap would be switched off. In some cases, that may not have matched what you see in normal use, and your Zap may have been paused as a result. We’re monitoring closely to confirm the fix is working as expected and to ensure this does not recur. If your Zap was paused, you can turn it back on from your Zapier dashboard. We’ll post another update here if anything changes. 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.

3. resolved May 07, 2026, 04:49 PM UTC

   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.

Read the full incident report →

Started May 05, 2026, 10:49 PM UTC· resolved May 06, 2026, 12:34 AM UTC

1. investigating May 05, 2026, 10:49 PM UTC

   We are currently investigating an issue where users receive "Session initialization failed" errors when attempting to connect apps in Zapier.

2. monitoring May 05, 2026, 11:06 PM UTC

   We are monitoring reports where users receive "Session initialization failed" errors when attempting to connect apps in Zapier. If you are experiencing issues with this, you can reach out to our team at: https://zapier.com/app/get-help

3. resolved May 06, 2026, 12:34 AM UTC

   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.

Read the full incident report →

Started May 05, 2026, 09:32 PM UTC· resolved May 06, 2026, 02:20 AM UTC

1. investigating May 05, 2026, 09:32 PM UTC

   We are looking into an issue related to the Klaviyo app returning 522 timeout errors. This is related to an incident with Klaviyo here: https://status.klaviyo.com/incidents/yyh7s59brj67

2. monitoring May 05, 2026, 09:45 PM UTC

   We are continuing to monitor the service disruption related to Klaviyo: https://status.klaviyo.com/incidents/yyh7s59brj67 If you are experiencing issues with this app integration, you can reach out to our team at: https://zapier.com/app/get-help

3. resolved May 06, 2026, 02:20 AM UTC

   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.

Read the full incident report →

Started May 05, 2026, 08:58 PM UTC· resolved May 05, 2026, 10:37 PM UTC

1. monitoring May 05, 2026, 08:58 PM UTC

   Between April 26, 2026, 7:14 PM UTC and April 30, 2026, 4:36 AM UTC, a subset of incoming webhooks to Zapier were not processed during ingestion. Webhooks sent with a Content-Type header that specified a non-UTF-8 character set in the way below were rejected instead of being delivered to your Zaps: Content-Type: application/x-www-form-urlencoded; charset=iso-8859-1 Webhooks using typical UTF-8 Content-Type values were not affected by this issue. If your upstream system sent webhooks matching the pattern above during that time window, those individual events did not trigger your Zaps. Other triggers and webhook formats continued to work as usual. For any specific events that occurred while your app was sending webhooks in that format during the window above, you will need to resend the webhook from the upstream application (for example, by having that app fire the event again or resubmit the payload), so that Zapier receives a new request. Replaying a past run in Zapier does not replace a missing inbound webhook from your app. If you are unsure whether your integration uses that header, check your server or integration configuration for charset=iso-8859-1 (or other non-UTF-8 charset) on application/x-www-form-urlencoded requests to your Zap’s webhook URL.

2. resolved May 05, 2026, 10:37 PM UTC

   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.

Read the full incident report →

Started May 01, 2026, 07:51 AM UTC· resolved May 01, 2026, 08:15 AM UTC

1. monitoring May 01, 2026, 07:51 AM UTC

   At approximately 4:45 AM UTC we experienced degraded performance affecting agents web search and chatbot website knowledge-source syncing due to an outage at our third-party provider, Firecrawl. Firecrawl has recovered and our services are operating normally again. Most affected runs recovered automatically, but a subset of agent runs may have failed during the incident window—customers can check their Activity and retry failed runs if needed. We’re continuing to monitor for any residual errors and will provide an update before closing.

2. resolved May 01, 2026, 08:15 AM UTC

   No additional customer reports have been received during the monitoring period. The incident is ready to be closed.

Read the full incident report →

Started Apr 28, 2026, 07:06 PM UTC· resolved Apr 28, 2026, 07:28 PM UTC

1. investigating Apr 28, 2026, 07:06 PM UTC

   Users are unable to access the Admin Center within Zapier settings. This controls access to SSO, SCIM, app connections, and other user management settings. The Admin Center page does not finish loading, but doesn't show an error otherwise Our Engineering team has confirmed the issue and is working toward resolving the problem as soon as possible.

2. monitoring Apr 28, 2026, 07:18 PM UTC

   A fix has been applied to the Admin Center, and we're now monitoring for any adverse effects. We'll continue to keep the incident open until we can confirm normal operations for the Admin Center.

3. resolved Apr 28, 2026, 07:28 PM UTC

   We can confirm that the Admin Center is now loading as expected, and the issue is now resolved. If you're still unable to load the page, you may need to reload the page and/or clear your browser's cookies and cache. If you're experiencing any issues with this was not resolved by clearing browser cache and cookies, please reach out to our support team here: https://zapier.com/app/get-help

Read the full incident report →

Started Apr 28, 2026, 04:11 PM UTC· resolved Apr 28, 2026, 08:45 PM UTC

1. investigating Apr 28, 2026, 04:11 PM UTC

   We’re seeing delays and timeouts affecting parts of Zapier. Our team is investigating and working to restore normal performance. What you might notice Slower responses or failed actions in places that depend on signing in or loading account information. Some Zaps and background tasks may also run more slowly or time out. Experiences that use AI or chat-style features may also be affected. What we know Our systems are under a heavier load than usual. We’ve narrowed the problem to unusually high demand on account-related requests and are working to confirm what’s driving it and how to safely reduce the load. What we’re doing We’re focused on stabilizing performance and will share more as we have concrete progress. Next update We expect to post another update within about 30 minutes. We’re sorry for the trouble this causes and thank you for your patience. Questions? Contact our Support team: https://zapier.com/app/get-help

2. monitoring Apr 28, 2026, 04:45 PM UTC

   We’ve identified the cause of the issues affecting Zapier.com "Zapier.com": http://Zapier.com and have implemented a fix. The site should now be loading as expected, and any delayed trigger events should be processing. We’re continuing to monitor performance to ensure everything is fully restored and will share another update once the issue is completely resolved.

3. resolved Apr 28, 2026, 08:45 PM UTC

   The performance issues that caused delays and timeouts on Zapier.com "Zapier.com": http://Zapier.com have now been resolved. Our systems have remained stable, and signing in, loading account information, and running Zaps should behave normally. During the incident, some customers may have seen slower responses, failed actions, or delayed trigger processing while we reduced load and shipped the fix. Everything should now be caught up; if you still see anything unexpected, try running your Zap again. If you need help with a specific Zap or account, contact our Support team: https://zapier.com/app/get-help

Read the full incident report →

Started Apr 27, 2026, 11:43 PM UTC· resolved Apr 28, 2026, 01:41 AM UTC

1. identified Apr 27, 2026, 11:43 PM UTC

   Users have reported that transferring ownership between Team members returns the following error. Unable to verify identity. Please try again. Our Engineering team is looking into the issue and working to identify the root cause. We'll continue to update you as we have more information.

2. monitoring Apr 28, 2026, 12:58 AM UTC

   A fix has been released, and we're now monitoring for any unexpected issues due to the fix being released. We'll continue to monitor until we're confident the issue has been resolved.

3. resolved Apr 28, 2026, 01:41 AM UTC

   The issue preventing ownership transfer in Teams and Enterprise accounts has been resolved. Account ownership transfers can now be self-served by following this guide: https://help.zapier.com/hc/en-us/articles/17946190203789-How-to-transfer-ownership-of-your-Team-or-Enterprise-account If you're experiencing any issues with this, please do reach out to our support team here: https://zapier.com/app/get-help

Read the full incident report →

Started Apr 27, 2026, 06:06 PM UTC· resolved Apr 27, 2026, 07:26 PM UTC

1. investigating Apr 27, 2026, 06:06 PM UTC

   We're currently investigating an issue where loading upcoming invoices on the billing page can return errors (HTTP 500) instead of showing invoice details. We will update the page as soon as we have more information. If you have any questions, please reach out to our Support Team - https://zapier.com/app/get-help

2. monitoring Apr 27, 2026, 06:55 PM UTC

   Databricks has released a fix that has resolved the upstream issue causing users to not be able to access invoices. The billing and invoices page is working again, allowing invoices to be viewed and downloaded again. We will continue to monitor the situation and provide any more details as they arise. If you have any questions, please reach out to our Support Team - https://zapier.com/app/get-help

3. resolved Apr 27, 2026, 07:26 PM UTC

   The issue affecting invoice access and downloads has been resolved. Service was fully restored at 18:30 UTC on April 27, 2026. At 17:20 UTC an outage from the Databricks App caused invoices to fail to load or download from the Billing and Invoices Page. Databricks released a fix for their outage and invoices are functioning as normal. If you attempted to view or download any invoices during this time, you can retry that action now. We apologize for the inconvenience this caused and appreciate your patience while the issue was resolved. If you have any questions, please reach out to our Support Team - https://zapier.com/app/get-help

Read the full incident report →

Started Apr 24, 2026, 07:31 PM UTC· resolved Apr 25, 2026, 03:58 AM UTC

1. investigating Apr 24, 2026, 07:31 PM UTC

   We are investigating an error related to AI by Zapier when adding a knowledge source. If you are experiencing this issue, you can connect with our support team here: https://zapier.com/app/get-help

2. resolved Apr 25, 2026, 03:58 AM UTC

   The issue causing some AI by Zapier steps to fail with a 500 error when adding a knowledge source has been resolved. If you were affected by this issue, your Zaps with AI by Zapier steps using knowledge sources will now work again. To restore functionality: 1. Open the affected Zap and navigate to the AI by Zapier step 2. Before deleting the step, we recommend copying and saving your prompt to avoid losing any work. 3. Delete the step 4. Re-add the AI by Zapier step 5. Copy your previous prompt into the new step 6. Re-upload your knowledge sources Once you've completed these steps, your Zap will be ready to use. If you are experiencing this issue, you can connect with our support team here: https://zapier.com/app/get-help.

Read the full incident report →

Started Apr 21, 2026, 11:40 PM UTC· resolved Apr 22, 2026, 12:19 AM UTC

1. investigating Apr 21, 2026, 11:40 PM UTC

   We are currently investigating an issue affecting chatbot users. Users are unable to use chat completion features, and all interaction attempts are resulting in the following error message: “There is a temporary issue with OpenAI: Attempted to access resource with incorrect regional hostname. Please make your request to api.openai.com "api.openai.com": http://api.openai.com” Our engineering team is actively working to identify the root cause and implement a solution. We will provide updates on this status page as progress is made. If you are experiencing issues or need assistance, please contact our support team: https://zapier.com/app/get-help

2. resolved Apr 22, 2026, 12:19 AM UTC

   The issue affecting chatbot users has been resolved. Chat completion features are now functioning normally, and users should no longer encounter error messages when interacting with chatbots.

Read the full incident report →

Started Apr 21, 2026, 03:38 AM UTC· resolved Apr 21, 2026, 05:05 AM UTC

1. investigating Apr 21, 2026, 03:38 AM UTC

   We are currently investigating an issue that is preventing some customers from accessing their chatbots. Affected users have reported seeing "Unable to load Chatbot" errors when attempting to view or manage their chatbots. We are looking into the cause of this issue and will update this status as soon as possible.

2. monitoring Apr 21, 2026, 04:01 AM UTC

   We’ve identified and addressed an issue that was preventing some users from accessing chatbots due to an authentication issue. All chatbot services are operating normally. We are continuing to monitor system performance and verify full restoration across all customer segments. If you experience any further issues accessing your chatbots, please contact our support team: https://zapier.com/app/get-help.

3. resolved Apr 21, 2026, 05:05 AM UTC

   We have successfully resolved the chatbot availability issue that affected some of our users. Our engineering team identified and resolved the underlying authentication issue. All chatbot services are now operating normally. You should now be able to view and manage your chatbots in the dashboard and use them externally without any issues. We have monitored and verified that the service is working properly. We apologize for any disruption this may have caused. If you experience any further issues accessing your chatbots, please contact our support team: https://zapier.com/app/get-help.

Read the full incident report →

Started Apr 20, 2026, 09:11 PM UTC· resolved Apr 21, 2026, 05:01 AM UTC

1. investigating Apr 20, 2026, 09:11 PM UTC

   agents.zapier.com "agents.zapier.com": http://agents.zapier.com is down and not responding. The websites are inaccessible for all users. We are looking into the cause of this issue and will update this status as soon as possible.

2. investigating Apr 20, 2026, 09:20 PM UTC

   agents.zapier.com: http://agents.zapier.com/ is down and not responding. The websites are inaccessible for all users. Canvas is also not loading for users. With that said, Agent jobs appear to still be functioning as normal We are looking into the cause of this issue and will update this status as soon as possible.

3. monitoring Apr 20, 2026, 09:46 PM UTC

   We have deployed a fix, and both Agents and Canvas appears to now be loading and working as they should be. We are now monitoring these changes, and will update this status once this issue is fully resolved

4. resolved Apr 21, 2026, 05:01 AM UTC

   We confirm that the fix deployed has resolved the issue with Agents and Canvas, and both are functioning correctly. All Agent workflow executions that were stuck on 'In Progress' status during this incident have been replayed. If you are experiencing any issues with Zapier Agents or Canvas, please contact our support team through this link: https://zapier.com/app/get-help

Read the full incident report →

Started Apr 20, 2026, 06:14 PM UTC· resolved Apr 20, 2026, 06:57 PM UTC

1. identified Apr 20, 2026, 06:14 PM UTC

   Our team has identified an issue affecting Chatbot and Forms creation. Existing Forms can be edited normally. For Chatbots, users might see an error when updating the slug as well. The Engineering team is working on a fix, and we'll be updating this status page shortly once resolved.

2. monitoring Apr 20, 2026, 06:27 PM UTC

   The issue affecting Chatbot and Forms creation is now resolved. Customers can now create any assets normally, and update slugs as needed. Existing assets remained unaffected. We'll continue to monitor our systems and provide a final update shortly

3. resolved Apr 20, 2026, 06:57 PM UTC

   This incident is fully resolved. Customers can now create Chatbots and Forms as usual. Many thanks for your patience, and feel free to reach out to our support team if you have any questions at: zapier.com/get-help.

Read the full incident report →

Started Apr 19, 2026, 11:10 PM UTC· resolved Apr 20, 2026, 01:05 AM UTC

1. investigating Apr 19, 2026, 11:10 PM UTC

   Due to a third party outage, we are investigating an outage causing failures for chatbot users attempting to add new knowledge sources that require web-scraped knowledge sources. Existing knowledge sources for Chatbots remain functional. Agents executions do not crash, or get marked as failed, but users may get a bad response when web browsing/scraping. There are not user facing errors for this behaviour. Main error periods: 19:18–19:35 UTC and 21:35–22:32 UTC. Errors began around 19:19UTC, and subsided after 22:32 UTC, and monitoring shows no new failures. If you need help or have any questions, please contact Support: https://zapier.com/app/get-help

2. monitoring Apr 19, 2026, 11:28 PM UTC

   A fix has been deployed to resolve these errors with web-scraping knowledge sources. We will continue to monitor. If you have any questions or continue to experience issues, please reach out to our support team: https://zapier.com/app/get-help Thank you for your patience.

3. resolved Apr 20, 2026, 01:05 AM UTC

   We have resolved the issue with web-scraping tools not working throughout tools like Agents, Chatbot knowledge sources, and Web Parser. For any questions, or if you're still seeing failures with web-scraping tools in Zapier, please contact: https://zapier.com/app/get-help

Read the full incident report →

Started Apr 16, 2026, 08:04 PM UTC· resolved Apr 17, 2026, 10:51 PM UTC

1. identified Apr 16, 2026, 08:04 PM UTC

   We have identified an issue where links to access Zap data exports are returning errors and are temporarily inaccessible. Users who attempt to access a previously generated Zap export link may be unable to do so at this time. We will provide an update within the next 2 hours (3 PM PST).

2. resolved Apr 16, 2026, 08:14 PM UTC

   This incident has been resolved. Links to access Zap data exports are now working as expected. Some users were temporarily unable to access previously generated Zap export links. No data was lost or compromised. Our engineering team identified and deployed a fix. Export links have been confirmed as working in production. If you experience ongoing issues, contact Support by clicking above or go to: https://zapier.com/app/get-help

3. investigating Apr 17, 2026, 01:50 PM UTC

   We have received reports that some users are still experiencing issues accessing Zap run history export download links. This issue was previously identified and resolved on April 16, but we are now seeing reports that it is still occurring for some users. Our team is actively investigating. We will provide updates here as we learn more.

4. monitoring Apr 17, 2026, 02:50 PM UTC

   We’ve made a change to fix an issue where some emailed download links for Zap history exports and account data exports were failing. We’re monitoring to confirm downloads are working normally again. If you received a broken link earlier, please request a new export email (older emails may still contain the broken link). If you experience ongoing issues, contact Support by clicking above or go to: https://zapier.com/app/get-help

5. resolved Apr 17, 2026, 10:51 PM UTC

   We have been able to get this issue resolved. Users should now be able to successfully download their Zap Run History export files. If you are running into any other issues, feel free to reach out to Zapier Support: https://zapier.com/app/get-help

Read the full incident report →

Started Apr 16, 2026, 02:08 PM UTC· resolved Apr 16, 2026, 02:28 PM UTC

1. monitoring Apr 16, 2026, 02:08 PM UTC

   We have identified an issue that affected Zapier Agents during a 15-minute window between 9:00AM-9:15AM EST, due to a temporary connection failure. A fix has been implemented and Agent runs are executing successfully. We will continue to monitor the service to confirm resolution.

2. resolved Apr 16, 2026, 02:28 PM UTC

   The connectivity issue which affected Zapier Agents during a 15 minute window is fully resolved. Agent executions are back to normal, and connectivity remains stable. If you have any questions, please reach out to our support team at: zapier.com/get-help.

Read the full incident report →

Started Apr 15, 2026, 09:52 PM UTC· resolved Apr 15, 2026, 11:38 PM UTC

1. investigating Apr 15, 2026, 09:52 PM UTC

   We are currently investigating 404 errors while editing zap templates. Our engineering team is actively investigating the root cause and exploring solutions. We'll update this status page as we make progress toward a resolution. If you're experiencing issues or need assistance, please contact our support team at https://zapier.com/app/get-help

2. resolved Apr 15, 2026, 11:38 PM UTC

   The issue causing 404 errors when editing and deleting Zap templates has been resolved. Users attempting to edit templates were encountering 404 errors due to a routing misconfiguration introduced during an ATC (Application Traffic Control) rollout, which changed the default ATC origin from the monolith to the marketing site. This broke routing for the /zap-templates path, causing edit actions to fail. The fix was deployed by completing the ATC routing correction to production. Once the rollout completed, edit functionality was restored. A remaining cosmetic bug — where the UI incorrectly indicates a template deletion failed despite the deletion succeeding — has been identified as a separate, no-impact bug and does not affect actual data. No data was lost as a result of this incident. If you're still experiencing issues, please contact Support by clicking above or visit: https://zapier.com/app/get-help Thank you for your patience.

Read the full incident report →

Started Apr 14, 2026, 12:50 PM UTC· resolved Apr 14, 2026, 09:09 PM UTC

1. investigating Apr 14, 2026, 12:50 PM UTC

   We are currently investigating intermittent delays affecting Slack-triggered Zaps. Starting around Friday, April 11th. If you use Slack as a trigger for your Zaps, you may experience delays in execution for a small subset of your workflows. Our engineering team is actively investigating the root cause, and we'll update this status page as we make progress toward a resolution. We apologize for any disruption this may cause to your Zaps. If you have questions or need assistance, please contact our support team at https://zapier.com/app/get-help

2. resolved Apr 14, 2026, 09:09 PM UTC

   We have successfully resolved the intermittent delays affecting Slack-triggered Zaps that began around Friday, April 11th. Our engineering team identified and deployed a fix, and Slack triggers are now operating as expected. If you continue to experience any delays with your Slack-triggered Zaps or have any questions, please don't hesitate to contact our support team at https://zapier.com/app/get-help We appreciate your patience while we worked through this issue.

Read the full incident report →

Started Apr 08, 2026, 05:27 PM UTC· resolved Apr 08, 2026, 07:33 PM UTC

1. investigating Apr 08, 2026, 05:27 PM UTC

   Copilot’s ‘Ask’ mode is currently malfunctioning, causing repeated prompts, duplicate messages, and eventual crashes when users try to build Zaps. This is causing that mode to be unable to build Zaps for users. For any users being affected by this, we can ask users to switch to “Build” mode in Copliot instead, as this mode is not affected and working correctly.

2. monitoring Apr 08, 2026, 06:36 PM UTC

   We have implemented a fix to the resolve the issue with the “Ask” mode in Copilot. We are currently monitoring that fix to ensure that everything is now working as it should.

3. resolved Apr 08, 2026, 07:33 PM UTC

   Copilot "Ask" mode is up and running again and and can be utilized for all accounts. Earlier today the "Ask" mode was malfunctioning, causing repeated prompts, duplicate messages, and eventual crashes when users attempted to build Zaps. If you experience ongoing issues, contact Support by clicking above or go to: https://zapier.com/app/get-help Thank you for your patience.

Read the full incident report →