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 March 30, 2026

Zaps Paused due Prior Connection Failure with Google Services

Detected by Pingoru
Mar 30, 2026, 05:51 PM UTC
Resolved
Mar 30, 2026, 05:51 PM UTC
Duration
—
Timeline · 2 updates
  1. identified Mar 30, 2026, 01:35 PM UTC

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

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

Minor March 28, 2026

Database Upgrade

Detected by Pingoru
Mar 28, 2026, 04:05 PM UTC
Resolved
Mar 28, 2026, 04:05 PM UTC
Duration
—
Timeline · 2 updates
  1. investigating Mar 28, 2026, 03:20 PM UTC

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

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

Minor March 26, 2026

Intermittent failures across tasks due to exhausted db connections for developercli

Detected by Pingoru
Mar 26, 2026, 05:42 PM UTC
Resolved
Mar 26, 2026, 05:42 PM UTC
Duration
—
Affected: Zap History
Timeline · 2 updates
  1. identified Mar 26, 2026, 04:33 PM UTC

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

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

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

Read the full incident report →

Minor March 25, 2026

Payment failures for some customers

Detected by Pingoru
Mar 25, 2026, 04:29 PM UTC
Resolved
Mar 25, 2026, 04:29 PM UTC
Duration
—
Timeline · 5 updates
  1. investigating Mar 24, 2026, 05:41 PM UTC

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

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

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

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

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

Minor March 25, 2026

Monitoring a publicly reported LiteLLM package issue

Detected by Pingoru
Mar 25, 2026, 03:35 AM UTC
Resolved
Mar 25, 2026, 03:35 AM UTC
Duration
—
Timeline · 2 updates
  1. monitoring Mar 24, 2026, 03:51 PM UTC

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

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

Minor March 24, 2026

MCP Servers: Issues adding/removing tools

Detected by Pingoru
Mar 24, 2026, 01:24 PM UTC
Resolved
Mar 24, 2026, 01:24 PM UTC
Duration
—
Affected: MCP
Timeline · 3 updates
  1. investigating Mar 24, 2026, 12:44 PM UTC

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

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

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

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

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

Read the full incident report →

Minor March 18, 2026

OAuth Authorization Page Is Blank

Detected by Pingoru
Mar 18, 2026, 11:09 PM UTC
Resolved
Mar 18, 2026, 11:09 PM UTC
Duration
—
Affected: Website
Timeline · 4 updates
  1. investigating Mar 18, 2026, 09:32 PM UTC

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

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

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

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

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

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

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

Read the full incident report →

Minor March 18, 2026

Delay in Zap History displaying Zap Runs

Detected by Pingoru
Mar 18, 2026, 05:15 PM UTC
Resolved
Mar 18, 2026, 05:15 PM UTC
Duration
—
Timeline · 3 updates
  1. investigating Mar 17, 2026, 01:39 PM UTC

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

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

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

Minor March 18, 2026

Connection Failure with Google Services

Detected by Pingoru
Mar 18, 2026, 03:59 PM UTC
Resolved
Mar 18, 2026, 03:59 PM UTC
Duration
—
Affected: Agents
Timeline · 4 updates
  1. identified Mar 18, 2026, 02:03 AM UTC

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

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

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

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

Read the full incident report →

Minor March 18, 2026

Delay in loading Zap History and Task Usage

Detected by Pingoru
Mar 18, 2026, 05:03 AM UTC
Resolved
Mar 18, 2026, 05:03 AM UTC
Duration
—
Timeline · 2 updates
  1. investigating Mar 17, 2026, 11:55 PM UTC

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

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

Minor March 13, 2026

Checkout page not rendering properly

Detected by Pingoru
Mar 13, 2026, 05:11 PM UTC
Resolved
Mar 13, 2026, 05:11 PM UTC
Duration
—
Timeline · 2 updates
  1. investigating Mar 13, 2026, 04:50 PM UTC

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

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

