Home
Services
IFTTT

IFTTT ifttt.com

Is IFTTT down right now? Live status and outage tracker

No, IFTTT is up.

No outage detected, and no user reports in the last hour.

IFTTT's own status page: status.ifttt.com

Live Updated 1 min ago Data refreshes every 5 minutes

Not working for you? Official status pageStatus page

User reports, last 24 hours, 15 minutes a segment: 96 flowing 0 slow (elevated) 0 jammed (outage)

User reports, last 24 hours

No reports in this window

No problem reports came in for IFTTT in the last hour, and at this time of day there are usually almost none. There has been no spike in reports since 29 October. These are user reports from the US, where most people report IFTTT problems.

NormalClose to the usual level24 h · 0 reports
ElevatedMore than 1.5 times the usual levelNone in this chart
OutageMore than twice the usual level and far above the day's averageNone in this chart
Usual levelWhat a usual day sees at that timeAlmost none at this time of day

Reports, last hour

Quiet

Uptime, 24 h

100.00%

No outage windows

Last outage

None

In the last 24 hours

Busiest 15 minutes

No reports

Last 24 hours

IFTTT outages and problems

No user reports came in for IFTTT in the past 24 hours, and its uptime over that window is 100.00%.

No 15-minute window had any reports at all, so the chart above stays flat.

No problems detected in the last 24 hoursReports for IFTTT stayed at their usual level the whole time.

Official status

What IFTTT's status page says

Checking status.ifttt.com…

Report categories

What people can report about IFTTT

People who report a problem with IFTTT to the outage-report feed behind this page can tag what is affected. These are the categories they can pick; the feed shows no counts per category:

Website
Login
App

World map

Where IFTTT problem reports come from

The map shows where recent problem reports for IFTTT came from in the US. Big cities always send the most, so dots in many places point to a widespread problem, and one area far ahead of the rest can mean a regional one.

Outage now
Problems now
Normal

Each dot is a group of recent reports, coloured by how its country is doing now; bigger dots, more reports.

Map outlines: Natural Earth.

Last 30 days

IFTTT problem spikes, last 30 days

Since 29 October, IFTTT had no outage spikes or periods of elevated reports.

A spike is a sharp rise in problem reports from users, kept exactly as this page showed it at the time. This history starts on 29 October 2026. Monthly reports for all services

Troubleshooting

How to fix IFTTT not working

IFTTT is up on our end, so if it won't work for you, the problem is most likely on your side. Work through these in order:

Your browser tries to reach ifttt.com over your own connection, right now. Nothing is sent to us or stored.

Check the official status page
Open status.ifttt.com and read the status at the top of the page. It shows whether user problem reports are above their usual level, counted in 15-minute windows over the last 24 hours; the page does not ping the service itself. If reports are elevated, give it time and try again.
Open the applet's activity log
Go to My Applets and open the failing applet. Tap or click View activity to see recent runs and the step that failed, which tells you whether the trigger or the action is at fault. Make sure the applet is switched on.
Reconnect the broken service
Open the applet and go to Settings, then find the service showing the error and choose Reconnect. Sign in to that service again; a stale connection is a common cause of silent failures, and reconnecting refreshes it without rebuilding the applet. Test the applet after you reconnect.
Test the trigger outside the app
Trigger the source yourself: send an email to the address that feeds the applet, or toggle the smart device that starts the flow. If the source works on its own but the applet still does not fire, open the help centre at help.ifttt.com and search the error text from the activity log. Include the applet name and the service that failed when you contact support.

While IFTTT is down: what to use instead

Zapier If both apps you need are supported there, use Zapier to pass a trigger from one service to an action in another.
Make Make can link supported apps with visual workflows.
Apple Shortcuts On iPhone, Apple Shortcuts can automate tasks across compatible apps and built-in features when the workflow stays on your device.
Power Automate Power Automate can connect supported Microsoft apps for work tasks.

Your device

Fix IFTTT on Windows, Mac, Android and iPhone

