Zapier Outage History

Zapier is up right now

Zapier had 103 outages in the last 2 years totaling 51m of downtime — averaging 4.2 incidents per month.

There were 103 Zapier outages since January 29, 2026 totaling 51m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.zapier.com

Minor October 5, 2026

Logging into Zapier using Facebook or Microsoft SSO shown a blank page after authentication.

Detected by Pingoru
Oct 05, 2026, 06:54 PM UTC
Resolved
Oct 05, 2026, 07:46 PM UTC
Duration
51m
Affected: Login
Timeline · 3 updates
  1. investigating Oct 05, 2026, 06:54 PM UTC

    Status: Investigating Our Engineering team is aware of an issue affecting users who sign into Zapier.com "Zapier.com": http://Zapier.com using Facebook or Microsoft Single Sign-On (SSO). Users logging into Zapier with these services will see a blank screen after authenticating. The login authentication is successful; however, the page can be accessed after a hard refresh or by opening a new tab. We are investigating the issue and will give another update as soon as we find the cause. Affected components Login (Partial outage)

  2. monitoring Oct 05, 2026, 07:42 PM UTC

    Status: Monitoring Our Engineering team has identified the issue and has released a fix. We're now monitoring our systems to see if there are any other problems that could result from the fix. Affected components Login (Partial outage)

  3. resolved Oct 05, 2026, 07:46 PM UTC

    Status: Resolved The issue is now considered resolved, with both Facebook and Microsoft single sign-on working as expected. If you find yourself still unable to log in, please reach out to our Support team at zapier.com/get-help "zapier.com/get-help": http://zapier.com/get-help Thank you for your patience as we worked to resolve the issue. Affected components Login (Operational)

Read the full incident report →

Minor September 28, 2026

Azure DevOps connections failing: expired OAuth client secret (AADSTS7000222)

Detected by Pingoru
Sep 28, 2026, 01:18 PM UTC
Resolved
Sep 28, 2026, 01:18 PM UTC
Duration
—
Affected: Instant TriggersPolling Triggers
Timeline · 3 updates
  1. investigating Sep 28, 2026, 12:13 PM UTC

    Status: Investigating Azure DevOps connections are failing because the OAuth client secret has expired. We have identified the issue, and we are currently investigating this further. Only Zaps using the Azure DevOps connection are affected. Affected components Instant Triggers (Degraded performance) Polling Triggers (Degraded performance)

  2. monitoring Sep 28, 2026, 12:40 PM UTC

    Status: Monitoring We have found and resolved the issue affecting the connection. If the connection still shows expired, manually testing the connection should restore it. Affected components Polling Triggers (Operational) Instant Triggers (Operational)

  3. resolved Sep 28, 2026, 01:18 PM UTC

    Status: Resolved This has been fully resolved. If you still face this issue, please reach out to our support team via the Get help and support with Zapie "Get help and support with Zapie": https://help.zapier.com/hc/en-us/articles/8496213764877-Get-help-and-support-with-Zapierr channels Affected components Instant Triggers (Operational) Polling Triggers (Operational)

Read the full incident report →

Minor September 9, 2026

Zap History not displaying Zap runs

