Zapier Outage History

Zapier is up right now

There were 50 Zapier outages since February 4, 2026. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.zapier.com

Minor May 1, 2026

INC-908: Firecrawl outage

Detected by Pingoru
May 01, 2026, 08:15 AM UTC
Resolved
May 01, 2026, 08:15 AM UTC
Duration
Affected: Agents
Timeline · 2 updates
  1. monitoring May 01, 2026, 07:51 AM UTC

    Status: Monitoring 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. Affected components Agents (Degraded performance)

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

    Status: Resolved No additional customer reports have been received during the monitoring period. The incident is ready to be closed. Affected components Agents (Operational)

Read the full incident report →

Minor April 28, 2026

Service delays and timeouts across Zapier.com

Detected by Pingoru
Apr 28, 2026, 08:45 PM UTC
Resolved
Apr 28, 2026, 08:45 PM UTC
Duration
Affected: WebsiteSupportLogin
Timeline · 3 updates
  1. investigating Apr 28, 2026, 04:11 PM UTC

    Status: Investigating 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 Affected components Website (Degraded performance) Login (Degraded performance) Support (Degraded performance)

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

    Status: Monitoring 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. Affected components Website (Degraded performance) Login (Degraded performance) Support (Degraded performance)

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

    Status: Resolved 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 Affected components Website (Operational) Login (Operational) Support (Operational)

Read the full incident report →

Minor April 28, 2026

Users are unable to access Admin Center.

Detected by Pingoru
Apr 28, 2026, 07:28 PM UTC
Resolved
Apr 28, 2026, 07:28 PM UTC
Duration
Timeline · 3 updates
  1. investigating Apr 28, 2026, 07:06 PM UTC

    Status: Investigating 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

    Status: Monitoring 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

    Status: Resolved 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 →

Minor April 28, 2026

"Unable to verify identity. Please try again." Error when transferring ownership between Team members.

Detected by Pingoru
Apr 28, 2026, 01:41 AM UTC
Resolved
Apr 28, 2026, 01:41 AM UTC
Duration
Timeline · 3 updates
  1. identified Apr 27, 2026, 11:43 PM UTC

    Status: Identified 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

    Status: Monitoring 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

    Status: Resolved 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 →

Minor April 27, 2026

500 error when viewing upcoming invoices

Detected by Pingoru
Apr 27, 2026, 07:26 PM UTC
Resolved
Apr 27, 2026, 07:26 PM UTC
Duration
Affected: Website
Timeline · 3 updates
  1. investigating Apr 27, 2026, 06:06 PM UTC

    Status: Investigating 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 Affected components Website (Degraded performance)

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

    Status: Monitoring 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 Affected components Website (Operational)

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

    Status: Resolved 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 Affected components Website (Operational)

Read the full incident report →

Minor April 25, 2026

AI by Zapier action Fails with 500 error when a Knowlledge source is added

Detected by Pingoru
Apr 25, 2026, 03:58 AM UTC
Resolved
Apr 25, 2026, 03:58 AM UTC
Duration
Timeline · 2 updates
  1. investigating Apr 24, 2026, 07:31 PM UTC

    Status: Investigating 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

    Status: Resolved 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 →

Minor April 22, 2026

Chatbot

Detected by Pingoru
Apr 22, 2026, 12:19 AM UTC
Resolved
Apr 22, 2026, 12:19 AM UTC
Duration
Timeline · 2 updates
  1. investigating Apr 21, 2026, 11:40 PM UTC

    Status: Investigating 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

    Status: Resolved 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 →

Minor April 21, 2026

Chatbots failing to load

Detected by Pingoru
Apr 21, 2026, 05:05 AM UTC
Resolved
Apr 21, 2026, 05:05 AM UTC
Duration
Affected: Chatbots
Timeline · 3 updates
  1. investigating Apr 21, 2026, 03:38 AM UTC

    Status: Investigating 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. Affected components Chatbots (Degraded performance)

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

    Status: Monitoring 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. Affected components Chatbots (Degraded performance)

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

    Status: Resolved 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. Affected components Chatbots (Operational)

Read the full incident report →

Minor April 21, 2026

agents.zapier.com is down

Detected by Pingoru
Apr 21, 2026, 05:01 AM UTC
Resolved
Apr 21, 2026, 05:01 AM UTC
Duration
Affected: AgentsCanvas
Timeline · 4 updates
  1. investigating Apr 20, 2026, 09:11 PM UTC

    Status: Investigating 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. Affected components Agents (Degraded performance)

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

    Status: Investigating 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. Affected components Agents (Degraded performance)

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

    Status: Monitoring 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 Affected components Canvas (Degraded performance) Agents (Degraded performance)

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

    Status: Resolved 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 Affected components Canvas (Operational) Agents (Operational)

Read the full incident report →

