IFTTT

Affected: IFTTT.com, IFTTT mobile apps

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-24 14:09 UTC

   We're experiencing issues across IFTTT.com and the IFTTT mobile apps. We are currently looking into the issue.

2. identified 2026-08-24 14:15 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-08-24 14:17 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-08-24 17:16 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on IFTTT's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-08-24 14:00 UTC

   We're experiencing issues across IFTTT.com and the IFTTT mobile apps. We are currently looking into the issue.

Excerpts are shortened. Read the full incident on IFTTT's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-25 22:56 UTC

   We're currently investigating an issue that is preventing some users from receiving messages sent by the SMS service's send me an SMS action.

2. monitoring 2026-06-29 20:41 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-06-30 18:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on IFTTT's status page.

Affected: Applet performance

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2026-04-08 07:51 UTC

   We're experiencing a higher number of Applet run errors. The issue has been identified, a fix has been applied and we are monitoring performance.

2. resolved 2026-04-08 10:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on IFTTT's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-12-05 21:26 UTC

   We are currently investigating this issue.

2. investigating 2025-12-08 15:32 UTC

   Paused services may be experiencing technical difficulties. All Applets using these services will resume once the technical difficulties are resolved.

3. resolved 2026-01-14 23:34 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on IFTTT's status page.

Affected: IFTTT.com, IFTTT mobile apps

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-10-20 16:15 UTC

   We're experiencing issues across IFTTT.com and the IFTTT mobile apps. We are currently looking into the issue.

2. investigating 2025-10-20 16:43 UTC

   We are continuing to investigate this issue.

3. monitoring 2025-10-20 21:24 UTC

   We are seeing improvements in the responsiveness of our website and the mobile apps. We will continue to monitor service health until we can confirm that all issues have been resolved.

4. resolved 2025-10-21 07:08 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on IFTTT's status page.

Affected: IFTTT.com

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-10-06 17:56 UTC

   We're experiencing an elevated level of errors on ifttt.com and are currently looking into the issue.

2. monitoring 2025-10-06 18:11 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2025-10-06 18:17 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on IFTTT's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-09-15 18:24 UTC

   The Jira service is paused while we address an API deprecation. Thank you for your patience.

2. resolved 2026-09-11 11:34 UTC

   This issue has been resolved. Users are requested to reconnect the service by going to https://ifttt.com/jira/settings and clicking "Reconnect".

Excerpts are shortened. Read the full incident on IFTTT's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-09-08 16:25 UTC

   We’re currently looking into an issue that’s causing some users not to receive text messages, including those from the Send me an SMS action and two-factor authentication (2FA) codes sent via SMS.

2. identified 2025-09-09 13:18 UTC

   Two-factor authentication (2FA) codes are now successfully being sent, however Send me an SMS action runs continue to be affected. Thank you for your patience.

3. resolved 2025-09-12 15:24 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on IFTTT's status page.

Affected: Applet performance

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-09-03 21:06 UTC

   Paused services may be experiencing technical difficulties. All Applets using these services will resume once the technical difficulties are resolved.

2. resolved 2025-10-08 16:06 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on IFTTT's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-08-25 18:28 UTC

   Paused services may be experiencing technical difficulties. All Applets using these services will resume once the technical difficulties are resolved.

2. resolved 2026-08-06 21:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on IFTTT's status page.

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-08-14 02:53 UTC

   The notifications service is currently paused for maintenance. During this time, Applets that use notifications will not run.

2. resolved 2025-08-14 04:22 UTC

   The notifications service maintenance has been completed, and the service is now active. Applets using notifications are running as expected.

Excerpts are shortened. Read the full incident on IFTTT's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-08-12 22:36 UTC

   The notifications service is currently paused for maintenance. During this time, Applets that use notifications will not run.

2. resolved 2025-08-12 22:52 UTC

   The notifications service maintenance has been completed, and the service is now active. Applets using notifications are running as expected.