Detected by Pingoru
Sep 09, 2026, 07:41 PM UTC
Resolved
Sep 09, 2026, 07:41 PM UTC
Duration
—
Affected: Zap History
Timeline · 4 updates
  1. investigating Sep 09, 2026, 05:51 PM UTC

    Status: Investigating We're currently experiencing an issue where the Zap History page is not displaying recent Zap runs happening from today, September 9, 2026 starting at approximately 12:39PM EST. Zap runs are still processing normally, but can't be accessed or reviewed at the moment. We're actively investigating and will continue to update this status page with our progress. Many thanks for your patience! If you have any questions, please contact our Support team at: zapier.com/get-help. Affected components Zap History (Partial outage)

  2. identified Sep 09, 2026, 06:14 PM UTC

    Status: Identified We've identified the root cause for Zap runs not displaying in the Zap History, and our Engineering team is working on a resolution. Zap runs are slowly appearing again in the Zap history, and we'll confirm once all Zap runs can be accessed. For any questions, please reach out to our Support team at: zapier.com/get-help. Affected components Zap History (Partial outage)

  3. monitoring Sep 09, 2026, 06:59 PM UTC

    Status: Monitoring The Engineering team has implemented a fix for this issue, and Zap runs continue to load into the Zap History. Executions have not been affected: Zap runs are executing normally. However, the Zap run data was not rendering in the Zap history correctly. We appreciate your patience while we worked through this, and we will share a final update once all Zap runs are displaying successfully. If you have questions or need help, please contact our Support team at: zapier.com/get-help. Affected components Zap History (Partial outage)

  4. resolved Sep 09, 2026, 07:41 PM UTC

    Status: Resolved We have implemented a fix regarding Zap history runs not showing, so they should be available in your Zap history page now. If you have questions or need help, please contact our Support team at: zapier.com/get-help "zapier.com/get-help": http://zapier.com/get-help. Affected components Zap History (Operational)

Read the full incident report →

Minor September 8, 2026

Webhook Triggers and Zap Actions - Service Disruption

Detected by Pingoru
Sep 08, 2026, 05:08 PM UTC
Resolved
Sep 08, 2026, 05:08 PM UTC
Duration
—
Affected: Instant TriggersSearches & Writes
Timeline · 2 updates
  1. monitoring Sep 08, 2026, 02:06 PM UTC

    Status: Monitoring A brief infrastructure issue between approximately 8:15–9:50 AM ET caused some Zap workflows using webhook triggers to not fire, and some Zap action steps to fail. The issue has been resolved, and Zap Runs are processing normally. We're reviewing affected accounts and replaying missed webhook events where possible. If you notice a Zap that should have run during this window and did not, contact Support: zapier.com/app/get-help "zapier.com/app/get-help": http://zapier.com/app/get-help Affected components Instant Triggers (Degraded performance) Searches & Writes (Degraded performance)

  2. resolved Sep 08, 2026, 05:08 PM UTC

    Status: Resolved The issue causing some Zap workflows to not trigger from webhooks or fail on action steps between approximately 8:15–9:50 AM ET has been resolved. If you're still seeing issues with a Zap that should have run during this window, contact Support: zapier.com/app/get-help "zapier.com/app/get-help": http://zapier.com/app/get-help Affected components Instant Triggers (Operational) Searches & Writes (Operational)

Read the full incident report →

Minor September 7, 2026

Freshservice - Webhook delivery disruption

Detected by Pingoru
Sep 07, 2026, 12:44 PM UTC
Resolved
Sep 07, 2026, 12:44 PM UTC
Duration
—
Timeline · 5 updates
  1. investigating Sep 01, 2026, 12:03 PM UTC

    Status: Investigating Customers using Freshservice webhook triggers may not receive new updates in their Zaps. We are investigating the disruption with Freshservice and will share further information as it becomes available.

  2. investigating Sep 03, 2026, 02:16 PM UTC

    Status: Investigating We are still investigating the disruption with Freshservice and have touched base with their team to continue digging into this. We will continue to share further information as it becomes available. We appreciate your patience while our team works on this.

  3. investigating Sep 03, 2026, 09:39 PM UTC

    Status: Investigating We’re still investigating the disruption with Freshdesk. If you are experiencing issues related to this, please reach out here: https://zapier.com/app/get-help

  4. investigating Sep 04, 2026, 07:08 PM UTC

    Status: Investigating The Freshservice disruption is still under investigation. The Freshservice team has confirmed the issue and is working to implement a fix. We’ll provide the next update once we know more. If you’re experiencing this issue, please reach out to our Support team: https://zapier.com/app/get-help

  5. resolved Sep 07, 2026, 12:44 PM UTC

    Status: Resolved Freshservice webhook triggers are now delivering to Zapier again following a fix deployed by Freshservice. We’ve confirmed incoming webhook activity has resumed and are continuing to monitor volumes. If you experience ongoing issues, contact Support by clicking above or go to: https://zapier.com/app/get-help Thank you for your patience.

Read the full incident report →

