Zapier Outage History

Zapier is up right now

Zapier had 75 outages in the last 2 years totaling 42m of downtime — averaging 3.1 incidents per month.

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

Source: https://status.zapier.com

Minor June 16, 2026

Error connecting to Facebook Apps

Detected by Pingoru
Jun 16, 2026, 02:36 AM UTC
Resolved
Jun 16, 2026, 02:36 AM UTC
Duration
—
Timeline · 3 updates
  1. investigating Jun 15, 2026, 09:52 PM UTC

    Status: Investigating We are receiving customer reports that Zap workflows using Facebook Lead Ads or Facebook Pages are returning the following error when Zap runs occur. "An unknown error occurred." Users are also unable to connect to existing or create new app connections, with those connections instantly expiring. We're looking into the issue to identify its root cause.

  2. monitoring Jun 15, 2026, 11:02 PM UTC

    Status: Monitoring Our Engineering team has completed its initial investigation and is now working with Facebook to resolve the issue. Errors have decreased during our investigation, but we will continue to monitor for any spikes until we hear back from the Facebook team. We will provide updates as soon as we have more information.

  3. resolved Jun 16, 2026, 02:36 AM UTC

    Status: Resolved We have successfully resolved the Facebook Lead Ads integration issue that affected our platform from 12:30pm–4:00pm PDT (7:30pm–11:00pm UTC) on June 16, 2026. During this window, customers experienced failures when connecting or reconnecting Facebook Lead Ads and Facebook Pages integrations, and existing Zaps using these integrations failed to execute. We identified this as an upstream issue with Facebook's APIs, which has since been resolved. All affected workflows have been replayed and are now operating normally. If you continue to experience any issues with your Facebook integrations, please try reconnecting your Facebook app connection or don't hesitate to contact Zapier Support: https://zapier.com/app/get-help.

Read the full incident report →

Minor June 14, 2026

Intermittent errors loading Zapier Templates pages

Detected by Pingoru
Jun 14, 2026, 09:14 AM UTC
Resolved
Jun 14, 2026, 09:14 AM UTC
Duration
—
Affected: Website
Timeline · 3 updates
  1. investigating Jun 14, 2026, 06:06 AM UTC

    Status: Investigating We’re investigating an issue causing intermittent errors when loading Zapier Templates pages "Zapier Templates pages": https://zapier.com/templates, including some template detail/category pages (for example, Lead Management). You may see pages fail to load or display server errors intermittently. Our team is actively working to identify and resolve the root cause. We will provide updates as soon as we have more information. If you require any assistance, please contact our Support Team: https://zapier.com/app/get-help Affected components Website (Degraded performance)

  2. monitoring Jun 14, 2026, 08:37 AM UTC

    Status: Monitoring We’re seeing recovery for the issue affecting Zapier template pages "Zapier template pages": https://zapier.com/templates. The templates page should now be accessible again, and we’re continuing to monitor stability. Our team is still investigating and working on preventative measures to reduce the chance of this happening again. We’ll post another update when we have more information or when we’re ready to mark this resolved. If you continue to see errors accessing templates, contact Support: https://zapier.com/app/get-help. Affected components Website (Degraded performance)

  3. resolved Jun 14, 2026, 09:14 AM UTC

    Status: Resolved The issue affecting access to Zapier template pages has been resolved. Users should now be able to access template pages as expected. We’ve made improvements to help prevent this from happening again and will continue monitoring for stability. If you continue to experience issues accessing templates, please don't hesitate to contact Zapier Support: https://zapier.com/app/get-help. Affected components Website (Operational)

Read the full incident report →

Minor June 12, 2026

Templates not loading

