Zapier Outage History

Started Feb 25, 2026, 03:58 PM UTC· resolved Feb 25, 2026, 05:56 PM UTC

1. investigating Feb 25, 2026, 03:58 PM UTC

   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

   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

   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 →

Started Feb 24, 2026, 02:52 AM UTC· resolved Feb 24, 2026, 04:07 AM UTC

1. investigating Feb 24, 2026, 02:52 AM UTC

   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

   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

   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 →

Started Feb 20, 2026, 07:51 PM UTC· resolved Feb 21, 2026, 06:47 PM UTC

1. identified Feb 20, 2026, 07:51 PM UTC

   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

   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

   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 →

Started Feb 13, 2026, 08:03 AM UTC· resolved Feb 13, 2026, 03:44 PM UTC

1. monitoring Feb 13, 2026, 08:03 AM UTC

   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

   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

   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 →

Started Feb 12, 2026, 06:02 PM UTC· resolved Feb 12, 2026, 06:19 PM UTC

1. investigating Feb 12, 2026, 06:02 PM UTC

   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.

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

   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

Read the full incident report →

Started Feb 12, 2026, 03:37 PM UTC· resolved Feb 12, 2026, 05:55 PM UTC

1. investigating Feb 12, 2026, 03:37 PM UTC

   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

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

   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

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

   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

Read the full incident report →

Started Feb 10, 2026, 08:47 PM UTC· resolved Feb 10, 2026, 11:06 PM UTC

1. investigating Feb 10, 2026, 08:47 PM UTC

   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

   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

   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 →

Started Feb 10, 2026, 06:48 PM UTC· resolved Feb 10, 2026, 07:11 PM UTC

1. investigating Feb 10, 2026, 06:48 PM UTC

   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

   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

   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 →

Started Jan 30, 2026, 03:30 PM UTC· resolved Jan 30, 2026, 08:27 PM UTC

1. investigating Jan 30, 2026, 03:30 PM UTC

   We're investigating an issue affecting OAuth login on mcp.zapier.com "mcp.zapier.com": http://mcp.zapier.com for newly signed-up customers. Impact: New customers who signed up after 18:00 UTC on January 29 may experience OAuth login failures when accessing MCP (our agent platform). Unaffected: All other Zapier services are operating normally. Existing customers are not impacted. Status: Our engineering team is actively investigating the root cause, which appears to be related to a recent change in how new accounts are synchronized between our systems. We are working to identify and fix the underlying issue. Next steps: We’ll share updates as we make progress. If you signed up recently and can’t log in to MCP, please contact our support team for assistance. https://zapier.com/app/get-help We appreciate your patience while we work to resolve this issue.

2. monitoring Jan 30, 2026, 04:49 PM UTC

   Identified: Jan 29, 2026, 23:36:19.834 UTC Monitoring: Jan 30, 2026, 16:38:00 UTC Update: We’ve identified and addressed the issue preventing some newly signed-up customers from logging in to mcp.zapier.com "mcp.zapier.com": http://mcp.zapier.com. The fix has been deployed, and login attempts are now succeeding as expected. We’re continuing to monitor the situation to ensure everything remains stable. All other Zapier services are operating normally.

3. resolved Jan 30, 2026, 08:27 PM UTC

   We're happy to report that the issue related to failures associated with logging in to http://mcp.zapier.com/ has been resolved. Functionality has been fully restored, and users can now login without error. 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 →

Started Jan 28, 2026, 09:38 PM UTC· resolved Jan 29, 2026, 12:44 AM UTC

1. identified Jan 28, 2026, 09:38 PM UTC

   We are currently experiencing intermittent issues with sample record retrieval in the Zapier editor. When users attempt to pull sample records during the trigger step of Zap setup or editing, they may encounter throttling errors that prevent the samples from loading. There is no impact to existing, already built Zaps.

2. monitoring Jan 29, 2026, 12:22 AM UTC

   The number of errors generated by this issue has subsided, and our customers' reports have also decreased. Our teams continue to monitor the issue to ensure it is resolved. We'll provide another update if we see changes in frequency or if the issue is resolved. If you continue to see issues, please feel free to reach out to our Support team: https://zapier.com/app/get-help

3. resolved Jan 29, 2026, 12:44 AM UTC

   We are happy to report that the issue has been resolved and we are no longer seeing reports of issues from our customers. There's no action to take, and loading sample trigger data should now be working as expected. Please let us know if you're still seeing issues or have questions!

Read the full incident report →

Started Jan 28, 2026, 10:07 AM UTC· resolved Feb 04, 2026, 12:37 AM UTC

1. investigating Jan 28, 2026, 10:07 AM UTC

   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

   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

   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

   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

   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

   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

   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

   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

   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

    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

    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 →