Is IFTTT Down?

No — IFTTT is up

IFTTT's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 466 ms

Right now

The verdict is the worse of these two. How we decide

IFTTT's status page

status.ifttt.com · read 4 minutes ago · checked every 3 minutes

Operational

IFTTT's components, as its status page reports them
Component	Status
IFTTT.com the service itself	Operational
IFTTT mobile apps	Operational
Applet performance	Operational

Open their status page

FlareWarden checks

ifttt.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 466 ms
Checked: 5 hours ago

By region

Amsterdam reachable, 246 ms
Chicago reachable, 241 ms
Paris reachable, 418 ms
San Jose reachable, 308 ms
Singapore reachable, 866 ms
Stockholm reachable, 173 ms
Sydney reachable, 1238 ms
Toronto reachable, 243 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Amsterdam	148 ms	4 ms	10 ms	227 ms
Chicago	165 ms	1 ms	3 ms	232 ms
Paris	157 ms	21 ms	23 ms	329 ms
San Jose	124 ms	2 ms	4 ms	296 ms
Singapore	145 ms	2 ms	4 ms	856 ms
Stockholm	43 ms	2 ms	4 ms	160 ms
Sydney	207 ms	1 ms	8 ms	1230 ms
Toronto	80 ms	8 ms	12 ms	207 ms

We check that ifttt.com loads, not every feature behind it. Test it yourself

History

Incidents IFTTT reported

Since Oct 22, 15 days · from status.ifttt.com

Incidents: 0
Major or critical: 0
Median to resolve: —

No incidents reported in this window.

IFTTT website availability

Measured by FlareWarden · ifttt.com

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 199ms

Last 30 days

72-day clean streak

Oct 7 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of ifttt.com from multiple regions every 6 hours. IFTTT's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 72 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

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 17 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. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
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. Our checks only change their 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, and the verdict is the worse of what it reports and what our checks see: a major outage of IFTTT itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when IFTTT goes down

We check IFTTT every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required