Detected by Pingoru
Jun 12, 2026, 03:51 AM UTC
Resolved
Jun 12, 2026, 03:51 AM UTC
Duration
—
Affected: Website
Timeline · 3 updates
  1. investigating Jun 12, 2026, 03:03 AM UTC

    Status: Investigating We are currently investigating an issue affecting the Templates feature on our platform. Users may experience errors when attempting to load or select templates. Our team is actively working to identify and resolve the root cause. We will provide updates as soon as we have more information. If you require any assistance, please contact our Support Team: https://zapier.com/app/get-help Thank you for your patience. Affected components Website (Degraded performance)

  2. monitoring Jun 12, 2026, 03:38 AM UTC

    Status: Monitoring Templates should now be loading normally for users. We’re continuing to monitor and investigate to prevent this from happening again. If you’re still seeing issues, please contact Support: https://zapier.com/app/get-help Affected components Website (Degraded performance)

  3. resolved Jun 12, 2026, 03:51 AM UTC

    Status: Resolved The issue preventing some users from loading templates is now resolved, and templates are loading normally. If you’re still experiencing issues, please contact Support: http://zapier.com/app/get-help Affected components Website (Operational)

Read the full incident report →

Minor June 12, 2026

Delayed webhook Zap runs

Detected by Pingoru
Jun 12, 2026, 02:33 AM UTC
Resolved
Jun 12, 2026, 02:33 AM UTC
Duration
—
Affected: Instant Triggers
Timeline · 2 updates
  1. identified Jun 12, 2026, 02:32 AM UTC

    Status: Identified Some webhook-triggered Zap runs are experiencing processing delays. Our team is actively investigating the cause and working toward a resolution. Affected components Instant Triggers (Degraded performance)

  2. resolved Jun 12, 2026, 02:33 AM UTC

    Status: Resolved Between June 9 and June 11, some webhook-triggered Zap runs experienced processing delays of up to 48 hours. All delayed events have since been processed successfully, and no data was lost during this delay. We are implementing additional safeguards to prevent recurrence. If you experience any ongoing issues, contact Support: https://zapier.com/app/get-help Thank you for your patience. Affected components Instant Triggers (Operational)

Read the full incident report →

Minor June 8, 2026

Chatbots dropping connections; possible "Forbidden" errors

Detected by Pingoru
Jun 08, 2026, 06:18 PM UTC
Resolved
Jun 08, 2026, 06:18 PM UTC
Duration
—
Affected: Chatbots
Timeline · 2 updates
  1. identified Jun 08, 2026, 05:28 PM UTC

    Status: Identified We identified an issue that caused some Chatbots to fail or time out when customers initialized chats or interacted with embedded chatbots. Some users may have seen a "Forbidden" error. • The affected period was approximately 11:00 PM – 5:30 AM MST on June 8, 2026. • Zap Runs and tasks were not affected. • No data loss is expected. • The issue has since self-resolved. Chatbots metrics are healthy and error rates have returned to normal. We traced the cause to a degradation in our LLM proxy, which led to backend request timeouts and dropped chatbot connections. We are continuing to investigate the scope of customer impact and will post another update soon. If you experienced issues with Chatbots during this window or notice anything still not working, please contact Support: https://zapier.com/app/get-help Affected components Chatbots (Degraded performance)

  2. resolved Jun 08, 2026, 06:18 PM UTC

    Status: Resolved The issue affecting Chatbots has been resolved. Between approximately 11:00 PM and 5:30 AM MST on June 8, 2026, some customers may have experienced failures or timeouts when initializing chats or interacting with embedded chatbots. The issue self-resolved and Chatbots has been operating normally since. Zap Runs and tasks were not affected. No data loss occurred. We are continuing to monitor the service and will take steps to reduce the likelihood of recurrence. If you experienced issues during this window or notice anything still not working, contact Support: https://zapier.com/app/get-help Affected components Chatbots (Operational)

Read the full incident report →

Minor June 6, 2026

Intermittent errors on Templates pages