Minor April 20, 2026

Creation of new chatbots and forms results in an error

Detected by Pingoru
Apr 20, 2026, 06:57 PM UTC
Resolved
Apr 20, 2026, 06:57 PM UTC
Duration
Affected: FormsChatbots
Timeline · 3 updates
  1. identified Apr 20, 2026, 06:14 PM UTC

    Status: Identified 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. Affected components Forms (Degraded performance) Chatbots (Degraded performance)

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

    Status: Monitoring 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 Affected components Forms (Degraded performance) Chatbots (Degraded performance)

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

    Status: Resolved 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. Affected components Forms (Operational) Chatbots (Operational)

Read the full incident report →

Minor April 20, 2026

Web-scraped sources cannot be added to Chatbots, and Agents not returning informatio

Detected by Pingoru
Apr 20, 2026, 01:05 AM UTC
Resolved
Apr 20, 2026, 01:05 AM UTC
Duration
Affected: AgentsChatbots
Timeline · 3 updates
  1. investigating Apr 19, 2026, 11:10 PM UTC

    Status: Investigating 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 Affected components Chatbots (Degraded performance) Agents (Degraded performance)

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

    Status: Monitoring 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. Affected components Chatbots (Degraded performance) Agents (Degraded performance)

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

    Status: Resolved 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 Affected components Chatbots (Operational) Agents (Operational)

Read the full incident report →

Minor April 17, 2026

Zap Run History Export Download Links Returning Errors

Detected by Pingoru
Apr 17, 2026, 10:51 PM UTC
Resolved
Apr 17, 2026, 10:51 PM UTC
Duration
Timeline · 5 updates
  1. identified Apr 16, 2026, 08:04 PM UTC

    Status: Identified 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

    Status: Resolved 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

    Status: Investigating 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

    Status: Monitoring 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

    Status: Resolved 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 →

Minor April 16, 2026

Temporary Agent run executions errors during a 15-minute window

Detected by Pingoru
Apr 16, 2026, 02:28 PM UTC
Resolved
Apr 16, 2026, 02:28 PM UTC
Duration
Affected: Agents
Timeline · 2 updates
  1. monitoring Apr 16, 2026, 02:08 PM UTC

    Status: Monitoring 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. Affected components Agents (Degraded performance)

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

    Status: Resolved 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. Affected components Agents (Operational)

Read the full incident report →

Minor April 15, 2026

404 Errors while editing templates

Detected by Pingoru
Apr 15, 2026, 11:38 PM UTC
Resolved
Apr 15, 2026, 11:38 PM UTC
Duration
Timeline · 2 updates
  1. investigating Apr 15, 2026, 09:52 PM UTC

    Status: Investigating 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

    Status: Resolved 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 →

Minor April 14, 2026

Slack Triggerred Zaps: Delays in triggering

Detected by Pingoru
Apr 14, 2026, 09:09 PM UTC
Resolved
Apr 14, 2026, 09:09 PM UTC
Duration
Timeline · 2 updates
  1. investigating Apr 14, 2026, 12:50 PM UTC

    Status: Investigating 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

    Status: Resolved 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 →

Minor April 8, 2026

Copilots "Ask" mode is not working correctly

Detected by Pingoru
Apr 08, 2026, 07:33 PM UTC
Resolved
Apr 08, 2026, 07:33 PM UTC
Duration
Affected: Copilot
Timeline · 3 updates
  1. investigating Apr 08, 2026, 05:27 PM UTC

    Status: Investigating 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. Affected components Copilot (Degraded performance)

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

    Status: Monitoring 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. Affected components Copilot (Degraded performance)

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

    Status: Resolved 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. Affected components Copilot (Operational)

Read the full incident report →

Minor April 8, 2026

Errors related to Custom Actions and Code by Zapier steps

Detected by Pingoru
Apr 08, 2026, 05:46 PM UTC
Resolved
Apr 08, 2026, 05:46 PM UTC
Duration
Timeline · 3 updates
  1. investigating Apr 08, 2026, 04:08 PM UTC

    Status: Investigating We're currently investigating an issue affecting custom actions. Services may be unavailable or experiencing delays. We'll provide updates as we learn more.

  2. investigating Apr 08, 2026, 04:13 PM UTC

    Status: Investigating We have discovered the issue may appear in Code by Zapier steps as well, and are continuing to investigate the root cause.

  3. resolved Apr 08, 2026, 05:46 PM UTC

    Status: Resolved We've identified and resolved the soft timeout limit errors that were impacting Code by Zapier and Custom Action steps. This issue was affecting the execution and processing of these steps across multiple Zaps. All affected runs have been automatically replayed. If you experienced any issues or need additional support, please feel free to reach out at https://zapier.com/app/get-help

Read the full incident report →

Minor April 7, 2026

