Zapier Outage History

Started Apr 08, 2026, 04:08 PM UTC· resolved Apr 08, 2026, 05:46 PM UTC

1. investigating Apr 08, 2026, 04:08 PM UTC

   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

   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

   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 →

Started Apr 07, 2026, 02:10 AM UTC· resolved Apr 07, 2026, 03:31 AM UTC

1. monitoring Apr 07, 2026, 02:10 AM UTC

   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.

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

   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.

Read the full incident report →

Started Apr 07, 2026, 01:29 AM UTC· resolved Apr 07, 2026, 01:43 AM UTC

1. monitoring Apr 07, 2026, 01:29 AM UTC

   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

   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 →

Started Apr 06, 2026, 08:12 PM UTC· resolved Apr 06, 2026, 11:16 PM UTC

1. investigating Apr 06, 2026, 08:12 PM UTC

   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.

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

   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.

Read the full incident report →

Started Apr 04, 2026, 04:13 PM UTC· resolved Apr 04, 2026, 04:16 PM UTC

1. monitoring Apr 04, 2026, 04:13 PM UTC

   No customer impact identified

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

   resolved

Read the full incident report →

Started Apr 03, 2026, 10:07 AM UTC· resolved Apr 03, 2026, 11:12 AM UTC

1. investigating Apr 03, 2026, 10:07 AM UTC

   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

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

Read the full incident report →

Started Apr 03, 2026, 08:18 AM UTC· resolved Apr 03, 2026, 08:48 AM UTC

1. investigating Apr 03, 2026, 08:18 AM UTC

   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.

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

   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.

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

   This is now resolved.

Read the full incident report →

Started Apr 02, 2026, 10:32 AM UTC· resolved Apr 02, 2026, 11:57 AM UTC

1. investigating Apr 02, 2026, 10:32 AM UTC

   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.

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

   Root cause identified. We'll be reverting a recent deployment. Which should fix the issue.

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

   Root cause identified. We'll be reverting a recent deployment. Which should fix the issue. (Edited to reflect the correct current status)

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

   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

Read the full incident report →

Started Mar 31, 2026, 02:23 PM UTC· resolved Mar 31, 2026, 04:48 PM UTC

1. investigating Mar 31, 2026, 02:23 PM UTC

   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

   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.

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

   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

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

   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

Read the full incident report →

Started Mar 30, 2026, 01:35 PM UTC· resolved Mar 30, 2026, 05:51 PM UTC

1. identified Mar 30, 2026, 01:35 PM UTC

   A previous incident on March 18 "previous incident on March 18": https://status.zapier.com/incidents/01KKZAYF71JFXMX65DDWC33PXP caused Zaps using Google Sheets and Google Drive to pause. While that incident was resolved, some affected Zaps were not restored and remain paused. If your Google Sheets or Google Drive Zaps are currently paused, you will need to turn them back on manually. You can check for affected Zaps directly using this filtered view of your paused Google Sheets and Google Docs Zaps "this filtered view of your paused Google Sheets and Google Docs Zaps": https://zapier.com/app/assets/zaps?app=GoogleSheetsV2CLIAPI%2CGoogleDocsV2CLIAPI&status=off. Look for Zaps that were paused between March 18 and March 19, 2026 and turn on any that should be active. If your Zaps missed data while they were paused, you can import the missing records using Transfer existing data using a spreadsheet "Transfer existing data using a spreadsheet": https://help.zapier.com/hc/en-us/articles/21695863326861-Transfer-existing-data-using-a-spreadsheet. If you need help or have questions, contact our support team at https://zapier.com/app/get-help.

2. resolved Mar 30, 2026, 05:51 PM UTC

   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

Read the full incident report →

Started Mar 28, 2026, 03:20 PM UTC· resolved Mar 28, 2026, 04:05 PM UTC

1. investigating Mar 28, 2026, 03:20 PM UTC

   TLDR: A production upgrade for Monolithdb from version 8.0.40 to 8.4.8 is currently in progress

2. resolved Mar 28, 2026, 04:05 PM UTC

   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

Read the full incident report →

Started Mar 26, 2026, 04:33 PM UTC· resolved Mar 26, 2026, 05:42 PM UTC