Detected by Pingoru
Jun 06, 2026, 12:36 AM UTC
Resolved
Jun 06, 2026, 12:36 AM UTC
Duration
—
Affected: Website
Timeline · 3 updates
  1. investigating Jun 06, 2026, 12:11 AM UTC

    Status: Investigating Templates pages are intermittently failing to load in production. Users may see errors when loading the Templates page or individual template pages, and some content (like images) may not display correctly. We’re actively investigating and will share another update when more information is available. Questions? Contact Support: http://zapier.com/app/get-help Affected components Website (Degraded performance)

  2. monitoring Jun 06, 2026, 12:24 AM UTC

    Status: Monitoring Templates pages are loading normally again after intermittent loading errors. We’re continuing to monitor performance and traffic to ensure the issue does not recur. If you’re still seeing problems, please contact Support: https://zapier.com/app/get-help. Affected components Website (Degraded performance)

  3. resolved Jun 06, 2026, 12:36 AM UTC

    Status: Resolved The issue affecting Zapier Templates pages has been resolved. Some users may have experienced intermittent errors or missing content when loading Templates pages. We’ve taken steps to stop the abnormal traffic driving the problem, and the Templates pages are now operating normally. If you’re still seeing issues, please contact Support: https://zapier.com/app/get-help Affected components Website (Operational)

Read the full incident report →

Minor June 5, 2026

Zap History Export Notifications are not being send to users.

Detected by Pingoru
Jun 05, 2026, 07:41 PM UTC
Resolved
Jun 05, 2026, 07:41 PM UTC
Duration
—
Affected: Zap History
Timeline · 3 updates
  1. investigating Jun 05, 2026, 06:14 PM UTC

    Status: Investigating We have received reports that Zap History export notifications are not being sent when customers are requesting an export of their Zap runs. This means that emails with the download link for those exports are not being sent. Our team is working to identify and resolve the issue as soon as possible. We'll continue to give updates as we make progress. Affected components Zap History (Degraded performance)

  2. identified Jun 05, 2026, 07:19 PM UTC

    Status: Identified Our Engineering team has identified the root cause of the issue and is working towards resolving it. We'll continue to update as we make progress! Affected components Zap History (Degraded performance)

  3. resolved Jun 05, 2026, 07:41 PM UTC

    Status: Resolved A fix has been implemented, and after some monitoring, we're no longer seeing errors when customers are requesting Zap History exports. Any previous export requests during the incident window below have been successfully replayed, so no action is needed. Jun 5th 2026 13:42 - 19:00 UTC If you're still having issues or have questions, please reach out to our Support team at https://zapier.com/app/get-help Affected components Zap History (Operational)

Read the full incident report →

Minor June 2, 2026

Code by Zapier is running into Lamda errors mentioning KMS

Detected by Pingoru
Jun 02, 2026, 11:16 PM UTC
Resolved
Jun 02, 2026, 11:16 PM UTC
Duration
—
Timeline · 3 updates
  1. investigating Jun 02, 2026, 10:33 PM UTC

    Status: Investigating We are currently investigating an issue with Code by Zapier that is resulting in error messages when those steps are running: “Lambda was unable to configure access to your environment variables, because you have reached the grant limit of your KMS key or execution role”. We are working on resolving this as soon as possible, and will update this Status page as soon 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!

  2. monitoring Jun 02, 2026, 11:01 PM UTC

    Status: Monitoring A fix has been implemented and we are now monitoring the results. Code by Zapier steps that were failing with the environment variable error should now be running normally again. We are continuing to watch closely to confirm full recovery, and any tasks that were affected during the disruption are being replayed. We’ll post a final update once we’ve confirmed 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.

  3. resolved Jun 02, 2026, 11:16 PM UTC

    Status: Resolved This incident has been resolved. The issue that was causing some Code by Zapier steps to fail with the environment variable error has been fixed, and Code by Zapier is now operating normally. Any tasks that were affected during the disruption have been replayed, so no action is needed on your end. 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 working on resolving that.

Read the full incident report →

Minor June 2, 2026

Code by Zapier seeing errors