Minor March 11, 2026

Copilot intermittently not responding in the Editor

Detected by Pingoru
Mar 11, 2026, 07:29 PM UTC
Resolved
Mar 11, 2026, 07:29 PM UTC
Duration
—
Timeline · 3 updates
  1. identified Mar 11, 2026, 06:55 PM UTC

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

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

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

Minor March 5, 2026

Degraded Performance for Zapier MCP in Claude CoWork

Detected by Pingoru
Mar 05, 2026, 10:50 PM UTC
Resolved
Mar 05, 2026, 10:50 PM UTC
Duration
—
Affected: MCP
Timeline · 3 updates
  1. investigating Mar 05, 2026, 08:30 PM UTC

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

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

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

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

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

Read the full incident report →

Minor March 3, 2026

Users are not able to create new app connections using OAuth flow

Detected by Pingoru
Mar 03, 2026, 10:29 PM UTC
Resolved
Mar 03, 2026, 10:29 PM UTC
Duration
—
Timeline · 3 updates
  1. investigating Mar 03, 2026, 09:57 PM UTC

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

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

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

Minor February 27, 2026

Zaps using notion triggers stopped triggering

Detected by Pingoru
Feb 27, 2026, 08:13 PM UTC
Resolved
Feb 27, 2026, 08:13 PM UTC
Duration
—
Timeline · 5 updates
  1. investigating Feb 26, 2026, 03:13 PM UTC

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

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

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

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

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

Minor February 26, 2026

Some app integrations experiencing delayed triggers sporadically

Detected by Pingoru
Feb 26, 2026, 10:26 PM UTC
Resolved
Feb 26, 2026, 10:26 PM UTC
Duration
—
Affected: Polling TriggersSearches & Writes
Timeline · 3 updates
  1. investigating Feb 26, 2026, 05:24 PM UTC

    Status: Investigating 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 Affected components Searches & Writes (Degraded performance) Polling Triggers (Degraded performance)

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

    Status: Monitoring 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. Affected components Searches & Writes (Operational) Polling Triggers (Operational)

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

    Status: Resolved 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 Affected components Searches & Writes (Operational) Polling Triggers (Operational)

Read the full incident report →

Minor February 25, 2026

Task Usage Page Currently Unavailable

Detected by Pingoru
Feb 25, 2026, 05:56 PM UTC
Resolved
Feb 25, 2026, 05:56 PM UTC
Duration
—
Timeline · 3 updates
  1. investigating Feb 25, 2026, 03:58 PM UTC

    Status: Investigating We’re currently investigating an issue affecting the Task Usage page. At the moment, some customers may not be able to view their task usage data in the UI. Our engineering team is actively working to resolve this and restore visibility to the Task Usage page as quickly as possible. We’ll continue to share updates as soon as we have more information. If you have any questions, reach out to our support team here: https://zapier.com/app/get-help

  2. monitoring Feb 25, 2026, 04:32 PM UTC

    Status: Monitoring The issue affecting the Task Usage page has been resolved. Customers should now be able to view task usage data in the UI as expected. We appreciate your patience while our team worked to restore full visibility. Please reach out to support if you continue to experience any issues.

  3. resolved Feb 25, 2026, 05:56 PM UTC

    Status: Resolved This issue is now resolved, and the Task Usage Page should now be loading correctly for all users. If you are running into any other issues, please reach back out to Zapier Support: https://zapier.com/app/get-help

Read the full incident report →

Minor February 24, 2026

AI by Zapier steps in Zaps with transcribe action running into an error