1. identified Mar 26, 2026, 04:33 PM UTC

   We‘re investigating intermittent task failures affecting some Zaps that occurred between March 24 and March 26, 2026. We have identified the root cause as exhausted database connections in our developercli service and have deployed a fix. What happened: Between March 24 at 11:02 AM UTC and March 26 at 2:04 PM UTC, some tasks failed intermittently due to exhaustion of the database connection pool. This affected a subset of customer Zaps, though the majority of our platform remained operational. Current status: The underlying issue has been resolved. We‘re currently replaying affected tasks to ensure they complete successfully. Most tasks with auto-replay enabled are being automatically reprocessed. What you may have experienced: If you use developercli-dependent Zaps, you may have seen task failures during this window. We apologize for any disruption this caused to your workflows. Next steps: We‘re completing task replays and will provide a full update once all affected tasks have been reprocessed. We do not expect any further issues. Thank you for your patience as we work through this issue. If you have any questions, please reach out to our support team - zapier.com/app/get-help "zapier.com/app/get-help": http://zapier.com/app/get-help.

2. resolved Mar 26, 2026, 05:42 PM UTC

   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

Read the full incident report →

Started Mar 24, 2026, 05:41 PM UTC· resolved Mar 25, 2026, 04:29 PM UTC

1. investigating Mar 24, 2026, 05:41 PM UTC

   We’re investigating an issue impacting a subset of customers where payments may fail during checkout, subscription renewals, or plan changes. Customers may see a generic “unable to process payment” error and invoices may remain unpaid due to repeated failed attempts. If you are seeing this error, re-adding your payment method should resolve the issue and allow you to checkout. Our team is working to resolve this error internally as well. If you have any questions feel free to reach out to our support team. - zapier.com/app/get-help "zapier.com/app/get-help": http://zapier.com/app/get-help.

2. identified Mar 24, 2026, 06:52 PM UTC

   Starting on March 24th at 2:00am UTC an issue began impacting some customers where payments may fail during checkout, subscription renewals, or plan changes. Customers may see a generic “unable to process payment” error and invoices may remain unpaid due to repeated failed attempts. If you are seeing this error, re-adding your payment method should resolve the issue and allow you to checkout. We are also emailing all users directly who are affected. If you have any questions feel free to reach out to our support team. - zapier.com/app/get-help "zapier.com/app/get-help": http://zapier.com/app/get-help.

3. identified Mar 24, 2026, 09:26 PM UTC

   An issue was discovered affecting some customer accounts that resulted in payment methods being removed from our systems. Customers may see a "payment failed" error during checkout, subscription renewals, or plan changes. If you received an email from us about needing to add a new payment method, your account was affected by this issue. If you received this email or are seeing payment errors, re-adding your payment method in your billing settings should resolve the issue and allow your account to process payments normally. We are also emailing all users directly who are affected. If you have any questions feel free to reach out to our support team. - zapier.com/app/get-help "zapier.com/app/get-help": http://zapier.com/app/get-help.

4. monitoring Mar 25, 2026, 05:50 AM UTC

   We're continuing to monitor the situation with payment methods that were unintentionally removed from our systems. Our team has worked to reinstate the payment methods for affected customers, and payment processing has resumed for many accounts. We're currently verifying that all affected customers can process payments successfully. You may still need to re-add their payment information if you encounter issues during checkout or renewal. We're actively investigating any remaining cases and will provide updates as we learn more. If you're unable to complete a payment or renew your subscription, please visit your billing settings to add or update your payment method: https://help.zapier.com/hc/en-us/articles/8496294350093-View-and-update-your-billing-information. If you see any further issues, please reach out to our support team at https://zapier.com/app/get-help. We apologize for the inconvenience and appreciate your patience as we work through this.

5. resolved Mar 25, 2026, 04:29 PM UTC

   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

Read the full incident report →

Started Mar 24, 2026, 03:51 PM UTC· resolved Mar 25, 2026, 03:35 AM UTC

1. monitoring Mar 24, 2026, 03:51 PM UTC

   We're aware of public reports regarding a supply chain issue affecting specific LiteLLM package versions published to PyPI. Out of caution, we reviewed our environments and confirmed that the LiteLLM versions deployed by Zapier are not among the affected versions reported publicly. At this time, we have no evidence of impact to customer data, Zapier systems, or services. We also confirmed that no automated systems could upgrade to the affected versions and found no other related deployments in our environment. We will continue monitoring the situation and will share updates if anything changes. If you have any questions, please reach out to our support team - zapier.com/app/get-help "zapier.com/app/get-help": http://zapier.com/app/get-help.

2. resolved Mar 25, 2026, 03:35 AM UTC

   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.

Read the full incident report →

Started Mar 24, 2026, 12:44 PM UTC· resolved Mar 24, 2026, 01:24 PM UTC