Detected by Pingoru
Jun 02, 2026, 05:26 PM UTC
Resolved
Jun 02, 2026, 05:26 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating Jun 02, 2026, 03:54 PM UTC

    Status: Investigating We are currently investigating an issue affecting the ability of Code by Zapier steps to run. Starting at approximately 11:00am EST, some Code by Zapier steps began encountering errors, including CodeStorageExceededException OR ResourceConflictException This is affecting new Code by Zapier steps, and some existing steps as well. We will provide updates as we make progress on resolving this issue. Thank you for your patience.

  2. investigating Jun 02, 2026, 04:51 PM UTC

    Status: Investigating We're continuing to investigate reports of errors affecting Code by Zapier steps, including “CodeStorageExceededException” and “ResourceConflictException.” Our engineering team remains actively engaged in identifying the cause of the issue. While we do not have any new information to share at this time, we will provide further updates as our investigation progresses. If you have any questions, please reach out to our support team — https://zapier.com/app/get-help Thank you for your patience and understanding.

  3. monitoring Jun 02, 2026, 05:20 PM UTC

    Status: Monitoring We have pushed out a fix for this Code by Zapier error, and are monitoring the results to ensure that it is working as intended, and fully clearing up those errors. Once we have been able to confirm that this issue is officially resolved, we will update this Status to reflect that. If you have any questions, please reach out to our support team: https://zapier.com/app/get-help Thank you again for your patience and understanding.

  4. resolved Jun 02, 2026, 05:26 PM UTC

    Status: Resolved We have been able to confirm that the update we previously pushed has fully resolved that error. So your Code by Zapier steps should be working as normal, and no longer running into those errors. If you are running into this error, please reach out to our support team: https://zapier.com/app/get-help Thanks again for your patience while we resolved that.

Read the full incident report →

Major May 22, 2026

Zapier Sidekick users are getting logged out and running into errors.

Detected by Pingoru
May 22, 2026, 06:34 PM UTC
Resolved
May 22, 2026, 07:16 PM UTC
Duration
42m
Affected: Website
Timeline · 1 update
  1. investigating May 22, 2026, 06:34 PM UTC

    Status: Investigating Sidekick users are experiencing an issue with getting logged out, and running into session errors. After the users then log back in, they are no longer able to see and access workspace content and chats. We are currently investigating the cause of this issue, and will update here once we have more information. Affected components Website (Degraded performance)

Read the full incident report →

Minor May 21, 2026

Delays between Zap execution

Detected by Pingoru
May 21, 2026, 03:05 AM UTC
Resolved
May 21, 2026, 03:05 AM UTC
Duration
—
Timeline · 2 updates
  1. investigating May 20, 2026, 11:57 PM UTC

    Status: Investigating We have identified delays between Zap execution and when runs become visible in Zap History. Importantly, Zap executions themselves are not failing or delayed — this issue only impacts the visibility of Zap History data in the UI. Our team is actively investigating the issue and we will continue to provide updates as soon as more information becomes available.

  2. resolved May 21, 2026, 03:05 AM UTC

    Status: Resolved This issue has been resolved. The delays between Zap execution and when runs become visible in Zap History are no longer occurring. Zap History data should now be appearing in the UI as expected. As noted in our earlier update, Zap executions themselves were not impacted — this issue only affected the visibility of run data in the UI. Thank you for your patience while our team worked on this. If you continue to experience any issues, please don't hesitate to contact support: https://zapier.com/app/get-help

Read the full incident report →

Minor May 20, 2026

LinkedIn Integrations— authentication and connection errors

