User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Productivity
ifttt.com · Productivity
Is IFTTT down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what to try.
Your browser → ifttt.com—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
Live outage map
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses, and places with fewer than 3 reports are not shown. Updates every minute.
What's broken
Our checks
Reaching it
Last check reached it in 153 ms · 6 min ago.
Official status
All clear
All Systems Operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 20:30 | 0 | 0.0 | 310 ms | 0 |
| 20:45 | 0 | 0.0 | 195 ms | 0 |
| 21:00 | 0 | 0.0 | 228 ms | 0 |
| 21:15 | 0 | 0.0 | 360 ms | 0 |
| 21:30 | 0 | 0.0 | 222 ms | 0 |
| 21:45 | 0 | 0.0 | 255 ms | 0 |
| 22:00 | 0 | 0.0 | 332 ms | 0 |
| 22:15 | 0 | 0.0 | 393 ms | 0 |
| 22:30 | 0 | 0.0 | 306 ms | 0 |
| 22:45 | 0 | 0.0 | 222 ms | 0 |
| 23:00 | 0 | 0.0 | 255 ms | 0 |
| 23:15 | 0 | 0.0 | 201 ms | 0 |
| 23:30 | 0 | 0.0 | 178 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live IFTTT badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for IFTTT yet. Outages of 10 minutes or more get their own page here.
Having trouble with IFTTT?
One report per service every 10 minutes from this network. No account.
Follow IFTTT
Get an email when IFTTT goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send IFTTT alerts to Slack, Discord or a webhook — free.
About IFTTT
IFTTT, at ifttt.com, is one of the Productivity services we monitor. IFTTT connects apps and devices with applets that trigger automatically.
IFTTT publishes an official status page at status.ifttt.com; when we can read it, its incident level is folded into the status shown here.
Common problems people hit with IFTTT: applets not running, service connections failing, and delays.
Measured uptime from our checks: 100% over 1 day of checks. No public incidents logged since monitoring began 1 day ago.
Response time over the last 24 hours: 268 ms average, 67–547 ms range across 24 successful checks.
Questions
Is IFTTT down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was IFTTT last down?
We have not recorded a public IFTTT incident since monitoring began 1 day ago.
What is IFTTT's uptime?
From our own checks: 100% over 1 day of checks.
How fast does IFTTT respond?
268 ms on average over the last 24 hours (67–547 ms).
Does IFTTT have an official status page?
Yes, at https://status.ifttt.com.
IFTTT not working for me but the status is fine. What now?
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For IFTTT, watch for applets not running, service connections failing, and delays. If many people report IFTTT here at once, the problem is on IFTTT's side.