IFTTT on Windows

Fix: Clear your browser cache, disable conflicting extensions, and ensure your Windows Defender or firewall settings aren't blocking IFTTT. You can also try flushing your DNS cache to resolve connection issues.
Check: Check if the IFTTT website loads in your browser, or use the ping utility in the command line to test connectivity to the IFTTT servers. If other websites load but IFTTT does not, the service may be experiencing an outage.

Command Prompt

ping ifttt.comTest whether IFTTT's servers reply

nslookup ifttt.comCheck that IFTTT's DNS resolves

tracert ifttt.comTrace where the connection drops

ipconfig /flushdnsClear the DNS cache, then reload

IFTTT on Mac

Fix: Try clearing website data in Safari or Chrome, and verify that your macOS firewall or third-party security software is not blocking IFTTT. Restarting your browser or switching to a different network can also resolve connection drops.
Check: Verify if the IFTTT web portal loads in Safari, and use network diagnostics to test server connectivity. If the page fails to load across multiple browsers, IFTTT might be facing a server issue.

Terminal

ping -c 4 ifttt.comTest whether IFTTT's servers reply

nslookup ifttt.comCheck that IFTTT's DNS resolves

traceroute ifttt.comTrace where the connection drops

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponderFlush the macOS DNS cache, then reload

IFTTT on Android

Fix: Force stop the IFTTT app in your settings, clear its cache, and ensure you have the latest version installed from the Google Play Store. If issues persist, try toggling between Wi-Fi and mobile data to rule out network problems.
Check: Check if the IFTTT app displays connection errors or fails to trigger applets on your device. If the app fails to connect while other internet-dependent apps work fine, the service is likely down.

IFTTT on iPhone and iPad

Fix: Restart the IFTTT app by swiping it closed from the App Switcher, and check the App Store for any pending updates. Reinstalling the app or resetting your network settings can also resolve persistent connection issues.
Check: Open the IFTTT app to see if your applets fail to load or sync, or check if the IFTTT widget displays connection errors. If the app fails to connect while other apps work online, IFTTT is likely down.

About

What happens when IFTTT goes down

IFTTT is an automation service that connects apps and devices through Applets, and if you use it for smart home routines and social posts, an outage interrupts those triggers and actions. The report level above comes from user problem reports counted in 15-minute windows over the last 24 hours; this site does not ping or monitor the service itself.

Applets that rely on a specific trigger or action stop running, and your run history shows failed runs or no runs at all. The app may not load your applets or activity. Trigger problems often show up first, because a trigger that never fires cannot pass anything to the action, while action problems leave the trigger working but the final step never happens. It is often partial: one connection can fail while another keeps working, and a regional outage in a connected service breaks only the applets that use it.

Servers and network

IFTTT IP address, servers and network

IPv4 addresses: 13.32.121.19
Show all 4
13.32.121.67
13.32.121.78
13.32.121.85
IPv6 addresses: 2600:9000:2240:6600:1:b1c6:9e40:93a1
Show all 8
2600:9000:2240:ac00:1:b1c6:9e40:93a1
2600:9000:236e:2800:1:b1c6:9e40:93a1
2600:9000:236e:aa00:1:b1c6:9e40:93a1
2600:9000:236e:c800:1:b1c6:9e40:93a1
2600:9000:236e:d400:1:b1c6:9e40:93a1
2600:9000:236e:dc00:1:b1c6:9e40:93a1
2600:9000:236e:fc00:1:b1c6:9e40:93a1
Network: AS16509 · Amazon.com, Inc., registered in the United States
Served through: Amazon CloudFront · our check was answered by its Frankfurt (FRA) data centre
DNS hosted by: Amazon Route 53
HTTPS certificate: Issued by Amazon, valid until 15 Apr 2027 (165 days)
HTTP/3: Not advertised
Our check: Answered in 34 ms