Detected by Pingoru
May 20, 2026, 05:00 PM UTC
Resolved
May 20, 2026, 05:00 PM UTC
Duration
—
Timeline · 3 updates
  1. investigating May 20, 2026, 12:43 PM UTC

    Status: Investigating We are currently experiencing intermittent authentication and connection issues affecting our LinkedIn, LinkedIn Conversions, and LinkedIn Lead Gen Forms integrations. Users may see authentication failures or connection errors when attempting to use Zaps with these LinkedIn integrations. These issues began around 1:50am EDT on May 20th and are impacting a subset of our users. LinkedIn's platform is experiencing widespread API issues, resulting in elevated error rates (primarily 401 authentication failures and 500 server errors). This has been confirmed on LinkedIn's API status page. We are actively monitoring the situation and working with LinkedIn to track their recovery progress. We apologize for any disruption this may cause to your workflows. We'll continue to monitor this closely and will update you as the situation develops.

  2. monitoring May 20, 2026, 04:10 PM UTC

    Status: Monitoring We’re seeing recovery in LinkedIn and LinkedIn Ads integrations after an upstream LinkedIn API incident that caused intermittent authentication and API errors (401/500/503). Our internal error rates have returned to normal levels and we’ve replayed a small set of impacted tasks. We’ll continue monitoring closely and will share another update if anything changes. If you’re still seeing issues, please retry your connection or task and contact Support "contact Support ": https://zapier.com/app/get-help with a link to the affected Zap.

  3. resolved May 20, 2026, 05:00 PM UTC

    Status: Resolved The issue affecting our LinkedIn, LinkedIn Conversions, and LinkedIn Lead Gen Forms integrations has been resolved. Earlier today, an upstream LinkedIn API incident caused intermittent authentication and connection errors. LinkedIn’s platform has recovered, our internal error rates are back to normal, and we’ve replayed impacted tasks where needed. LinkedIn and LinkedIn Ads integrations should be working normally again. If you still see errors, retry your connection or Zap task. If you need help, contact Support: https://zapier.com/app/get-help

Read the full incident report →

Minor May 20, 2026

Customer with a large number of app restrictions cannot manage custom actions.

Detected by Pingoru
May 20, 2026, 12:11 AM UTC
Resolved
May 20, 2026, 12:11 AM UTC
Duration
—
Timeline · 2 updates
  1. monitoring May 19, 2026, 11:23 PM UTC

    Status: Monitoring Our Engineering team is currently monitoring reports indicating that Enterprise users with a high number of app restrictions (over 100) are unable to modify or manage custom actions. Affected users will see the following error when viewing custom actions. We couldn't determine whether this app is restricted. Please try again in a moment. We'll continue to keep our customers informed as we identify the root cause and resolve the issue.

  2. resolved May 20, 2026, 12:11 AM UTC

    Status: Resolved The issue preventing some enterprise customers from managing custom actions has been resolved. Customers with over 100 app restrictions were unable to paginate through their custom actions due to a URL formatting issue in our system. This has been corrected and all affected pages now load as expected. No data was lost and no customer action is required. If you're still experiencing issues, contact Support: https://zapier.com/app/get-help Thank you for your patience.

Read the full incident report →

Minor May 8, 2026

Errors when creating or reconnecting app connections

Detected by Pingoru
May 08, 2026, 10:11 PM UTC
Resolved
May 08, 2026, 10:11 PM UTC
Duration
—
Timeline · 4 updates
  1. investigating May 08, 2026, 09:02 PM UTC

    Status: Investigating We are currently investigating an issue where users may encounter the following error when creating a new connection or reconnecting an app: "Failed to execute 'removeChild' on 'Node': parameter 1 is not of type 'Node'. Uh oh, something is not quite right!" Our team is actively working to identify the root cause. We’ll provide updates as soon as more information is available.

  2. identified May 08, 2026, 09:26 PM UTC

    Status: Identified We’ve identified the root cause of the issue causing errors when creating or reconnecting app connections, including the message: "Failed to execute 'removeChild' on 'Node': parameter 1 is not of type 'Node'. Uh oh, something is not quite right!" Our team is working on implementing a fix. We’ll share another update as soon as more information is available.

  3. monitoring May 08, 2026, 09:33 PM UTC

    Status: Monitoring We’ve rolled back a recent change that was identified as the cause of errors when creating or reconnecting app connections. We are seeing signs of recovery and are continuing to monitor performance closely to ensure the issue is fully resolved. We’ll provide another update once monitoring is complete.

  4. resolved May 08, 2026, 10:11 PM UTC

    Status: Resolved Our Engineering team has monitored our backend for any spikes in errors after the fix was released, and we're happy to see that we're at normal operation and no longer seeing errors. As such, the incident is now considered resolved. Please reach out to our Support team if you continue to see issues or have questions about the incident.