1. investigating Mar 24, 2026, 12:44 PM UTC

   We’re investigating an issue where some users are unable to add or remove tools on Zapier MCP servers. Affected users may see a message prompting them to “switch to the account that owns the server” and may be disconnected after authentication. Our team has identified and reproduced the issue and is actively working on a fix. We’ll share another update as we learn more.

2. monitoring Mar 24, 2026, 01:00 PM UTC

   We’ve identified the cause of the issue preventing some users from adding or removing tools on Zapier MCP servers, and we have a fix in progress. We’ll continue monitoring and will provide another update once we’ve confirmed full recovery. If you have any other questions on this in the meantime, please reach out to our Support team at https://zapier.com/get-help.

3. resolved Mar 24, 2026, 01:24 PM UTC

   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

Read the full incident report →

Started Mar 18, 2026, 09:32 PM UTC· resolved Mar 18, 2026, 11:09 PM UTC

1. investigating Mar 18, 2026, 09:32 PM UTC

   We're currently investigating an issue where users are seeing a blank OAuth Authorization page on zapier.com "zapier.com": http://zapier.com and when attempting to create new connections. We will provide an updated status by 2:30 PM PST

2. investigating Mar 18, 2026, 10:11 PM UTC

   We’re continuing to investigate the issue where users are seeing a blank OAuth Authorization page on zapier.com "zapier.com": http://zapier.com and when attempting to create new connections. Our team is actively prioritizing this issue and will share updates as soon as we have more information.

3. monitoring Mar 18, 2026, 10:28 PM UTC

   We have implemented a fix for the issue causing a blank OAuth Authorization page on zapier.com "zapier.com": http://zapier.com and when creating new connections. As of March 18, 2026 at 22:17:52 UTC, we believe the issue to be resolved, and we are continuing to monitor to ensure stability.

4. resolved Mar 18, 2026, 11:09 PM UTC

   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

Read the full incident report →

Started Mar 18, 2026, 02:03 AM UTC· resolved Mar 18, 2026, 03:59 PM UTC

1. identified Mar 18, 2026, 02:03 AM UTC

   We have identified the cause of an ongoing issue affecting Google integrations, including Google Sheets, with some impact to Google Drive and Google Docs. Users may experience intermittent connection or authentication errors, which can result in failed Zap runs or workflows not triggering as expected. In some cases, Zap runs may be delayed or temporarily held. Our team is actively working on mitigation to restore stability. We are seeing early signs of improvement, but some users may continue to experience intermittent issues while mitigation efforts are ongoing. We appreciate your patience as we continue to resolve this issue. We’ll provide further updates as progress continues.

2. monitoring Mar 18, 2026, 03:22 AM UTC

   We previously saw connection failures for Google Sheets, Google Docs, and Google Drive integrations, which caused some Zaps using these apps to stop running as expected. We have applied a fix, and authentication error rates are now significantly decreasing. There was no data loss, but some Zaps may have missed runs during the impact windows, particularly in high-volume workflows. Zaps using these Google apps should now be running normally again and picking up new data. We are also currently replaying any Zap runs that were held during the incident. We’re monitoring the fix closely, and if you notice any ongoing issues, please contact Support: https://zapier.com/app/get-help

3. resolved Mar 18, 2026, 11:09 AM UTC

   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. During the incident window, some workflows using these Google integrations may have failed to run, and some triggers may have missed events (especially high-volume workflows). There was no data loss. We rolled back the affected Google integrations to their last stable versions and replayed held tasks for impacted users. 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://help.zapier.com/hc/en-us/articles/8496274335885-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.

4. resolved Mar 18, 2026, 03:59 PM UTC

   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.

Read the full incident report →

Started Mar 17, 2026, 11:55 PM UTC· resolved Mar 18, 2026, 05:03 AM UTC

1. investigating Mar 17, 2026, 11:55 PM UTC

   We are currently investigating delays affecting the display of Zap run history, and errors on the Zap Usage page. You may be seeing a delay in loading times on both pages. Zap executions are running normally and completing as expected. We appreciate your patience as we work through this issue. We'll provide updates as the situation progresses.

2. resolved Mar 18, 2026, 05:03 AM UTC

   The Zap History and Task Usage pages are now loading normally again. During this incident, you may have experienced slow load times, intermittent errors, or missing data on the Zap History and Task Usage pages. Zap executions were not affected and continued to run as expected throughout. This issue is now considered resolved, and we are continuing to monitor to ensure stability. If you're still seeing delays or errors on these pages, we recommend clearing your browser's cache and cookies and logging back into Zapier. For any other issues or questions, please reach out to our support team at https://zapier.com/app/get-help.

