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 1 hr ago. Last stored result reached it in 467 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 | 373 ms | 0 |
| Tue 00 | 0 | 0.0 | 351 ms | 0 |
| Tue 02 | 0 | 0.0 | 429 ms | 0 |
| Tue 04 | 0 | 0.0 | 303 ms | 0 |
| Tue 06 | 0 | 0.0 | 379 ms | 0 |
| Tue 08 | 0 | 0.0 | 343 ms | 0 |
| Tue 11 | 0 | 0.0 | 423 ms | 0 |
| Tue 13 | 0 | 0.0 | 484 ms | 0 |
| Tue 15 | 0 | 0.0 | 473 ms | 0 |
| Tue 17 | 0 | 0.0 | 492 ms | 0 |
| Tue 19 | 0 | 0.0 | 465 ms | 0 |
| Tue 22 | 0 | 0.0 | 440 ms | 0 |
| Wed 00 | 0 | 0.0 | 326 ms | 0 |
| Wed 02 | 0 | 0.0 | 542 ms | 0 |
| Wed 04 | 0 | 0.0 | 604 ms | 0 |
| Wed 07 | 0 | 0.0 | 442 ms | 0 |
| Wed 09 | 0 | 0.0 | 389 ms | 0 |
| Wed 11 | 0 | 0.0 | 433 ms | 0 |
| Wed 13 | 0 | 0.0 | 466 ms | 0 |
| Wed 15 | 0 | 0.0 | 400 ms | 0 |
| Wed 17 | 0 | 0.0 | 413 ms | 0 |
| Wed 20 | 0 | 0.0 | 447 ms | 0 |
| Wed 22 | 0 | 0.0 | 599 ms | 0 |
| Thu 00 | 0 | 0.0 | 447 ms | 0 |
| Thu 02 | 0 | 0.0 | 352 ms | 0 |
| Thu 04 | 0 | 0.0 | 414 ms | 0 |
| Thu 06 | 0 | 0.0 | 464 ms | 0 |
| Thu 08 | 0 | 0.0 | 467 ms | 0 |
| Thu 10 | 0 | 0.0 | 335 ms | 0 |
| Thu 12 | 0 | 0.0 | 372 ms | 0 |
| Thu 14 | 0 | 0.0 | 555 ms | 0 |
| Thu 17 | 0 | 0.0 | 498 ms | 0 |
| Thu 19 | 0 | 0.0 | 375 ms | 0 |
| Thu 21 | 0 | 0.0 | 431 ms | 0 |
| Thu 23 | 0 | 0.0 | 427 ms | 0 |
| Fri 01 | 0 | 0.0 | 469 ms | 0 |
| Fri 03 | 0 | 0.0 | 487 ms | 0 |
| Fri 05 | 0 | 0.0 | 408 ms | 0 |
| Fri 07 | 0 | 0.0 | 643 ms | 0 |
| Fri 09 | 0 | 0.0 | 355 ms | 0 |
| Fri 10 | 0 | 0.0 | 598 ms | 0 |
| Fri 11 | 0 | 0.0 | 350 ms | 0 |
| Fri 13 | 0 | 0.0 | 467 ms | 0 |
| Fri 15 | 0 | 0.0 | 312 ms | 0 |
| Fri 17 | 0 | 0.0 | 418 ms | 0 |
| Fri 19 | 0 | 0.0 | 418 ms | 0 |
| Fri 20 | 0 | 0.0 | 522 ms | 0 |
| Fri 22 | 0 | 0.0 | 467 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 Imagine 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 Imagine goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Imagine alerts to Slack, Discord or a webhook — free.
We track Imagine (imagine.art) as part of the AI group. Generate controllable, consistent visual assets at scale with 50+ AI image and video models in one platform. Built for teams that ship creative fast.
Imagine publishes an official status page at status.imagine.art; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong 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: 455 ms average, 312–643 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Imagine incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
455 ms on average over the last 24 hours (312–643 ms).
Yes, at https://status.imagine.art.
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 Imagine here at once, the problem is on Imagine'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 Imagine. 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.