Minor August 28, 2026

Tables, Chatbots, and Forms not loading for some customers

Detected by Pingoru
Aug 28, 2026, 03:35 PM UTC
Resolved
Aug 28, 2026, 03:35 PM UTC
Duration
—
Affected: FormsChatbotsTables
Timeline · 3 updates
  1. investigating Aug 28, 2026, 02:35 PM UTC

    Status: Investigating We're currently investigating an issue affecting Tables, Chatbots, and Forms for some users. Affected users may find that existing Tables, Chatbots, or Forms are not loading and are instead being redirected to a creation page. If you need help in the meantime, contact Support: https://zapier.com/app/get-help Affected components Tables (Degraded performance) Forms (Degraded performance) Chatbots (Degraded performance)

  2. monitoring Aug 28, 2026, 03:01 PM UTC

    Status: Monitoring A fix has been implemented for the issue affecting Tables, Chatbots, and Forms. These should now be loading as expected for affected users. We are continuing to monitor to confirm full stability. We will post a final update within 24 hours. If anything still seems off, contact Support: https://zapier.com/app/get-help Affected components Tables (Degraded performance) Forms (Degraded performance) Chatbots (Degraded performance)

  3. resolved Aug 28, 2026, 03:35 PM UTC

    Status: Resolved The issue affecting Tables, Chatbots, and Forms has been resolved as of approximately 15:00 UTC. Some users were unable to load existing Tables, Chatbots, or Forms and were redirected to a creation page instead. All affected surfaces — Tables, Forms, Chatbots, and folder/subfolder creation — have been verified and are working normally. No data loss occurred, and Zap runs were not affected. If you're still experiencing issues, contact Support: https://zapier.com/app/get-help Thank you for your patience. Affected components Tables (Operational) Forms (Operational) Chatbots (Operational)

Read the full incident report →

Minor August 26, 2026

Intermittent instant trigger failures