Excerpts are shortened. Read the full incident on IFTTT's status page.

Affected: IFTTT.com, IFTTT mobile apps, Applet performance

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-07-24 20:01 UTC

   We're experiencing issues across IFTTT.com and the IFTTT mobile apps. We are currently looking into the issue.

2. monitoring 2025-07-24 20:20 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2025-07-31 14:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on IFTTT's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-07-08 20:33 UTC

   Paused services may be experiencing technical difficulties. All Applets using these services will resume once the technical difficulties are resolved.

2. resolved 2026-01-14 23:34 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on IFTTT's status page.

Affected: Applet performance

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-06-12 18:33 UTC

   We're experiencing an elevated level of Applet run delays and are currently looking into the issue.

2. monitoring 2025-06-12 18:53 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2025-06-12 19:24 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on IFTTT's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-05-22 21:33 UTC

   We’re currently experiencing an outage that prevents new connections to the Twitter service. Existing Twitter Applets and the creation of new Applets are not affected. More details are available here: https://docs.x.com/status

2. resolved 2025-05-23 18:51 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on IFTTT's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-05-09 16:45 UTC

   Paused services may be experiencing technical difficulties. All Applets using these services will resume once the technical difficulties are resolved.

2. monitoring 2025-05-09 19:38 UTC

   The Twitter service has been unpaused and we're currently monitoring to ensure everything is working as expected.

3. resolved 2025-05-12 17:52 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on IFTTT's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-05-08 19:17 UTC

   Paused services may be experiencing technical difficulties. All Applets using these services will resume once the technical difficulties are resolved.

2. monitoring 2025-06-02 23:58 UTC

   The Ecobee service has been un-paused. Applets using this service should now be running as expected. If you're still experiencing issues, please reconnect the service at ifttt.com/ecobee/settings.

3. resolved 2025-06-12 18:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on IFTTT's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2025-04-29 01:22 UTC

   The Agile Octopus service is temporarily paused for maintenance. No Applet using Agile Octopus triggers or queries will be operational. Once unpaused, the users will need to reconnect their service.

2. monitoring 2025-04-29 18:05 UTC

   Maintenance is complete and the Agile Octopus service is now active again. We’re currently monitoring the service.

3. resolved 2025-05-05 19:54 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on IFTTT's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-03-15 00:16 UTC

   Paused services may be experiencing technical difficulties. All Applets using these services will resume once the technical difficulties are resolved.

2. monitoring 2025-03-20 17:18 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2025-03-20 22:50 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on IFTTT's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-03-05 23:06 UTC

   We're currently investigating an issue that is preventing the Webhooks service triggers, queries, and actions from running as expected.

2. monitoring 2025-03-05 23:17 UTC

   A fix has been implemented, and we are monitoring the results. This incident may have affected Webhooks Applet runs that occurred between 21:48 UTC and 23:10 UTC

3. resolved 2025-03-06 01:02 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on IFTTT's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2025-03-04 23:44 UTC

   Between March 3 at 8:00 PM UTC and March 4 at 4:30 AM UTC, some Applets may have run late or not triggered. The issue has been resolved, and Applets should now be functioning as expected. We apologize for any inconvenience and appreciate your patience. More details about this...

Excerpts are shortened. Read the full incident on IFTTT's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-02-20 17:20 UTC

   The Dropbox service is experiencing an elevated level of Applet run errors, and we're currently investigating the issue.

2. monitoring 2025-02-21 13:35 UTC

   This issue appears to be resolved by Dropbox and we are continuing to monitor.

3. resolved 2025-02-21 22:35 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on IFTTT's status page.

Affected: Applet performance

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-02-14 22:17 UTC

   Paused services may be experiencing technical difficulties. All Applets using these services will resume once the technical difficulties are resolved.

