Looking for an update now? Check the current status, or follow Zapier for future changes.
84.7%of 59 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
86.7%
30
4
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 24Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
Incident History
No source-attested incident records are available for the current collector history. Older legacy archive records remain available below.
Legacy Incident Archive
77 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
July 2026
BambooHR: Testing/creating connections fail with status code 403
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We've identified the cause the issue preventing users from creating new BambooHR connections or testing/updating existing BambooHR connections.
We've released an update the we believe will address this issue, and will continue to monitor to confirm the issue is resolved.
investigating
We've received reports of customers being unable to create new BambooHR connections, or test existing BambooHR connections, within the Zap Editor. Attempts at either result in an error code with response status code 403.
We are working with BambooHR to identify the cause of the error and resolve this as quickly as possible.
Translate by Zapier – Elevated Error Rate
Source not attested
Last archived state: resolved
View archived record details
investigating
We are currently investigating elevated error rates affecting the Translate by Zapier integration. Starting at approximately 2:00pm UTC on July 20, 2026, users of this integration have been experiencing 403 "User Rate Limit Exceeded" errors when attempting to use the translation features.
**What's Happening**
Our investigation has identified that the Google Cloud Translation API v2 is returning rate limit errors for requests from the Translate by Zapier integration. This is causing approxima...
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](https://zapier.com/app/get-help "https://zapier.com/app/get-help")
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](https://zapier.com/app/get-help "https://zapier.com/app/get-help")
AI by Zapier
Source not attested
Last archived state: resolved
View archived record details
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.
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.
Increased 4XX errors from Airtable
Source not attested
Last archived state: resolved
View archived record details
monitoring
We’ve confirmed the trigger-side impact from the Airtable incident has healed, and are looking into replaying any missed triggers.
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](https://zapier.com/app/get-help "https://zapier.com/app/get-help")
Users who sign up for a Team trial are instead signed up for a Pro trial.
Source not attested
Last archived state: resolved
View archived record details
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](https://zapier.com/app/get-help "https://zapier.com/app/get-help").
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](https://zapier.com/app/get-help "ht...
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](https://zapier.com/app/get-help "https://zapier.co...
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.
June 2026
Slack Find Message action is unable to find bot messages
minorSource not attested
Last archived state: resolved
View archived record details
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](https://zapier.com/app/get-help "https://zapier.com/app/get-help")
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](https://zapier.com/app/get-help " https://zapier.com/app/get-help")
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 ...
Degraded performance for Zapier Agents
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We’re currently experiencing an issue where some Zapier Agents runs may fail or be missed.
This may affect:
• Zapier Agents
• Agent-triggered workflow runs
Zapier’s core automation systems are otherwise continuing to process normally.
If you need help, contact Support: [https://zapier.com/app/get-help](https://zapier.com/app/get-help "https://zapier.com/app/get-help")
Delayed processing for webhook-based triggers
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results. We increased processing capacity to clear the backlog of delayed webhook-based trigger events, and trigger processing has returned to normal.
No trigger data was lost during the incident — affected events were delayed rather than dropped, and the backlog has now cleared. Our team is continuing to monitor processing times closely to ensure they remain stable.
If you have any questions, please reach out to our support team: [http...
investigating
We are currently investigating an issue causing delays in the processing of webhook-based triggers. As a result, some Zaps that rely on trigger events may run later than usual. This may affect trigger events across a range of apps.
No trigger data is being lost — affected events are delayed, not dropped, and will be processed once the system catches up. Our team is actively investigating and working to restore normal processing times.
If you have any questions, please reach out to our sup...
Facebook Lead Ads intermittently missing leads
Source not attested
Last archived state: resolved
View archived record details
monitoring
We continue to work in active coordination with Meta, who have implemented a fix to reduce impact to your workflows and resume the proper delivery of leads.
Their incident team is proactively applying further optimizations, and monitoring the situation to confirm resolution.
If you have any questions or need help, contact us at zapier.com/get-help.
identified
We're in active coordination with our partners at Meta, who have identified an issue with their webhook delivery to 3rd party apps. Meta's incident team is engaged and working toward remediation.
investigating
We continue to work with our Partners from Meta to identify the root cause and provide next steps.
We remain available at zapier.com/get-help if you have any questions or need assistance.
investigating
We're received reports of missed leads for Facebook Lead Ads triggers. We're currently working with our Partners at Meta to figure out the root cause and implement a fix as soon as possible. We'll be updating this status page with our progress.
Many thanks for your patience! If you have any questions, feel free to reach us at zapier.com/get-help.