Detected by Pingoru
Feb 24, 2026, 04:07 AM UTC
Resolved
Feb 24, 2026, 04:07 AM UTC
Duration
—
Timeline · 3 updates
  1. investigating Feb 24, 2026, 02:52 AM UTC

    Status: Investigating We're currently investigating an issue affecting the Transcribe action in AI by Zapier. Users who use this action see "Failed to process document with AI: fetch failed" error message. Our engineering team is actively investigating the root cause. We will provide updates as soon as we have more information. If you need help, please contact Support: https://zapier.com/app/get-help

  2. monitoring Feb 24, 2026, 03:18 AM UTC

    Status: Monitoring Between approximately 10:00PM UTC on Feb 23 and 3:20 AM UTC on February 24, users experienced errors when using the Transcribe action in AI by Zapier. The action returned the error "Failed to process document with AI: fetch failed" in both test and live runs. A fix has been implemented, and this action is running successfully again. We're now attempting to replay the errored runs that happened during this period. We will continue monitoring and post a final update within 24 hours. If anything seems off, contact Support by clicking above or go to: https://zapier.com/app/get-help

  3. resolved Feb 24, 2026, 04:07 AM UTC

    Status: Resolved Between approximately 10:00PM UTC on Feb 23 and 3:20 AM UTC on February 24, we saw errors being returned from the Transcribe cation in AI by Zapier. The team were able to identify and roll-back the change causing this issue and the issue should now be resolved. If you run into any unexpected errors, please feel free to reach out to us at: https://zapier.com/app/get-help

Read the full incident report →

Minor February 21, 2026

Airtable Authentication Expiring

Detected by Pingoru
Feb 21, 2026, 06:47 PM UTC
Resolved
Feb 21, 2026, 06:47 PM UTC
Duration
—
Timeline · 3 updates
  1. identified Feb 20, 2026, 07:51 PM UTC

    Status: Identified Airtable is currently running into an incident which is causing downstream effects within Zapier. Airtable triggers are currently seeing slight delays and authentication errors. You can follow their status page for updates: https://status.airtable.com/ If you have any questions, feel free to reach out to our support team. https://zapier.com/app/get-help

  2. identified Feb 21, 2026, 12:55 AM UTC

    Status: Identified We’re continuing to monitor an ongoing incident on Airtable’s end that is causing downstream effects within Zapier. At this time, Airtable triggers may still experience slight delays and intermittent authentication errors. We’re awaiting full resolution from Airtable before moving on to next steps. For the latest updates, please refer to Airtable’s status page: https://status.airtable.com/ If you have any questions, feel free to reach out to our support team. https://zapier.com/app/get-help

  3. resolved Feb 21, 2026, 06:47 PM UTC

    Status: Resolved On February 20, 2026, between 1:44 PM and 8:27 PM EST, an Airtable outage caused authentication errors and trigger delays for customers using Airtable integrations through Zapier. Affected Airtable authentications were marked as inactive, resulting in errors and delays for impacted automations. The Zapier platform remained fully operational throughout. Airtable's services have since fully recovered. If you are still experiencing issues with your Airtable connections, please visit the Zapier Connections page to reconnect Airtable, and check your Zap History to replay any affected runs.

Read the full incident report →

Minor February 13, 2026

Upstream errors with Airtable authentications

Detected by Pingoru
Feb 13, 2026, 03:44 PM UTC
Resolved
Feb 13, 2026, 03:44 PM UTC
Duration
—
Timeline · 3 updates
  1. monitoring Feb 13, 2026, 08:03 AM UTC

    Status: Monitoring Some users encountered authentication issues due to an upstream issue at Airtable: https://status.airtable.com/incidents/3b5b6xxwpcb5 We are now seeing users are able to reconnect and we are monitoring to ensure this is resolved and investigating the impact and duration of the issue.

  2. monitoring Feb 13, 2026, 10:02 AM UTC

    Status: Monitoring Authentication issues appear to be resolved now, our current focus is on measuring and mitigating the impact of this on related Zaps What we’ve done • Restored all affected authentications automatically. • Replayed failed action steps. (Automatic replays are underway) • Replayed polling attempts to capture delayed trigger events. (Automatic replays are underway) • Confirmed that Airtable integrations are now functioning normally. • Validated that error rates have returned to baseline.

  3. resolved Feb 13, 2026, 03:44 PM UTC

    Status: Resolved We are pleased to confirm that this incident has been resolved. All Airtable Zaps and connections are back to normal. Impacted customers have now received an email with a timeline of events, actions taken, and next steps (if any). If you have any questions or need assistance, please reach out to our Support team at: https://zapier.com/app/get-help.