2. resolved 2025-02-20 17:22 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on IFTTT's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-01-09 01:11 UTC

   We're currently investigating an issue that is preventing some users from receiving messages sent by the SMS service's send me an SMS action.

2. resolved 2025-01-11 18:28 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on IFTTT's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-12-04 21:11 UTC

   Paused services may be experiencing technical difficulties. All Applets using these services will resume once the technical difficulties are resolved.

2. monitoring 2024-12-16 17:12 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2024-12-17 17:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on IFTTT's status page.

Affected: IFTTT.com, IFTTT mobile apps, Applet performance

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2024-11-05 22:46 UTC

   We're currently investigating an issue that is preventing the actions for the Email and Email Digest services from sending emails.

2. monitoring 2024-11-07 22:28 UTC

   A fix has been implemented and we are monitoring the results.

3. investigating 2024-11-08 18:40 UTC

   We're currently investigating an issue that is preventing the actions for the Email and Email Digest services from sending emails.

4. monitoring 2024-11-08 21:47 UTC

   A fix has been implemented and we are monitoring the results.

5. resolved 2024-12-04 22:08 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on IFTTT's status page.

Failure mode: A configuration change caused the failure. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2024-10-23 11:23 UTC

   The SoundCloud integration is currently undergoing maintenance to align with the latest requirements of the SoundCloud API. For the duration of the maintenance: * Applet executions with SoundCloud triggers and actions are paused * Users are not able to connect or reconnect their...

2. identified 2024-10-23 18:02 UTC

   SoundCloud integration is operational right now. Maintenance will resume tomorrow.

3. identified 2024-10-24 11:42 UTC

   We are resuming maintenance work on the SoundCloud integration.

4. monitoring 2024-10-24 18:09 UTC

   Maintenance is complete. SoundCloud Applets resumed running. We will be making the integration available again to new users and for reconnecting in the nearest future.

5. resolved 2024-10-24 19:21 UTC

   The SoundCloud integration is fully functional and generally available again following maintenance.

Excerpts are shortened. Read the full incident on IFTTT's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-10-15 13:27 UTC

   Paused services may be experiencing technical difficulties. All Applets using these services will resume once the technical difficulties are resolved.

2. monitoring 2024-10-16 11:19 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2024-10-23 11:19 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on IFTTT's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-09-17 16:30 UTC

   The service's triggers may be experiencing technical difficulties. Once the technical difficulties are resolved, all applets using these services will resume.

2. resolved 2024-10-07 16:26 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on IFTTT's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2024-09-04 18:19 UTC

   Paused services may be experiencing technical difficulties. All Applets using these services will resume once the technical difficulties are resolved.

2. monitoring 2024-09-04 20:54 UTC

   A fix has been implemented and we are monitoring the results.

3. identified 2024-09-09 23:03 UTC

   The issue has been identified and a fix is being implemented.

4. monitoring 2024-09-13 21:14 UTC

   A fix has been implemented and we are monitoring the results.

5. resolved 2024-09-20 20:34 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on IFTTT's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2024-08-29 18:09 UTC

   Paused services may be experiencing technical difficulties. All Applets using these services will resume once the technical difficulties are resolved.

2. monitoring 2024-09-12 23:05 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2024-09-20 20:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on IFTTT's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-06-10 22:53 UTC

   We're currently investigating an issue that is preventing some users from receiving messages sent by the SMS service's send me an SMS action

2. resolved 2024-06-12 16:47 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on IFTTT's status page.

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-06-03 15:28 UTC

   We're currently investigating an issue that is preventing some Applets that include filter code from running as expected, as well as saving filter code changes when creating or editing Applets.

2. monitoring 2024-06-03 15:44 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2024-06-03 18:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on IFTTT's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-05-30 03:24 UTC

   We're currently investigating an issue that is preventing some Applets that include filter code from running as expected.

