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 2 hr ago. Last stored result reached it in 145 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 17 | 0 | 0.0 | 132 ms | 0 |
| Tue 19 | 0 | 0.0 | 120 ms | 0 |
| Tue 21 | 0 | 0.0 | 264 ms | 0 |
| Wed 00 | 0 | 0.0 | 77 ms | 0 |
| Wed 02 | 0 | 0.0 | 335 ms | 0 |
| Wed 04 | 0 | 0.0 | 131 ms | 0 |
| Wed 06 | 0 | 0.0 | 73 ms | 0 |
| Wed 09 | 0 | 0.0 | 67 ms | 0 |
| Wed 11 | 0 | 0.0 | 112 ms | 0 |
| Wed 13 | 0 | 0.0 | 89 ms | 0 |
| Wed 15 | 0 | 0.0 | 131 ms | 0 |
| Wed 17 | 0 | 0.0 | 208 ms | 0 |
| Wed 19 | 0 | 0.0 | 200 ms | 0 |
| Wed 22 | 0 | 0.0 | 205 ms | 0 |
| Thu 00 | 0 | 0.0 | 148 ms | 0 |
| Thu 02 | 0 | 0.0 | 163 ms | 0 |
| Thu 03 | 0 | 0.0 | 148 ms | 0 |
| Thu 05 | 0 | 0.0 | 159 ms | 0 |
| Thu 07 | 0 | 0.0 | 176 ms | 0 |
| Thu 09 | 0 | 0.0 | 104 ms | 0 |
| Thu 11 | 0 | 0.0 | 176 ms | 0 |
| Thu 13 | 0 | 0.0 | 126 ms | 0 |
| Thu 15 | 0 | 0.0 | 153 ms | 0 |
| Thu 17 | 0 | 0.0 | 162 ms | 0 |
| Thu 19 | 0 | 0.0 | 192 ms | 0 |
| Thu 21 | 0 | 0.0 | 164 ms | 0 |
| Thu 23 | 0 | 0.0 | 117 ms | 0 |
| Fri 01 | 0 | 0.0 | 223 ms | 0 |
| Fri 03 | 0 | 0.0 | 198 ms | 0 |
| Fri 05 | 0 | 0.0 | 156 ms | 0 |
| Fri 07 | 0 | 0.0 | 120 ms | 0 |
| Fri 09 | 0 | 0.0 | 138 ms | 0 |
| Fri 10 | 0 | 0.0 | 141 ms | 0 |
| Fri 11 | 0 | 0.0 | 165 ms | 0 |
| Fri 13 | 0 | 0.0 | 175 ms | 0 |
| Fri 15 | 0 | 0.0 | 209 ms | 0 |
| Fri 17 | 0 | 0.0 | 217 ms | 0 |
| Fri 19 | 0 | 0.0 | 149 ms | 0 |
| Fri 20 | 0 | 0.0 | 172 ms | 0 |
| Fri 21 | 0 | 0.0 | 154 ms | 0 |
| Fri 22 | 0 | 0.0 | 220 ms | 0 |
| Fri 23 | 0 | 0.0 | 183 ms | 0 |
| Sat 01 | 0 | 0.0 | 185 ms | 0 |
| Sat 03 | 0 | 0.0 | 146 ms | 0 |
| Sat 05 | 0 | 0.0 | 159 ms | 0 |
| Sat 07 | 0 | 0.0 | 159 ms | 0 |
| Sat 08 | 0 | 0.0 | 192 ms | 0 |
| Sat 10 | 0 | 0.0 | 146 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 9 days of data so far, so the 90-day numbers fill in over time.
No outages on record for getimg.ai 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 getimg.ai goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send getimg.ai alerts to Slack, Discord or a webhook — free.
getimg.ai is listed in our AI category and checked at getimg.ai. Create and edit images, video, music, speech, and sound effects with leading AI models in one workspace—without model research or complex setup.
getimg.ai publishes an official status page at status.getimg.ai; 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 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 171 ms average, 140–220 ms range across 17 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public getimg.ai incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
171 ms on average over the last 24 hours (140–220 ms).
Yes, at https://status.getimg.ai.
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 getimg.ai here at once, the problem is on getimg.ai'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 getimg.ai. 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.