Read the full incident report →

Minor February 12, 2026

Change History Not Displaying

Detected by Pingoru
Feb 12, 2026, 06:19 PM UTC
Resolved
Feb 12, 2026, 06:19 PM UTC
Duration
—
Affected: Website
Timeline · 2 updates
  1. investigating Feb 12, 2026, 06:02 PM UTC

    Status: Investigating We are currently investigating an issue affecting the Change History feature in the editor. Users may be unable to view the change history in the left editor sidebar. We will provide updates as we learn more. Thank you for your patience. Affected components Website (Degraded performance)

  2. resolved Feb 12, 2026, 06:19 PM UTC

    Status: Resolved This issue has been resolved. Between 14:42 and 18:00 UTC on February 12, some users were unable to view the Change History panel in the editor. All systems are now operating normally. If you experienced issues during this time, please refresh your browser. Need help? Contact Support: https://zapier.com/app/get-help Affected components Website (Operational)

Read the full incident report →

Minor February 12, 2026

AI Features Degraded — Chatbots & Agents

Detected by Pingoru
Feb 12, 2026, 05:55 PM UTC
Resolved
Feb 12, 2026, 05:55 PM UTC
Duration
—
Affected: AgentsChatbots
Timeline · 3 updates
  1. investigating Feb 12, 2026, 03:37 PM UTC

    Status: Investigating Investigating We’re looking into an issue that’s causing timeouts for some AI features in Zapier. Impact (what users may see) • Chatbots: Errors when adding or using table-based knowledge sources; attempts may fail with an on-screen error. • AI Agents: Adding a new data source may fail with “trouble loading your knowledge source.” Running Agents that already use knowledge sources may work intermittently (some runs succeed, others fail). What we’re doing We’re putting a temporary workaround in place that automatically switches to a backup service so these features can keep working while we address the underlying issue. Next update We’ll share updates as we make progress. Please contact our support team for assistance. https://zapier.com/app/get-help Affected components Chatbots (Degraded performance) Agents (Degraded performance)

  2. monitoring Feb 12, 2026, 04:00 PM UTC

    Status: Monitoring We’ve implemented a fix. Agents and Chatbots can now sync and add table-based knowledge sources, and functionality is returning to normal. We’re watching closely to ensure everything remains stable and will post a final update once monitoring is complete. Need help? Contact Support: https://zapier.com/app/get-help Affected components Agents (Degraded performance) Chatbots (Degraded performance)

  3. resolved Feb 12, 2026, 05:55 PM UTC

    Status: Resolved This incident has been resolved as of 2026-02-12T15:38:00 UTC. Agents and Chatbots can now successfully add and sync table-based knowledge sources. If you encountered errors during the incident, please re-add and sync your knowledge sources. Need help? Contact Support: https://zapier.com/app/get-help Affected components Chatbots (Operational) Agents (Operational)

Read the full incident report →

Minor February 10, 2026

Facebook Custom Audiences integration retuns an deprecated API error