2. monitoring 2024-05-30 04:30 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2024-05-30 05:04 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on IFTTT's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-04-29 20:11 UTC

   Paused services may be experiencing technical difficulties. All Applets using these services will resume once the technical difficulties are resolved.

2. monitoring 2024-04-30 08:30 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2024-05-06 18:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on IFTTT's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-04-25 20:03 UTC

   We're currently investigating an issue that is preventing the Webhooks service "Receive a web request" and "Receive a web request with a JSON payload" triggers from running as expected.

2. monitoring 2024-04-25 20:23 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2024-04-26 16:20 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on IFTTT's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-04-23 18:08 UTC

   We're currently investigating an issue that is preventing some users from receiving messages sent by the SMS service's send me an SMS action

2. resolved 2024-04-25 16:02 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on IFTTT's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2024-03-21 15:30 UTC

   We are investigating an issue that prevented some Applets using the IFTTT Email service's Send me an email action from running between March 21st to March 22nd. This issue has now been resolved and Email actions should be running as expected.

Excerpts are shortened. Read the full incident on IFTTT's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-03-01 23:25 UTC

   We're currently investigating an issue that is preventing users from connecting to the Instagram service.

2. investigating 2024-03-04 20:12 UTC

   We're currently investigating an issue that is preventing some users from connecting to the Instagram service and Instagram & Facebook Applets from running as expected.

3. monitoring 2024-03-08 19:49 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2024-03-13 16:22 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on IFTTT's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2024-03-01 15:58 UTC

   The Google Assistant service is currently experiencing issues with its triggers.

2. monitoring 2024-03-01 17:28 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2024-03-01 22:19 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on IFTTT's status page.

Affected: Applet performance

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-02-22 16:55 UTC

   We're experiencing an elevated level of Applet run errors and are currently looking into the issue.

2. identified 2024-02-22 18:00 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2024-02-22 18:01 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2024-02-23 20:08 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on IFTTT's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-02-14 17:41 UTC

   We're currently investigating an issue that is preventing some users from connecting to the Facebook Pages service and some Facebook Pages Applets from running as expected.

2. monitoring 2024-02-21 21:59 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2024-02-22 20:53 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on IFTTT's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-02-12 17:45 UTC

   Paused services may be experiencing technical difficulties. All Applets using these services will resume once the technical difficulties are resolved.

2. monitoring 2024-02-12 19:01 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2024-02-23 19:40 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on IFTTT's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-01-29 08:41 UTC

   Paused services may be experiencing technical difficulties. All Applets using these services will resume once the technical difficulties are resolved.

2. monitoring 2024-02-12 17:46 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2024-02-23 18:02 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on IFTTT's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-01-22 18:21 UTC

   We're currently investigating an issue that is preventing some users from connecting to the Discord service and some Discord Applets from running as expected.

2. monitoring 2024-01-22 22:20 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2024-02-07 19:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on IFTTT's status page.

Affected: IFTTT.com, IFTTT mobile apps, Applet performance

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-01-22 15:27 UTC

   We're experiencing issues across IFTTT.com and the IFTTT mobile apps. We are currently looking into the issue.

2. monitoring 2024-01-22 15:56 UTC

   A fix has been implemented and we are monitoring the results.

3. monitoring 2024-01-22 16:28 UTC

   We are continuing to monitor for any further issues.

4. monitoring 2024-01-22 17:11 UTC

   We are continuing to monitor for any further issues.

5. resolved 2024-01-22 18:19 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on IFTTT's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-01-16 15:24 UTC

   Paused services may be experiencing technical difficulties. All Applets using these services will resume once the technical difficulties are resolved.

2. monitoring 2024-01-16 16:29 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2024-01-18 15:02 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on IFTTT's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-01-15 20:13 UTC

   We're currently investigating an issue that is preventing some users from connecting to the Facebook Pages service and some Facebook Pages Applets from running as expected.

2. monitoring 2024-01-16 18:42 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2024-01-18 15:02 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on IFTTT's status page.