Intermittent agent execution failures

Detected by Pingoru
Apr 07, 2026, 03:31 AM UTC
Resolved
Apr 07, 2026, 03:31 AM UTC
Duration
Affected: Agents
Timeline · 2 updates
  1. monitoring Apr 07, 2026, 02:10 AM UTC

    Status: Monitoring We are currently monitoring an issue affecting agent executions. Between April 6, 2026, at 22:12 UTC and 22:47 UTC, one of our services that powers Agents became unavailable due to internal load test traffic, which prevented agents from executing properly during this approximately 35-minute window. During this time, agents that were triggered experienced failures and were unable to complete. We are monitoring the underlying issue, and the service is now operating normally. We are continuing to investigate the full scope of impact and will provide additional updates as we gather more information. We sincerely apologize for any disruption this may have caused. Affected components Agents (Degraded performance)

  2. resolved Apr 07, 2026, 03:31 AM UTC

    Status: Resolved This issue has been resolved, and agent executions are operating normally. Between April 6, 2026, at 22:12 UTC and 22:47 UTC, a dependency that powers Agents became unavailable due to internal load test traffic. Agents triggered during this window may have failed to execute and will not be automatically retried. Agents that run from a Zap have been replayed and succeeded as well. If an agent run failed during this window, re-run the agent (or trigger it again via its normal trigger mechanism). New executions should now succeed. We apologize for the disruption. If you’re still seeing the issue, please refresh and try again, or contact Support at https://zapier.com/app/get-help. Affected components Agents (Operational)

Read the full incident report →

Minor April 7, 2026

Delayed or failed custom action requests

Detected by Pingoru
Apr 07, 2026, 01:43 AM UTC
Resolved
Apr 07, 2026, 01:43 AM UTC
Duration
Timeline · 2 updates
  1. monitoring Apr 07, 2026, 01:29 AM UTC

    Status: Monitoring Impact: Some customers may have seen failed or delayed workflow runs for a short period while we addressed a service issue. What happened: A brief spike in internal traffic put strain on systems that support authentication and request handling for certain workflow actions. That led to errors or slowdowns for workflows using those paths. Current status: The issue is resolved. Contributing factors have been addressed, capacity has been adjusted, and services are operating normally. We’ve worked through recovery steps for affected work, with checks showing things completing as expected. What you may have experienced: If your Zaps use custom actions, you might have seen failures or delays during the incident window. Affected work has been replayed or recovered where applicable.

  2. resolved Apr 07, 2026, 01:43 AM UTC

    Status: Resolved The incident affecting some custom action steps has been resolved. Between 22:12 and 22:47 UTC on April 6, 2026, some customers experienced failed or delayed workflow executions when using custom actions. Systems are stable and we’ve successfully replayed impacted Zap runs. Thanks for your patience.

Read the full incident report →

Minor April 6, 2026

Functions not executing

Detected by Pingoru
Apr 06, 2026, 11:16 PM UTC
Resolved
Apr 06, 2026, 11:16 PM UTC
Duration
Affected: Functions
Timeline · 2 updates
  1. investigating Apr 06, 2026, 08:12 PM UTC

    Status: Investigating We are investigating an issue affecting Zapier Functions. Started: Approximately 19:15 UTC on April 6, 2026 (2:15 PM Central). What we’re seeing: Triggers are being received as expected, but Functions are not running. In the product, you may notice that Functions do not appear to fire and there are no new entries in Functions run history for affected activity. We’re working to confirm scope and restore normal execution. We’ll post updates here as we learn more. Affected components Functions (Degraded performance)

  2. resolved Apr 06, 2026, 11:16 PM UTC

    Status: Resolved We've identified and resolved the root cause of the functions outage. The issue has been resolved and systems are operating normally. The team will continue to monitor performance and ensure full recovery across all impacted users. Affected components Functions (Operational)

Read the full incident report →

Minor April 4, 2026

Update PostgreSQL from version 14 to 17.

Detected by Pingoru
Apr 04, 2026, 04:16 PM UTC
Resolved
Apr 04, 2026, 04:16 PM UTC
Duration
Affected: Functions
Timeline · 2 updates
  1. monitoring Apr 04, 2026, 04:13 PM UTC

    Status: Monitoring No customer impact identified Affected components Functions (Degraded performance)

  2. resolved Apr 04, 2026, 04:16 PM UTC

    Status: Resolved resolved Affected components Functions (Operational)

Read the full incident report →

Minor April 3, 2026

Facebook Lead Ads and Microsoft apps are returning 'Cache key will cause errors if used with memcached' errors when creating new connections