Detected by Pingoru
Feb 10, 2026, 11:06 PM UTC
Resolved
Feb 10, 2026, 11:06 PM UTC
Duration
—
Timeline · 3 updates
  1. investigating Feb 10, 2026, 08:47 PM UTC

    Status: Investigating We are aware that customers are encountering the following error message during Zap runs and when loading sample records. "Unable to get selected custom audience. (#2635 "#2635": https://zapier.zendesk.com/agent/tickets/2635) You are calling a deprecated version of the Ads API. Please upgrade to the latest version: v23.0" We'll continue to provide updates as our teams work to resolve the issue.

  2. monitoring Feb 10, 2026, 10:29 PM UTC

    Status: Monitoring Monitoring — Facebook Custom Audiences Integration We have successfully deployed a fix for the Facebook Custom Audiences integration issue and are currently monitoring the results. What happened: Our integration was calling a deprecated version of the Facebook Ads API (v22), which is no longer supported. This was preventing some requests from completing successfully. What we did: We identified the issue and upgraded the integration to the latest supported API version (v23). Current status: The fix has been deployed and we are actively monitoring to ensure all functionality is restored and stable. Errors have subsided and users are no longer affected. We will provide an update once monitoring confirms full stability. Thank you for your patience.

  3. resolved Feb 10, 2026, 11:06 PM UTC

    Status: Resolved Resolved — Facebook Custom Audiences Integration The Facebook Custom Audiences integration issue has been fully resolved. What happened: Our integration was calling a deprecated version of the Facebook Ads API (v22), which is no longer supported. This prevented some requests from completing successfully. What we did:*We identified the issue and upgraded the integration to the latest supported API version (v23). We confirmed the update and rolled it out to all affected users. We also replayed failed runs to ensure they completed successfully. Current status: All functionality has been restored and the integration is operating normally. All affected users are back to full service. If you have any questions or experience any issues, please reach out to our support team: https://zapier.com/app/get-help

Read the full incident report →

Minor February 10, 2026

Copilot may show errors or become non-responsive when adding action to a Zap.

Detected by Pingoru
Feb 10, 2026, 07:11 PM UTC
Resolved
Feb 10, 2026, 07:11 PM UTC
Duration
—
Timeline · 3 updates
  1. investigating Feb 10, 2026, 06:48 PM UTC

    Status: Investigating We have received reports that Copilot shows errors and appears unresponsive when trying to add actions to a Zap in its chat window. However, Copilot continues to run in the background despite the errors in chat. Copilot can still be used to create Zaps at this time without issue. We're investigating the root cause of the issue and will give an update as soon as possible.

  2. monitoring Feb 10, 2026, 06:57 PM UTC

    Status: Monitoring Our Engineering teams have pushed out a fix for the issue, and we're currently monitoring our backend logs to ensure we're seeing a reduction in errors. You may need to refresh the page if you're still seeing Copilot errors or if it's unresponsive while adding actions to a Zap. If you have questions, please don't hesitate to reach out to our Support team at https://zapier.com/app/get-help

  3. resolved Feb 10, 2026, 07:11 PM UTC

    Status: Resolved Our Engineering teams have pushed out a fix for the issue, and we have confirmed this has resolved the issues with Copilot. You may need to refresh the page if you're still seeing Copilot errors or if it's unresponsive while adding actions to a Zap. If you have questions, please don't hesitate to reach out to our Support team at https://zapier.com/app/get-help

Read the full incident report →

Minor February 4, 2026

LinkedIn Ads - All Triggers - Missing Webhooks

