User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
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.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 48 min ago. Last stored result reached it in 166 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 22 | 0 | 0.0 | 1482 ms | 0 |
| Tue 00 | 0 | 0.0 | 203 ms | 0 |
| Tue 02 | 0 | 0.0 | 180 ms | 0 |
| Tue 04 | 0 | 0.0 | 447 ms | 0 |
| Tue 06 | 0 | 0.0 | 179 ms | 0 |
| Tue 08 | 0 | 0.0 | 186 ms | 0 |
| Tue 10 | 0 | 0.0 | 277 ms | 0 |
| Tue 12 | 0 | 0.0 | 663 ms | 0 |
| Tue 15 | 0 | 0.0 | 132 ms | 0 |
| Tue 17 | 0 | 0.0 | 303 ms | 0 |
| Tue 19 | 0 | 0.0 | 416 ms | 0 |
| Tue 21 | 0 | 0.0 | 578 ms | 0 |
| Wed 00 | 0 | 0.0 | 463 ms | 0 |
| Wed 02 | 0 | 0.0 | 224 ms | 0 |
| Wed 04 | 0 | 0.0 | 175 ms | 0 |
| Wed 06 | 0 | 0.0 | 465 ms | 0 |
| Wed 09 | 0 | 0.0 | 320 ms | 0 |
| Wed 11 | 0 | 0.0 | 611 ms | 0 |
| Wed 13 | 0 | 0.0 | 248 ms | 0 |
| Wed 15 | 0 | 0.0 | 1172 ms | 0 |
| Wed 17 | 0 | 0.0 | 295 ms | 0 |
| Wed 19 | 0 | 0.0 | 443 ms | 0 |
| Wed 22 | 0 | 0.0 | 289 ms | 0 |
| Thu 00 | 0 | 0.0 | 475 ms | 0 |
| Thu 02 | 0 | 0.0 | 279 ms | 0 |
| Thu 04 | 0 | 0.0 | 421 ms | 0 |
| Thu 06 | 0 | 0.0 | 273 ms | 0 |
| Thu 08 | 0 | 0.0 | 524 ms | 0 |
| Thu 10 | 0 | 0.0 | 441 ms | 0 |
| Thu 12 | 0 | 0.0 | 411 ms | 0 |
| Thu 14 | 0 | 0.0 | 212 ms | 0 |
| Thu 16 | 0 | 0.0 | 261 ms | 0 |
| Thu 18 | 0 | 0.0 | 298 ms | 0 |
| Thu 20 | 0 | 0.0 | 479 ms | 0 |
| Thu 23 | 0 | 0.0 | 452 ms | 0 |
| Fri 01 | 0 | 0.0 | 389 ms | 0 |
| Fri 03 | 0 | 0.0 | 162 ms | 0 |
| Fri 05 | 0 | 0.0 | 167 ms | 0 |
| Fri 07 | 0 | 0.0 | 290 ms | 0 |
| Fri 09 | 0 | 0.0 | 241 ms | 0 |
| Fri 11 | 0 | 0.0 | 1551 ms | 0 |
| Fri 13 | 0 | 0.0 | 217 ms | 0 |
| Fri 15 | 0 | 0.0 | 264 ms | 0 |
| Fri 17 | 0 | 0.0 | 379 ms | 0 |
| Fri 19 | 0 | 0.0 | 992 ms | 0 |
| Fri 21 | 0 | 0.0 | 246 ms | 0 |
| Fri 23 | 0 | 0.0 | 435 ms | 0 |
| Sat 01 | 0 | 0.0 | 166 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Idukki yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Idukki goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Idukki alerts to Slack, Discord or a webhook — free.
Idukki, at idukki.io, is one of the AI services we monitor. Idukki is a UGC platform for Shopify, WooCommerce, BigCommerce and Magento. Shoppable galleries, shoppable video and AI tagging in one 79 KB embed.
Idukki publishes an official status page at status.idukki.io; when we can read it, its incident level is folded into the status shown here.
Typical issues with AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 413 ms average, 162–1551 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Idukki incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
413 ms on average over the last 24 hours (162–1551 ms).
Yes, at https://status.idukki.io.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report Idukki here at once, the problem is on Idukki's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Idukki. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.