Monitoring - Starting May 26, there will be changes to our Gmail integration for consumer Gmail users (Gmail accounts ending in @gmail.com or @googlemail.com) that may require you to change your Zaps. More information and details on how to work with these changes can be found on our help documentation about Gmail here: https://zapier.com/help/common-problems-gmail/#my-gmail-zap-has-an-error-about-connecting-to-google-approved-or-not-approved-apps To be notified of updates regarding these changes, please subscribe to this issue.

Since our first communication with our consumer Gmail users on May 2, the list of applications approved by Google that you can send consumer Gmail data to has changed to the following:

Added to the Google-approved list: Contacts+, LionDesk CRM, Bombbomb.com.
Removed from the Google-approved list: Slack, Trello, and Asana. If you have any Zaps that send consumer Gmail data to these three apps, you will need to update them by May 26th to keep your Zaps working.

At the time of this writing, consumer Gmail users connecting Gmail to Google-approved apps on Zapier have until June 26 to re-authenticate their Google-approved apps on their Zapier account here: https://zapier.com/manage/gmail-permissions

The current list of approved apps can always be found in our help documentation about Gmail, and further changes will be posted here until final changes go live on June 26, 2019. Subscribe for instant updates.
May 22, 09:57 PDT
Website ? Operational
Zaps Operational
Instant Triggers ? Operational
Polling Triggers ? Operational
Searches & Writes ? Operational
Apps ? Operational
Developer Platform Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Polling Triggers Reliability ?
Fetching
Polling Triggers Response Time ?
Fetching
Instant Triggers Reliability ?
Fetching
Instant Triggers Response Time ?
Fetching
Support Queue ?
Fetching
Past Incidents
May 25, 2019

No incidents reported today.

May 24, 2019

No incidents reported.

May 23, 2019
Resolved - At 15:00 (3:00 PM) UTC, ClickFunnels began returning a 200 / OK response. All Triggers and Actions should be operational now.
May 23, 11:04 PDT
Identified - Starting around 9:30 PM UTC all requests to ClickFunnels from Zapier have been failing with a 503 / Service Unavailable error -- however, existing "Instant" Zaps with a ClickFunnel trigger (that send data to Zapier) continue to work.
May 22, 20:30 PDT
May 21, 2019
Resolved - The issue has been resolved and all apps can now be connected/reconnected again.
May 21, 19:03 PDT
Identified - Engineering has identified the issue. We are working on getting a fix in place so apps can be connected again.
May 21, 18:46 PDT
Investigating - Currently apps are unable to be connected or reconnected here: https://zapier.com/app/connections

Engineering is currently investigating this issue.
May 21, 18:11 PDT
Resolved - Error rates have stayed clean for the last hour, so we are closing this out now. Please feel free to reach out if you have any questions! https://zapier.com/app/contact-us
May 21, 14:17 PDT
Monitoring - Error rates from the Facebook Lead Ads API have returned to normal rates. If you have Zaps that you need to turn on, you should be able to do that now.

We will continue to monitor this issue for a short time, to ensure everything continues as expected.
May 21, 13:43 PDT
Identified - We are seeing increased error rates from the Facebook Lead Ads API.

Currently this is affecting the ability to turn a Zap on or off, when using a Facebook Lead Ads trigger. Some requests are successful, so it may work if you try turning it on again.

We will continue to monitor this and update as we learn more.
May 21, 11:39 PDT
Resolved - Salesforce has resolved the service disruption that was causing "timeout" errors for some Zaps: https://status.salesforce.com/incidents/3815

If any of your tasks have received errors, you should be able to replay them now from the task history.

Please let us know if you have any questions, or if you're seeing any errors you'd like us to help take a closer look at: https://zapier.com/app/contact-us
May 21, 11:11 PDT
Monitoring - We have seen a reduction in errors from the Salesforce API, and we have put our systems back to normal.

We will continue to monitor until Salesforce gives the all-clear for this incident: https://status.salesforce.com/incidents/3815

If any of your tasks have received errors, you should be able to replay them now from the task history. Please do not hesitate to reach out if you have any questions: https://zapier.com/app/contact-us
May 17, 18:36 PDT
Update - Salesforce has identified an incident with their service. The affects to your Zaps could include timeout errors or other errors.

We expect that once their maintenance is complete, Zaps will be back to normal. Salesforce has additional information about the incident here:
https://status.salesforce.com/incidents/3815
May 17, 12:25 PDT
Identified - We have identified issues with the Salesforce service.
May 17, 12:17 PDT
Resolved - A bug was deployed to the servers that power hooks.zapier.com, causing them to become unhealthy. This led to all webhook requests failing with an HTTP 503 error. We have now reverted the change and hooks are being accepted again, so any hooks that failed to be delivered should be resent. Please accept our sincere apologies for the disruption caused.
May 21, 03:54 PDT
Identified - There is currently an issue causing all instant triggers to fail. We are currently deploying a fix and normal service will be resumed shortly.
May 21, 03:47 PDT
May 20, 2019

No incidents reported.

May 19, 2019

No incidents reported.

May 18, 2019

No incidents reported.

May 17, 2019
Resolved - This issue was related to the Salesforce incident from today. Our systems are back to normal now, but we are continuing to monitor the related Salesforce incident:
https://status.salesforce.com/incidents/3815
May 17, 18:32 PDT
Investigating - We are currently investigating this issue.
May 17, 12:22 PDT
May 16, 2019

No incidents reported.

May 15, 2019

No incidents reported.

May 14, 2019

No incidents reported.

May 13, 2019

No incidents reported.

May 12, 2019

No incidents reported.

May 11, 2019

No incidents reported.