Read the full incident report →

Minor May 8, 2026

High Latency is impacting hook ingestion

Detected by Pingoru
May 08, 2026, 09:34 PM UTC
Resolved
May 08, 2026, 09:34 PM UTC
Duration
—
Timeline · 2 updates
  1. investigating May 08, 2026, 08:32 PM UTC

    Status: Investigating We are currently investigating an issue causing elevated latency in hook ingestion and event processing. As a result, some customers may experience delays of approximately 30–40 minutes before events are processed. Our team is actively working on the fix.We appreciate your patience and understanding while we work to resolve this issue.

  2. resolved May 08, 2026, 09:34 PM UTC

    Status: Resolved The issue has been resolved, and all systems are back to normal.

Read the full incident report →

Minor May 7, 2026

Zap error notifications

Detected by Pingoru
May 07, 2026, 04:49 PM UTC
Resolved
May 07, 2026, 04:49 PM UTC
Duration
—
Affected: Zap History
Timeline · 3 updates
  1. investigating May 06, 2026, 05:13 PM UTC

    Status: Investigating We’re investigating an issue affecting some Zaps that use error handling. You may have received an email titled “High Error Ratio” explaining that your Zap would be switched off. In some cases, that may not have matched what you see in normal use, and your Zap may have been paused as a result. We’re working on a fix to prevent this from happening again. If that happened to your Zap, you can turn it back on from your Zapier dashboard. We’ll post another update here when we have more to share. Affected components Zap History (Degraded performance)

  2. monitoring May 06, 2026, 07:35 PM UTC

    Status: Monitoring We’ve deployed a fix for an issue affecting some Zaps that use error handling. You may have received an email titled “High Error Ratio” explaining that your Zap would be switched off. In some cases, that may not have matched what you see in normal use, and your Zap may have been paused as a result. We’re monitoring closely to confirm the fix is working as expected and to ensure this does not recur. If your Zap was paused, you can turn it back on from your Zapier dashboard. We’ll post another update here if anything changes. If you are still experiencing this issue causing your Zaps to turn off, you can reach out to our team at: https://zapier.com/app/get-help. Affected components Zap History (Degraded performance)

  3. resolved May 07, 2026, 04:49 PM UTC

    Status: Resolved The issue causing incorrect “High Error Ratio” notifications has been resolved. Impact Some users received an email titled “High Error Ratio” indicating their Zap would be switched off. In certain cases, this did not reflect actual Zap performance, and some Zaps may have been paused incorrectly as a result. Resolution We implemented a fix and confirmed that notifications and Zap status are now behaving as expected. If you are still experiencing this issue causing your Zaps to turn off, you can reach out to our team at: https://zapier.com/app/get-help. Affected components Zap History (Operational)

Read the full incident report →

Minor May 6, 2026

Google SSO Login Failures

Detected by Pingoru
May 06, 2026, 11:18 PM UTC
Resolved
May 06, 2026, 11:18 PM UTC
Duration
—
Affected: Login
Timeline · 3 updates
  1. investigating May 06, 2026, 08:57 PM UTC

    Status: Investigating We are currently investigating an issue impacting Google single sign-on (SSO). Users attempting to log in to their zapier.com account using Google SSO may be unable to authenticate at this time. Impact All users are affected when using Google SSO. Login via username and password remains available, and users with active sessions are not impacted. Running automations continue to operate normally. Current Status Our engineering team is actively investigating the root cause. Initial efforts are focused on reviewing Google SSO configuration, credentials, and related environment variables. Relevant teams have been engaged and are working to identify and resolve the issue as quickly as possible. We will provide further updates as more information becomes available. Affected components Login (Partial outage)

  2. monitoring May 06, 2026, 09:20 PM UTC

    Status: Monitoring Monitoring: Google SSO Login Failures We have identified the issue impacting Google single sign-on (SSO) and have rolled back a recent website update as part of our mitigation efforts. Impact Users may have experienced failures when attempting to log in with Google SSO. Login via username and password remained available, and users with active sessions were not impacted. Running automations continued to operate normally. Current Status We are now monitoring the results of the rollback and are seeing signs of recovery. Our team will continue to observe system performance to ensure stability. We will provide further updates if any additional issues arise or once the incident is fully resolved. Affected components Login (Partial outage)

  3. resolved May 06, 2026, 11:18 PM UTC

    Status: Resolved Our team has confirmed that since 21:14 UTC all customers logging into Zapier via Google SSO can do so successfully. If you are still running into any issues, please contact our support team for assistance: https://zapier.com/app/get-help Affected components Login (Operational)