Checked from our server in Frankfurt, Germany, 6 days ago, for ifttt.com. A service behind a CDN answers from many data centres, usually the one nearest to you, so these addresses are where its traffic enters, not where its own servers stand. Visitors elsewhere may see different addresses.

Checked from 11 places around the world

All 11 locations got an answer from ifttt.com. Fastest from Milan (12 ms), slowest from Warsaw (107 ms). Every location connected through Amazon.com, Inc. (AS16509), using 9 different addresses.

Location	Result	Time	Address reached
FrankfurtGermany	Up	23 ms	13.32.121.85data centre in Frankfurt
ViennaAustria	Up	36 ms	99.84.91.77data centre in Vienna
MilanItaly	Up	12 ms	13.32.220.111data centre in Milan
ParisFrance	Up	36 ms	52.84.174.114data centre in Paris
AmsterdamNetherlands	Up	86 ms	52.84.174.114data centre in Paris
MadridSpain	Up	26 ms	65.8.202.78data centre in Madrid
WarsawPoland	Up	107 ms	13.32.121.85data centre in Frankfurt
Los AngelesUSA	Up	28 ms	18.65.25.82data centre in Los Angeles
São PauloBrazil	Up	54 ms	13.33.94.7data centre in Rio de Janeiro
SingaporeSingapore	Up	22 ms	13.35.163.81data centre in Singapore
TokyoJapan	Up	26 ms	3.165.39.37data centre in Tokyo

Checked with check-host.net from its servers in these cities 6 days ago, for ifttt.com. Time is how long each server took to load the page. Data-centre cities come from the names the network gives its servers.

Questions

IFTTT FAQ

Is IFTTT down right now?

The status at the top of this page shows whether user problem reports for IFTTT are above their usual level, counted in 15-minute windows over the last 24 hours. The site does not ping or monitor the service itself. Check the official status page, then try another network and open the app on a second device to see if the trouble follows you.

Why does an applet say it failed when the service itself looks fine?

An applet can fail when its trigger fires but the action service rejects the request, so one broken connection does not mean the whole service is down. Open the applet and reconnect the service that shows an error. If only that applet fails, the fault sits with its trigger or action.

Why do my IFTTT notifications arrive late or not at all?

Phone battery settings can pause the mobile app, so notifications from applets arrive late or never show. Check that notifications are allowed for the app and that background app refresh is on. Then run one applet and watch for the alert on the phone.

I cannot sign in to my IFTTT account after changing my password. What should I check?

Password managers often keep the old password, so the app keeps rejecting the new one. Sign out fully and clear the saved login for the app; open the password reset link in the same browser. If the email never arrives, check spam and any rules that move mail out of the inbox.

Why was my IFTTT Pro subscription charged after I cancelled?

Cancelling stops the next renewal, but a charge can still land if you cancelled near the billing date or through the app store instead of the web account. Check the subscription in the store that handles the payment and compare it with the billing settings in your account. The help centre can trace a charge that looks wrong.

For your site

Put the IFTTT status badge on your site

Paste one of these into a web page, a blog post or a README. The badge shows the same status as this page, based on user problem reports. Browsers can keep a copy for up to 4 hours. It links back here.

HTML

<a href="https://isitdownrightnow.app/services/ifttt/"><img src="https://isitdownrightnow.app/badge/ifttt.svg" alt="IFTTT status" height="20"></a>

Markdown, for README files

[![IFTTT status](https://isitdownrightnow.app/badge/ifttt.svg)](https://isitdownrightnow.app/services/ifttt/)

The badge is a plain image: no scripts, no cookies. People who see it on your page load it from our server.

How we track IFTTT

The status on this page comes from user-submitted problem reports for IFTTT, counted in 15-minute windows over the last 24 hours. Each window is compared with the normal level for IFTTT, so a few complaints on a quiet day don't trigger anything, but a sudden jump well above normal does.

When reports climb well above normal, the status here changes to partial outage or major outage and the chart moves with it. This is separate from IFTTT's official status page: user reports tend to show a problem early, while the official page confirms the cause. If the two disagree, check both.