Is IFTTT Down?

No — IFTTT is up

Reachable from all 8 checked regions

Average response time: 150ms

Last checked 1 hour ago · checks run every 6 hours

Official status page: https://status.ifttt.com

IFTTT uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

59ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 26 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

26-day clean streak

Aug 22 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams

150ms

DNS 127ms TCP 2ms TLS 7ms TTFB 142ms

arn

215ms

DNS 200ms TCP 1ms TLS 4ms TTFB 209ms

bom

34ms

DNS 11ms TCP 2ms TLS 5ms TTFB 24ms

cdg

92ms

DNS 70ms TCP 1ms TLS 4ms TTFB 80ms

dfw

112ms

DNS 94ms TCP 1ms TLS 4ms TTFB 104ms

ewr

117ms

DNS 99ms TCP 1ms TLS 4ms TTFB 109ms

fra

76ms

DNS 55ms TCP 1ms TLS 3ms TTFB 68ms

gru

406ms

DNS 390ms TCP 1ms TLS 3ms TTFB 399ms

What IFTTT does

IFTTT connects apps and devices through automations called Applets, which run when a trigger fires in one service and act on another. Consumers use it for smart home routines and social posting, and small businesses for light integration between tools that do not otherwise talk to each other. The automation runs unattended, which is what makes failure quiet.

What an outage looks like

Applets stop running, so the automation is absent rather than visibly broken: a light does not come on, a post is never made, a row is never appended. The site and mobile apps may fail to load. Applets can also stall because a single connected service is in maintenance while IFTTT itself is entirely healthy.

What to do about it

Check IFTTT's status page, which reports IFTTT.com, the mobile apps and Applet performance as three separate components, so the site can be unreachable while automations still run. IFTTT also schedules maintenance per connected service, during which Applets using that service do not run. If one Applet alone is failing, refresh its connection to the service.

Is it down for everyone, or just you?

If this page says IFTTT is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 18 cities across three regions to find out where it breaks.

Test it yourself

Related services

IFTTT outage FAQ

Do missed Applets run later?

Assume not. Applets fire on a trigger, and a trigger that occurs while IFTTT cannot act on it is generally not replayed once service returns. Time-sensitive automations lose that occurrence outright. Anything you need guaranteed, such as a payment or a critical alert, is a poor fit for a best-effort automation layer.

One Applet is broken but the rest work. Is that an outage?

Probably not. IFTTT disables Applets and connections for reasons specific to the connected service, such as an expired authorisation, and its help centre points to refreshing the connection used by the trigger as the first step. A platform incident tends to affect Applet performance broadly rather than one Applet in isolation.

Can IFTTT be up while my automation still fails?

Yes, and this is the common case. IFTTT schedules maintenance per service: a window on the X service, for instance, stops Applets using it while everything else keeps running. The Applet performance component covers IFTTT's own execution, not the availability of every third party it connects to.

Does the mobile app work when the site is down?

They are reported as separate components, so sometimes. IFTTT.com and IFTTT mobile apps have their own rows. In practice they often fail together, as in the August 2026 incident affecting loading of both, but a fault in one alone does happen and is worth checking before assuming everything is out.

How we measure this

We request IFTTT's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where IFTTT publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when IFTTT goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required