Read the full incident report →

Started Mar 17, 2026, 01:39 PM UTC· resolved Mar 18, 2026, 05:15 PM UTC

1. investigating Mar 17, 2026, 01:39 PM UTC

   We are currently investigating delays affecting the display of Zap run history. You may be seeing a delay in your runs showing up in your Zap history at this time. Zap executions are running normally and completing as expected, but there may be a delay of up to several minutes before runs appear in your Zap history view. We appreciate your patience as we work through this issue. We'll provide updates as the situation progresses.

2. monitoring Mar 17, 2026, 02:54 PM UTC

   We are seeing the recovery of our Zap history indexing system following a period of elevated load. The immediate impact has been resolved, and new Zap runs are now appearing in your history with normal latency. We will continue to update as new information is available.

3. resolved Mar 18, 2026, 05:15 PM UTC

   This issue has now been resolved, and all Zap runs should now be appearing correctly in the Zap history without delay. 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

Read the full incident report →

Started Mar 13, 2026, 04:50 PM UTC· resolved Mar 13, 2026, 05:11 PM UTC

1. investigating Mar 13, 2026, 04:50 PM UTC

   We’re currently investigating an issue affecting checkout where the payment and tax modals may not appear correctly. Self-serve customers who need to add or update payment or tax information during checkout may be unable to complete checkout. Workaround: If you can’t add a card during checkout, you can add a payment method from the billing settings page and then return to checkout. We’ll share another update as soon as we have more information.

2. resolved Mar 13, 2026, 05:11 PM UTC

   The checkout page payment and tax modals are now functioning normally again. During this incident, you may have been unable to add or update payment or tax information during checkout. If you still have trouble updating payment or tax details, you can update your payment method from the billing settings page and then return to checkout. We apologize for the disruption and appreciate your patience as we got this resolved. If you do see any further issues, please reach out to our support team at https://zapier.com/app/get-help

Read the full incident report →

Started Mar 11, 2026, 06:55 PM UTC· resolved Mar 11, 2026, 07:29 PM UTC

1. identified Mar 11, 2026, 06:55 PM UTC

   Our Engineering team is aware of reports of users receiving "Copilot isn't responding right now" or "Connection refused" errors and are deploying a fix for the issue. We will continue to monitor for any abnormal responses as we roll out a fix.

2. monitoring Mar 11, 2026, 07:10 PM UTC

   Our Engineering team has deployed a fix for the issue, and we're starting to see a decrease in Copilot errors across the platform. We'll continue to monitor the issue for any sudden spike and will share an update once we see normal performance.

3. resolved Mar 11, 2026, 07:29 PM UTC

   We're seeing error levels back to a normal level with no spikes over the last 20 minutes. As such, this issue is now considered resolved. If you still see the error messages, we recommend clearing Copilot chat by selecting the Settings icon at the top of the Copilot chat window. If that does not work, clear your browser's cookies and cache and then log back into Zapier. For any other issues or questions, please reach out to our support team at https://zapier.com/app/get-help

Read the full incident report →

Started Mar 05, 2026, 08:30 PM UTC· resolved Mar 05, 2026, 10:50 PM UTC

1. investigating Mar 05, 2026, 08:30 PM UTC

   We are investigating reports of increased errors and actions not functioning for customers utilizing Zapier MCP alongside Claude CoWork. Our Engineering team is working to identify and resolve the issue. If you're affected by this, please reach out to our Support team at zapier.com/get-help "zapier.com/get-help": http://zapier.com/get-help

2. monitoring Mar 05, 2026, 10:19 PM UTC

   We are continuing to monitor reports affecting customers using Zapier MCP with Claude CoWork. We are working with Anthropic to share our findings to help fix this issue. If you're affected by this and need assistance, please reach out to our Support team at https://zapier.com/get-help.

3. resolved Mar 05, 2026, 10:50 PM UTC

   Our Engineering team has decided to close this incident, as the root cause appears to be Claude's handling of MCP tool calls with Cowork. We have notified the Anthropic team of the issue and will continue working with their Support and Engineering teams to help resolve it. If you're still running into issues or have questions, we recommend reaching out to Anthropic support by using this Help Center guide: https://support.claude.com/en/articles/9015913-how-to-get-support

Read the full incident report →

Started Mar 03, 2026, 09:57 PM UTC· resolved Mar 03, 2026, 10:29 PM UTC