Read the full incident report →

Minor May 6, 2026

Errors related to Klaviyo app integration

Detected by Pingoru
May 06, 2026, 02:20 AM UTC
Resolved
May 06, 2026, 02:20 AM UTC
Duration
—
Timeline · 3 updates
  1. investigating May 05, 2026, 09:32 PM UTC

    Status: Investigating We are looking into an issue related to the Klaviyo app returning 522 timeout errors. This is related to an incident with Klaviyo here: https://status.klaviyo.com/incidents/yyh7s59brj67

  2. monitoring May 05, 2026, 09:45 PM UTC

    Status: Monitoring We are continuing to monitor the service disruption related to Klaviyo: https://status.klaviyo.com/incidents/yyh7s59brj67 If you are experiencing issues with this app integration, you can reach out to our team at: https://zapier.com/app/get-help

  3. resolved May 06, 2026, 02:20 AM UTC

    Status: Resolved The issue causing 522 timeout errors with the Klaviyo app integration has been resolved. This was related to an upstream service disruption on Klaviyo's side: https://status.klaviyo.com/incidents/yyh7s59brj67 Zaps using Klaviyo should now be functioning as expected. No data loss occurred — any Zap runs that failed during the incident can be replayed from Zap History. If you are still experiencing issues with your Klaviyo integration, please contact Support: https://zapier.com/app/get-help Thank you for your patience.

Read the full incident report →

Minor May 6, 2026

Session initialization failed error when trying to connect apps

Detected by Pingoru
May 06, 2026, 12:34 AM UTC
Resolved
May 06, 2026, 12:34 AM UTC
Duration
—
Timeline · 3 updates
  1. investigating May 05, 2026, 10:49 PM UTC

    Status: Investigating We are currently investigating an issue where users receive "Session initialization failed" errors when attempting to connect apps in Zapier.

  2. monitoring May 05, 2026, 11:06 PM UTC

    Status: Monitoring We are monitoring reports where users receive "Session initialization failed" errors when attempting to connect apps in Zapier. If you are experiencing issues with this, you can reach out to our team at: https://zapier.com/app/get-help

  3. resolved May 06, 2026, 12:34 AM UTC

    Status: Resolved We’ve resolved an issue where some users could see a “Session initialization failed” error when creating new app connections. The issue was caused by an unintended staged rollout configuration and was mitigated by rolling back the rollout. Existing Zaps and workflows were not impacted. If you saw a failed connection attempt during the incident window, please retry creating the connection now. If you’re still experiencing issues creating new app connections, please contact Zapier Support.

Read the full incident report →

Minor May 1, 2026

INC-908: Firecrawl outage

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

    Status: Monitoring At approximately 4:45 AM UTC we experienced degraded performance affecting agents web search and chatbot website knowledge-source syncing due to an outage at our third-party provider, Firecrawl. Firecrawl has recovered and our services are operating normally again. Most affected runs recovered automatically, but a subset of agent runs may have failed during the incident window—customers can check their Activity and retry failed runs if needed. We’re continuing to monitor for any residual errors and will provide an update before closing. Affected components Agents (Degraded performance)

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

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

Read the full incident report →