Detected by Pingoru
Aug 26, 2026, 09:41 PM UTC
Resolved
Aug 26, 2026, 09:41 PM UTC
Duration
—
Affected: Instant Triggers
Timeline · 4 updates
  1. investigating Aug 26, 2026, 04:55 PM UTC

    Status: Investigating Some customers may experience intermittent delays or failures with instant triggers, which can prevent workflows from starting. We are investigating the issue and working to restore normal processing. We will provide updates as soon as possible. Affected components Instant Triggers (Degraded performance)

  2. investigating Aug 26, 2026, 05:24 PM UTC

    Status: Investigating We're continuing to investigate a small number of workflows that failed to start between approximately 9:00–9:20 AM UTC on August 25. Affected triggers did not fire during this window. No data has been lost — failed triggers can be replayed once the issue is resolved. Our team is actively working to determine the root cause. We'll provide another update as soon as possible. If you need help: https://zapier.com/app/get-help Affected components Instant Triggers (Degraded performance)

  3. monitoring Aug 26, 2026, 06:59 PM UTC

    Status: Monitoring A fix has been implemented and we are monitoring the results. We have not seen any new instant trigger failures since approximately 10:26 AM PDT (17:26 UTC). The change we deployed adds automatic retries for the failure that was preventing a small number of triggers from firing, and we are continuing to roll it out fully. No data has been lost. We have confirmed that affected triggers replay successfully, and we are now replaying the triggers that failed during this incident. Our team is monitoring closely to confirm the issue is fully resolved. If you have any questions, please reach out to our support team: https://zapier.com/app/get-help Thank you for your patience. Affected components Instant Triggers (Degraded performance)

  4. resolved Aug 26, 2026, 09:41 PM UTC

    Status: Resolved Instant trigger processing has returned to normal. We have successfully replayed the affected triggers and continue not to see any impacted Zap runs, so the incident is now resolved. If you have any questions, please reach out to our support team: [https://zapier.com/app/get-help](https://zapier.com/app/get-help) Affected components Instant Triggers (Operational)

Read the full incident report →

Minor August 22, 2026

403 errors when trying to connect or reconnect to ActiveCampaign

Detected by Pingoru
Aug 22, 2026, 02:19 AM UTC
Resolved
Aug 22, 2026, 02:19 AM UTC
Duration
—
Timeline · 3 updates
  1. investigating Aug 21, 2026, 11:48 PM UTC

    Status: Investigating We have reports that users who try to create new app connections or reconnect existing ones for ActiveCampaign receive a 403 error. This causes the connection to fail. Our Engineering team is looking into the issue and will follow up as soon as we learn more. If you're unable to log in, please open a case with our Support team at https://zapier.com/app/get-help so we can continue to keep you up-to-date.

  2. monitoring Aug 22, 2026, 01:45 AM UTC

    Status: Monitoring The issue with ActiveCampaign app connections returning a 403 error has been resolved. Authentication and integration are now functioning normally, and Zap runs using ActiveCampaign aren't impacted by this going forward. Our team is currently investigating which Zap runs were affected during the incident and will provide further updates as needed. Thank you for your patience and we appreciate you bearing with us as we worked through this. If you continue to experience any issues, please reach out to our Support team at https://zapier.com/app/get-help.

  3. resolved Aug 22, 2026, 02:19 AM UTC

    Status: Resolved The issue with ActiveCampaign app connections and runs returning a 403 error has been fully resolved. Authentication and integration are functioning normally again. Impacted runs during the incident period have been replayed successfully. If you're experiencing any issues, please reach out to our Support team through this link: https://zapier.com/app/get-help.

Read the full incident report →

Minor August 19, 2026

Errors related to Pipedrive invalid IDs

Detected by Pingoru
Aug 19, 2026, 07:36 PM UTC
Resolved
Aug 19, 2026, 07:36 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating Aug 19, 2026, 04:07 PM UTC

    Status: Investigating We are investigating reports of invalid ID errors related to Pipedrive triggers/actions. If you are running into this issue, please reach out to us at https://zapier.com/app/get-help

  2. monitoring Aug 19, 2026, 04:39 PM UTC

    Status: Monitoring Errors/issue related to Pipedrive invalid IDs are recovering, and we'll continue to monitor this. If you're still encountering this issue, please reach out to us at https://zapier.com/app/get-help

  3. investigating Aug 19, 2026, 04:45 PM UTC

    Status: Investigating We are investigating the affected Zaps regarding the invalid ID errors. If you are experiencing this issue or have any questions, please reach out to us at https://zapier.com/app/get-help

  4. resolved Aug 19, 2026, 07:36 PM UTC

    Status: Resolved Errors related to Pipedrive invalid IDs are resolved. If you have any further questions, please reach out to us: https://zapier.com/app/get-help

Read the full incident report →

Minor August 19, 2026

Sales Contact forms are not loading

Detected by Pingoru
Aug 19, 2026, 06:36 PM UTC
Resolved
Aug 19, 2026, 06:36 PM UTC
Duration
—
Affected: Website
Timeline · 4 updates
  1. investigating Aug 18, 2026, 05:21 PM UTC

    Status: Investigating We're currently investigating an issue where our Contact Sales "Contact Sales": https://zapier.com/l/contact-sales form on the homepage does not load. Our team is actively working on identifying and resolving the issue. In the meantime, if you would like to contact our Sales team, please submit a ticket through our Support team here: zapier.com/get-help "zapier.com/get-help": http://zapier.com/get-help, and we'll be happy to assist and/or route you to the appropriate team. Affected components Website (Degraded performance)

  2. identified Aug 18, 2026, 06:06 PM UTC

    Status: Identified Our Engineering team has observed increased traffic to our Contact Sales form, causing it to reach our vendor's rate limit and fail to load. We're continuing our work to resolve the issue, but if you need to contact our Sales team and are unable to load the form, please feel free to create a ticket with Support (https://zapier.com/l/contact-sales), and we'll route the ticket accordingly. Affected components Website (Degraded performance)

  3. monitoring Aug 18, 2026, 08:54 PM UTC

    Status: Monitoring We’ve deployed a fix for the issue that caused some Contact Sales forms "Contact Sales forms": https://zapier.com/l/contact-sales to fail to load. We’re monitoring the form closely to confirm the improvement holds. If you need to contact our Sales team and are unable to load the form, please feel free to create a ticket with Support (https://zapier.com/app/get-help), and we'll route the ticket accordingly. Affected components Website (Degraded performance)

  4. resolved Aug 19, 2026, 06:36 PM UTC

    Status: Resolved After monitoring traffic, we're seeing forms respond as expected. We now consider the issue resolved. Thank you for your patience as we worked to resolve the issue. Affected components Website (Operational)

Read the full incident report →

Minor August 18, 2026

Zapier Functions temporarily unavailable

Detected by Pingoru
Aug 18, 2026, 11:58 PM UTC
Resolved
Aug 18, 2026, 11:58 PM UTC
Duration
—
Affected: Functions
Timeline · 2 updates
  1. investigating Aug 18, 2026, 11:50 PM UTC

    Status: Investigating We're currently experiencing an issue affecting Zapier Functions. Users attempting to create, edit, or run Functions may encounter errors or be unable to access the service. Zaps and other Zapier services continue to operate normally. No data loss is expected. If you are currently migrating your Functions, you may experience disruptions until this issue is resolved. Our team is actively investigating and working to restore full functionality. If you need help, contact Support: [https://zapier.com/app/get-help](https://zapier.com/app/get-help) Affected components Functions (Partial outage)

  2. resolved Aug 18, 2026, 11:58 PM UTC

    Status: Resolved The issue affecting Zapier Functions has been resolved. Functions are now operating normally. During this incident, users were unable to create, edit, or run Functions. No data loss occurred. Zaps and other Zapier services were not affected during this time. If you are still experiencing issues, contact Support: https://zapier.com/app/get-help Thank you for your patience. Affected components Functions (Operational)

Read the full incident report →

Minor August 17, 2026

Contact Sales forms is down

Detected by Pingoru
Aug 17, 2026, 10:54 PM UTC
Resolved
Aug 17, 2026, 10:54 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating Aug 17, 2026, 08:49 PM UTC

    Status: Investigating We are currently investigating an issue where our Contact Sales form is not rendering correctly under https://zapier.com/l/contact-sales. Our team is actively working on resolving this issue. In the meantime, if you would like to contact our Sales team, please submit a ticket through our Support team here: zapier.com/get-help, and we'll be happy to assist and/or route you to the appropriate team.

  2. identified Aug 17, 2026, 09:16 PM UTC

    Status: Identified We have identified the issue causing our Contact Sales, event registration, and webinar registration forms to fail. A third-party form provider we use across our marketing site has hit a daily API limit, which is preventing new form submissions from going through. Impact is limited to marketing-site forms — signing in, creating Zaps, and running existing Zaps are not affected. We are working with the provider to restore submissions as quickly as possible. If you have any questions, please reach out to our support team: https://zapier.com/app/get-help Thank you for your patience.

  3. monitoring Aug 17, 2026, 10:39 PM UTC

    Status: Monitoring A fix has been implemented and we are monitoring the results. Our third-party form provider has temporarily raised our API limit, and Contact Sales, webinar/event registration, ZapConnect registration, and AI Leaders Lab forms are displaying and submitting successfully again. Signing in, creating Zaps, and running existing Zaps were not affected at any point during this incident. We are continuing to monitor form submissions and traffic levels to confirm the fix holds. If you have any questions, please reach out to our support team: https://zapier.com/app/get-help Thank you for your patience.

  4. resolved Aug 17, 2026, 10:54 PM UTC

    Status: Resolved This incident has been resolved. Submissions to our Contact Sales, webinar/event registration, ZapConnect registration, and AI Leaders Lab forms are working normally again. The issue was caused by our third-party form provider’s daily API limit being exhausted by internal Zapier traffic, which prevented these marketing-site forms from loading and submitting. The upstream limit has been raised, the internal traffic source has been stopped, and form submissions have been confirmed stable. Thanks again for your patience while we were working on resolving that, and if you have any questions, or are running into any other issues, please reach out to our support team: https://zapier.com/app/get-help

Read the full incident report →

Minor July 28, 2026

Close CRM integration: authentication issues

Detected by Pingoru
Jul 28, 2026, 02:43 PM UTC
Resolved
Jul 28, 2026, 02:43 PM UTC
Duration
—
Timeline · 2 updates
  1. identified Jul 28, 2026, 01:34 PM UTC

    Status: Identified We’re aware of an issue affecting the Close CRM integration where some customers may see errors when connecting or reconnecting their Close account in Zapier (for example, “invalid_client”). We’ve identified the failure point and are working with the relevant parties to restore normal authentication as quickly as possible. We’ll share another update as we learn more. If you’re impacted, please retry later. If the issue is urgent, contact Zapier Support at: https://zapier.com/app/get-help with a screenshot of the error.

  2. resolved Jul 28, 2026, 02:43 PM UTC

    Status: Resolved This issue affecting the Close CRM integration has been resolved. Customers should now be able to connect or reconnect their Close account in Zapier normally. We have also replayed impacted delayed/held Zap runs that were paused during the incident. If you’re still seeing errors connecting or reconnecting Close, please retry and contact Zapier Support at: https://zapier.com/app/get-help.

Read the full incident report →

Minor July 22, 2026

Quota exceeded errors on a subset of Zap runs using Google apps integrations

Detected by Pingoru
Jul 22, 2026, 08:38 PM UTC
Resolved
Jul 22, 2026, 08:38 PM UTC
Duration
—
Timeline · 2 updates
  1. monitoring Jul 22, 2026, 06:32 PM UTC

    Status: Monitoring We have confirmed that the Quota Exceeded errors from Google Drive also affected a small subset of Zap workflows using Google Sheets, Google Docs, Google Slides and Gmail actions. The Google Drive quota exceeded errors have been resolved (https://status.zapier.com/incidents/01KY534ZVKCPV90WN0B6BAY0WY). The majority of affected Google apps Zap runs have been replayed. We are currently monitoring error rates and confirming that all affected Zap runs have succeeded at this point. If you have any questions, please reach out to our Support team at zapier.com/get-help.

  2. resolved Jul 22, 2026, 08:38 PM UTC

    Status: Resolved We previously reported quota-exceeded errors affecting a subset of Zap workflows using Google Drive, Google Sheets, Google Docs, Google Slides, and Gmail actions. The underlying issue has been fixed. Affected Zap runs have been replayed, and workflows that were paused due to elevated errors have been restored. No further action is needed on your end. If a Zap run still shows as failed, you can replay it from your Zap history, or contact Support at zapier.com/get-help "zapier.com/get-help": http://zapier.com/get-help.

Read the full incident report →

Minor July 22, 2026

Elevated errors for Google Drive app integration

Detected by Pingoru
Jul 22, 2026, 05:50 PM UTC
Resolved
Jul 22, 2026, 05:50 PM UTC
Duration
—
Timeline · 3 updates
  1. identified Jul 22, 2026, 02:19 PM UTC

    Status: Identified Our Engineering has identified an issue with the Google Drive integration hitting intermittent 403 - Quota Exhausted errors across all actions. The team is working on implementing a fix. If you have any questions, please reach out to our Support team at zapier.com/get-help.

  2. monitoring Jul 22, 2026, 04:34 PM UTC

    Status: Monitoring Our Engineering implemented a fix by rolling back an update that caused the elevated errors. All Zap workflows using Google Drive actions will continue to execute correctly. Errored runs will be replayed automatically. We continue to monitor performance to confirm all error rates have returned back to baseline. If you have any questions, please reach out to our Support team at zapier.com/get-help.

  3. resolved Jul 22, 2026, 05:50 PM UTC

    Status: Resolved The rollback was successful, and the Google Drive quota errors have been resolved. All Google Drive actions are back to normal. Errored runs have been replayed automatically. Many thanks for your patience while we worked through this. If you have any questions, please reach out to our Support team at zapier.com/get-help: http://zapier.com/get-help.

Read the full incident report →

Minor July 13, 2026

Elevated authentication errors (401s) impacting multiple products

Detected by Pingoru
Jul 13, 2026, 05:38 PM UTC
Resolved
Jul 13, 2026, 05:38 PM UTC
Duration
—
Timeline · 3 updates
  1. investigating Jul 13, 2026, 01:33 PM UTC

    Status: Investigating We are investigating an issue causing elevated authentication failures (401s) across multiple Zapier products and services. Our engineering team is actively investigating, and we will provide another update as we learn more. If you need help, contact Support: https://zapier.com/app/get-help

  2. monitoring Jul 13, 2026, 02:22 PM UTC

    Status: Monitoring We applied a fix and are seeing authentication failures and related errors return to normal across affected Zapier products and services. We are continuing to monitor closely to ensure the recovery is sustained. If you need help, contact Support: https://zapier.com/app/get-help

  3. resolved Jul 13, 2026, 05:38 PM UTC

    Status: Resolved This incident has been resolved. Between approximately 8:00 AM and 9:15 AM CDT (13:00–14:15 UTC), customers may have experienced errors or degraded functionality across multiple Zapier products, including: AI by Zapier, Agents, Chatbots, Forms, Interfaces, Tables, account management, and Zap runs and related automation processing. The underlying issue has been fixed, systems are operating normally, and affected Zap runs and webhook events have been replayed. If you’re still seeing issues, try refreshing the page, logging out and back in, or retrying any failed actions or workflow runs. If you have any questions, or are running into any other issues, please reach out to our support team: https://zapier.com/app/get-help Thanks again for your patience while we were working on resolving that.

Read the full incident report →

Minor July 12, 2026

AI by Zapier

Detected by Pingoru
Jul 12, 2026, 01:26 AM UTC
Resolved
Jul 12, 2026, 01:26 AM UTC
Duration
—
Timeline · 3 updates
  1. investigating Jul 11, 2026, 10:10 PM UTC

    Status: Investigating Investigating — We are investigating an issue affecting AI by Zapier steps in Zaps, which is causing errors for some customers. Affected customers may encounter the following error: DriverAdapterError Our team has identified the issue and is actively working to restore service as quickly as possible. We will provide another update as soon as we have more information.

  2. monitoring Jul 11, 2026, 10:51 PM UTC

    Status: Monitoring Monitoring — A fix has been implemented, and we are seeing recovery across AI by Zapier. We are continuing to monitor the service closely to ensure stability. We will continue monitoring and provide another update once we have confirmed the issue is fully resolved.

  3. resolved Jul 12, 2026, 01:26 AM UTC

    Status: Resolved The issue impacting AI by Zapier has been mitigated and systems are back to normal. Impact window: Approximately 19:00–22:20 UTC on July 11. We have automatically replayed the affected runs to recover previously failed executions. If you have any remaining questions or are still seeing issues, please contact support at https://zapier.com/get-help.

Read the full incident report →

Minor July 8, 2026

Increased 4XX errors from Airtable

Detected by Pingoru
Jul 08, 2026, 08:57 PM UTC
Resolved
Jul 08, 2026, 08:57 PM UTC
Duration
—
Timeline · 3 updates
  1. investigating Jul 08, 2026, 08:08 PM UTC

    Status: Investigating We are noticing issues related to the Airtable integration. This might result in increased 4XX errors in Zaps or missed triggers. If you are running into these issues, please reach out to our support team here: https://zapier.com/app/get-help

  2. monitoring Jul 08, 2026, 08:28 PM UTC

    Status: Monitoring We’ve confirmed the trigger-side impact from the Airtable incident has healed, and are looking into replaying any missed triggers.

  3. resolved Jul 08, 2026, 08:57 PM UTC

    Status: Resolved Issues related to Airtable errors are resolved. Any missed triggers and/or actions are replayed. If you have any questions, you can always reach out to our support team here: https://zapier.com/app/get-help

Read the full incident report →

Minor July 8, 2026

Users who sign up for a Team trial are instead signed up for a Pro trial.

Detected by Pingoru
Jul 08, 2026, 12:08 AM UTC
Resolved
Jul 08, 2026, 12:08 AM UTC
Duration
—
Timeline · 5 updates
  1. investigating Jul 07, 2026, 05:03 PM UTC

    Status: Investigating We have reports that users who sign up for a Team trial are actually enrolled in a Pro trial. This means that Teams features are not available during the trial period. Our Engineering team is aware of the issue and is working to resolve it. We'll continue to give updates as we make progress.

  2. investigating Jul 07, 2026, 07:19 PM UTC

    Status: Investigating We’re aware an issue where some users who sign up for a Teams trial are instead enrolled in a Pro trial. As a result, Teams features may not be available during the trial period. Our engineering team is continuing to investigate this issue and is working to resolve it. We’ll share another update by 2:15pm PT / 21:15 UTC. If you're experiencing any other issues with your account please contact Support at https://zapier.com/app/get-help.

  3. investigating Jul 07, 2026, 09:35 PM UTC

    Status: Investigating We’re aware of an issue where some users who try to start a Teams trial from our pricing page are instead placed on a Pro trial, so Teams features may not be available during the trial. Our engineering team is investigating a fix to restore the correct Teams trial signup experience. We will provide the update by 4:15pm PT / 23:15 UTC. If you’re experiencing any other issues with your account, please contact Support at https://zapier.com/app/get-help.

  4. monitoring Jul 07, 2026, 10:53 PM UTC

    Status: Monitoring We've identified and applied a fix for the issue where users signing up for a Teams trial from our pricing page were instead being placed on a Pro trial. New signups should now correctly receive a Teams trial with full access to Teams features. If you're experiencing any other issues with your account, please contact Support at https://zapier.com/app/get-help.

  5. resolved Jul 08, 2026, 12:08 AM UTC

    Status: Resolved A fix has been deployed and we have confirmed no further failures since the rollout. Users signing up for a Teams trial from our pricing page should now receive a Teams trial with access to Teams features. This incident is resolved. If you're experiencing any other issues with your account, please contact Support at https://zapier.com/app/get-help.

Read the full incident report →

Minor July 2, 2026

Slack Find Message action is unable to find bot messages

Detected by Pingoru
Jul 02, 2026, 01:10 PM UTC
Resolved
Jul 02, 2026, 01:10 PM UTC
Duration
—
Affected: Searches & Writes
Timeline · 4 updates
  1. investigating Jun 30, 2026, 01:46 AM UTC

    Status: Investigating We are currently investigating an issue with the Slack "Find Message" action that is preventing it from finding bot messages in Slack channels. What's happening Our team has identified that the Slack Find Message action is failing to find bot messages, while searches for human messages continue to work normally. Customers attempting to search for bot messages are seeing errors like "Nothing could be found for the search" or the step finds the closest matching non-bot message. Current status We've confirmed this issue is reproducible and are actively investigating its root cause. We apologize for any disruption this may cause to your workflows while we investigate this issue. Affected components Searches & Writes (Degraded performance)

  2. investigating Jun 30, 2026, 02:30 AM UTC

    Status: Investigating We’re investigating the issue where the Slack “Find Message” action returns “no results” for bot messages that should match. At this point, we're coordinating with the Slack team to troubleshoot and understand the underlying behavior, and we’ll share updates as we learn more. If you need help with this in the meantime, please contact our support team through this link: https://zapier.com/app/get-help Affected components Searches & Writes (Degraded performance)

  3. investigating Jun 30, 2026, 04:21 PM UTC

    Status: Investigating We’ve confirmed the issue where the Slack “Find Message” action returns “no results” for bot messages that should match. At this point, we’re actively still coordinating with the Slack team to understand the reasons for the change in behaviour, and we’ll share updates as we learn more. If you need help with this in the meantime, please contact our support team through this link: https://zapier.com/app/get-help Affected components Searches & Writes (Degraded performance)

  4. resolved Jul 02, 2026, 01:10 PM UTC

    Status: Resolved We’ve confirmed the issue where the Slack “Find Message” action returns “no results” for bot messages that should match. To subscribe to updates about the issue, please contact our support team through this link: https://zapier.com/app/get-help Affected components Searches & Writes (Operational)

Read the full incident report →