1. investigating Mar 03, 2026, 09:57 PM UTC

   We are aware of reports that new app connections can't be created when using OAuth. Users will see a 404 error or a blank page when trying to authorize new app connections that require OAuth. Existing app connections are not affected. We'll keep you updated as we work to resolve the issue. If you find yourself impacted, please reach out to our Support team at zapier.com/get-help "zapier.com/get-help": http://zapier.com/get-help

2. monitoring Mar 03, 2026, 10:07 PM UTC

   Our Engineering team identified the issue and has released a fix. We have seen a decline in the amount of errors but will continue to monitor for any spikes in errors or other issues that may arise as the fix is released. If you find yourself affected, please let us know by opening a ticket at zapier.com/get-help "zapier.com/get-help": http://zapier.com/get-help

3. resolved Mar 03, 2026, 10:29 PM UTC

   Thank you for your patience as we worked to resolve the issue. We're no longer seeing elevated error rates when customers create app connections, and we can confirm that customers can create new app connections without issue. This issue is now considered resolved, but feel free to reach out to our Support team if you have questions: https://zapier.com/app/get-help

Read the full incident report →

Started Feb 26, 2026, 05:24 PM UTC· resolved Feb 26, 2026, 10:26 PM UTC

1. investigating Feb 26, 2026, 05:24 PM UTC

   Our Engineering team is investigating an issue with several app integrations which could potentially cause some trigger and few action events to execute with a delay, or not execute. The team has been working on mitigating actions, and we'll be updating the status page as soon as we learn more. Many thanks for your patience. Feel free to reach out if you have any questions at: zapier.com/get-help: http://zapier.com/get-help

2. monitoring Feb 26, 2026, 06:49 PM UTC

   Our Engineering team has successfully mitigated the error rate for affected integrations. Optimizations have been implemented to handle errors in execution, and the affected app integrations are now operating at normal levels. We will continue to monitor error rates in real-time and will take additional action if needed. Thank you for your patience while we worked on this! If you need help or have any questions, please reach out to our Support team at: zapier.com/get-help.

3. resolved Feb 26, 2026, 10:26 PM UTC

   Our team has restored full functionality and verified system performance is stable. Since there's full functionality, the incident is considered closed. Affected customers have been contacted but no further action is necessary. If you have any other questions, please feel free to reach out to our support team at https://zapier.com/app/get-help

Read the full incident report →

Started Feb 26, 2026, 03:13 PM UTC· resolved Feb 27, 2026, 08:13 PM UTC

1. investigating Feb 26, 2026, 03:13 PM UTC

   Our team is currently investigating an issue where Zaps using Notion triggers stopped triggering approximately 3 hours ago. We're currently seeing improvement and starting to receive hooks from Notion again, and we're working together with our Partners to restore the Zaps back to normal. Many thanks for your patience, and feel free to reach us at zapier.com/get-help "zapier.com/get-help": http://zapier.com/get-help if you have any questions!

2. monitoring Feb 26, 2026, 03:33 PM UTC

   Our Engineering team has worked together with our Partners at Notion and identified the root cause. From 2026-02-25 21:07 To 2026-02-26 09:51 EST, Zaps using Notion triggers stopped triggering, or triggered intermittently due to a temporary error. At this stage, all Zaps using Notion triggers are back to normal. We will continue to monitor trigger activity and update this status page to confirm resolution. For any questions, please reach out support team at: zapier.com/get-help "zapier.com/get-help": http://zapier.com/get-help.

3. investigating Feb 27, 2026, 04:10 PM UTC

   We are investigating an issue impacting Zaps that use Notion webhook-based triggers. Between 2026-02-25 21:07 EST and 2026-02-26 09:51 EST, Zapier did not receive webhook events from Notion. As a result, Zaps relying on Notion webhook triggers may not have fired during this window. Webhook delivery from Notion has resumed, and we are receiving events again at normal levels. We recommend reviewing whether any business-critical Notion events occurred during the affected window that you expected to trigger an automation. If needed, you may re-run the intended action by retriggering the underlying event in Notion. We are actively working with Notion to better understand the underlying cause, and will share more information as it becomes available. If you need assistance reviewing your workflows, please contact Support: https://zapier.com/get-help

4. resolved Feb 27, 2026, 08:09 PM UTC

   This issue is not resolved. Zaps that using Airtable as a trigger should now be receiving all webhooks and triggering properly. If you are still running into into issues, please reach out to Zapier Support: https://zapier.com/get-help

5. resolved Feb 27, 2026, 08:13 PM UTC

   This issue is now resolved. Zaps that using Notion as a trigger should now be receiving all webhooks and triggering properly. If you are still running into into issues, please reach out to Zapier Support: https://zapier.com/get-help

Read the full incident report →