Detected by Pingoru
Apr 03, 2026, 11:12 AM UTC
Resolved
Apr 03, 2026, 11:12 AM UTC
Duration
Timeline · 2 updates
  1. investigating Apr 03, 2026, 10:07 AM UTC

    Status: Investigating We are investigating 'Cache key will cause errors if used with memcached' errors when creating new connections to apps such as Facebook Lead Ads and Microsoft apps including Outlook and Teams

  2. resolved Apr 03, 2026, 11:12 AM UTC

    Status: Resolved Our team has resolved the issue, and connections can now be established again.

Read the full incident report →

Minor April 3, 2026

Zapier Agents - Webhook triggers showing a placeholder URL

Detected by Pingoru
Apr 03, 2026, 08:48 AM UTC
Resolved
Apr 03, 2026, 08:48 AM UTC
Duration
Affected: Agents
Timeline · 3 updates
  1. investigating Apr 03, 2026, 08:18 AM UTC

    Status: Investigating Customers attempting to create a new agent with a webhook trigger, or viewing the relevant agent creation page, saw a placeholder URL instead of the real webhook URL. We will provide updates as we learn more. Thank you for your patience. Affected components Agents (Degraded performance)

  2. monitoring Apr 03, 2026, 08:39 AM UTC

    Status: Monitoring We have deployed a fix to resolve the error and are continuing to actively monitor the situation. 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. Affected components Agents (Degraded performance)

  3. resolved Apr 03, 2026, 08:48 AM UTC

    Status: Resolved This is now resolved. Affected components Agents (Operational)

Read the full incident report →

Minor April 2, 2026

Zapier Agents - Adding a knowledge source modal is stuck on a loading spinner

Detected by Pingoru
Apr 02, 2026, 11:57 AM UTC
Resolved
Apr 02, 2026, 11:57 AM UTC
Duration
Affected: Agents
Timeline · 4 updates
  1. investigating Apr 02, 2026, 10:32 AM UTC

    Status: Investigating Selecting certain apps as a knowledge source in Zapier Agents causes the modal to hang indefinitely with a loading spinner, blocking users from adding those sources. Current Impact: Customers are unable to add certain knowledge sources in Zapier Agents, as the modal gets stuck on a loading spinner. Affected components Agents (Degraded performance)

  2. monitoring Apr 02, 2026, 10:49 AM UTC

    Status: Monitoring Root cause identified. We'll be reverting a recent deployment. Which should fix the issue. Affected components Agents (Degraded performance)

  3. identified Apr 02, 2026, 11:10 AM UTC

    Status: Identified Root cause identified. We'll be reverting a recent deployment. Which should fix the issue. (Edited to reflect the correct current status) Affected components Agents (Degraded performance)

  4. resolved Apr 02, 2026, 11:57 AM UTC

    Status: Resolved We’ve resolved an issue where adding certain knowledge sources in Zapier Agents could get stuck on a loading spinner. A fix has been deployed to production and verified. If you’re still seeing the issue, please refresh and try again, or contact Support at https://zapier.com/app/get-help Affected components Agents (Operational)

Read the full incident report →

Minor March 31, 2026

Internal Server Errors (HTTP 500) affecting Zaps

Detected by Pingoru
Mar 31, 2026, 04:48 PM UTC
Resolved
Mar 31, 2026, 04:48 PM UTC
Duration
Affected: Zap Editor
Timeline · 4 updates
  1. investigating Mar 31, 2026, 02:23 PM UTC

    Status: Investigating We are currently investigating intermittent Internal Server Errors (HTTP 500) affecting Zaps. Some customers may experience errors when editing their Zaps, and we understand how disruptive this is to your workflows. Our engineering teams are actively working to identify and resolve the root cause. We will provide updates as we learn more. Thank you for your patience.

  2. identified Mar 31, 2026, 02:58 PM UTC

    Status: Identified We’ve identified the cause of intermittent Internal Server Errors (HTTP 500) affecting some Enterprise customers when editing Zaps that use app approvals. This can prevent changes from being saved during editing. Our investigation indicates the errors occur when the Zap editor attempts to retrieve approval rules from our approvals service. Our engineering teams are actively working to restore full reliability. Next update within 30 minutes, or sooner if we have a mitigation. Affected components Zap Editor (Degraded performance)

  3. monitoring Mar 31, 2026, 03:29 PM UTC

    Status: Monitoring We’ve implemented a fix for the intermittent Internal Server Errors (HTTP 500) affecting some Enterprise customers when editing Zaps that use app approvals. We’re now monitoring the situation closely to confirm the issue is fully resolved and will share another update if we see any further impact. If you have any questions, reach out to our Support team - https://zapier.com/app/get-help Affected components Zap Editor (Degraded performance)

  4. resolved Mar 31, 2026, 04:48 PM UTC

    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)

Read the full incident report →

Looking to track Zapier downtime and outages?

Pingoru polls Zapier's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Zapier reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Zapier alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Zapier for free

5 free monitors · No credit card required