Detected by Pingoru
Feb 04, 2026, 12:37 AM UTC
Resolved
Feb 04, 2026, 12:37 AM UTC
Duration
—
Timeline · 11 updates
  1. investigating Jan 28, 2026, 10:07 AM UTC

    Status: Investigating We are currently investigating an issue affecting the LinkedIn Ads "New Lead Gen Form Response (Sponsored content)" trigger. Customers using this trigger are experiencing delays or failures in their Zaps firing as expected. What's happening: The webhook notifications that power this trigger are not being received, which prevents connected Zaps from executing automatically. What we're doing: Our integrations engineering team is actively investigating the root cause. We've confirmed the issue is isolated to this specific trigger and have ruled out common account-level issues through standard troubleshooting steps. Current impact: Multiple customers have reported this issue. We're working to understand the full scope and timeline for resolution. Next steps: We'll provide an update as soon as we have more information about the cause and expected resolution time. Thank you for your patience as we work through this. For support, please reach out to our team and reference incident INC-670.

  2. investigating Jan 28, 2026, 11:20 AM UTC

    Status: Investigating Update: Our team has confirmed this is an upstream issue originating from LinkedIn's side. We have notified LinkedIn's support team and are actively monitoring the situation while awaiting their response.

  3. investigating Jan 28, 2026, 11:33 AM UTC

    Status: Investigating Update: Our team has confirmed this is an upstream issue originating from LinkedIn's side, affecting all LinkedIn Ads triggers. We will provide further updates as soon as possible. For support, please reach out to our team and reference incident INC-670.

  4. identified Jan 28, 2026, 12:19 PM UTC

    Status: Identified We’re investigating an issue where LinkedIn Ads instant triggers are not receiving webhook events from LinkedIn. As a result, Zaps using LinkedIn Ads triggers are not running, and new leads will not be captured until this is resolved. Our team has identified this as an upstream issue with LinkedIn and has engaged LinkedIn Developer Support. There’s no action required on your end at this time. We’ll share another update as soon as we have more information. Start time: January 27, 2026 at 8:21 UTC

  5. monitoring Jan 28, 2026, 05:31 PM UTC

    Status: Monitoring Our team is monitoring the upstream issue with LinkedIn. Our team continues to work with LinkedIn's Developer Support team to help identify the root cause of the issue. If you have questions about this incident, please feel free to reach out to our Support team: https://zapier.com/app/get-help

  6. monitoring Jan 28, 2026, 09:50 PM UTC

    Status: Monitoring Our team continues to monitor issues with LinkedIn Ads triggers not receiving events. We will keep you up to date as we work alongside LinkedIn's Developer Support team to resolve the issue.

  7. monitoring Jan 28, 2026, 11:11 PM UTC

    Status: Monitoring LinkedIn's teams are still working to resolve the upstream issue where LinkedIn Ad instant triggers are not receiving triggers. We hope to have an additional update when US business hours resume tomorrow.

  8. monitoring Jan 29, 2026, 10:58 AM UTC

    Status: Monitoring LinkedIn has resumed sending webhook events to Zapier for LinkedIn Ads instant triggers. We’re continuing to work with LinkedIn to help identify the root cause of the issue and will share another update once we have confirmation. If you have questions about this incident, please feel free to reach out to our Support team: https://zapier.com/app/get-help

  9. monitoring Jan 29, 2026, 10:09 PM UTC

    Status: Monitoring Service has been restored as of 22:00 UTC Jan 29th. The outage started at 2026-01-27 07:30 UTC / 2026-01-27 02:30 EST, and service was fully restored at 2026-01-29 02:00 UTC / 2026-01-28 21:00 EST. We’re continuing to work with LinkedIn to help their team replay any webhook events that were missed during the outage. This status page will continue to be updated until we get word that the events have been replayed from the LinkedIn team. If you have questions about this incident, please feel free to reach out to our Support team: https://zapier.com/app/get-help

  10. monitoring Jan 30, 2026, 03:20 PM UTC

    Status: Monitoring We’re continuing to work with LinkedIn to help their team replay any webhook events that were missed during the outage. This status page will continue to be updated until we get word that the events have been replayed from the LinkedIn team. If you don’t wish to have your webhooks replayed, you can add a filter to your Zap(s) to only continue if the "Form Submitted At" field is before Jan 27th, 8:21 UTC OR after Jan 29th 01:32 UTC. If you have questions about this incident, please feel free to reach out to our Support team: https://zapier.com/app/get-help

  11. resolved Feb 04, 2026, 12:37 AM UTC

    Status: Resolved We're happy to report that the LinkedIn team has successfully completed replaying the missed hooks for the New Lead Gen Form Response (Sponsored content) trigger that occurred during the incident window (Jan 27th, 8:21 UTC until Jan 29th, 01:32 UTC). If you have any questions or need assistance, please reach out to our Support team at https://zapier.com/app/get-help

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