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 50 min ago. Last stored result reached it in 85 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 15 | 0 | 0.0 | 192 ms | 0 |
| Mon 17 | 0 | 0.0 | 147 ms | 0 |
| Mon 20 | 0 | 0.0 | 90 ms | 0 |
| Mon 22 | 0 | 0.0 | 68 ms | 0 |
| Tue 00 | 0 | 0.0 | 85 ms | 0 |
| Tue 02 | 0 | 0.0 | 57 ms | 0 |
| Tue 04 | 0 | 0.0 | 80 ms | 0 |
| Tue 06 | 0 | 0.0 | 121 ms | 0 |
| Tue 08 | 0 | 0.0 | 117 ms | 0 |
| Tue 10 | 0 | 0.0 | 53 ms | 0 |
| Tue 12 | 0 | 0.0 | 74 ms | 0 |
| Tue 14 | 0 | 0.0 | 166 ms | 0 |
| Tue 17 | 0 | 0.0 | 174 ms | 0 |
| Tue 19 | 0 | 0.0 | 82 ms | 0 |
| Tue 21 | 0 | 0.0 | 36 ms | 0 |
| Tue 23 | 0 | 0.0 | 93 ms | 0 |
| Wed 01 | 0 | 0.0 | 70 ms | 0 |
| Wed 04 | 0 | 0.0 | 122 ms | 0 |
| Wed 06 | 0 | 0.0 | 42 ms | 0 |
| Wed 08 | 0 | 0.0 | 37 ms | 0 |
| Wed 10 | 0 | 0.0 | 49 ms | 0 |
| Wed 13 | 0 | 0.0 | 66 ms | 0 |
| Wed 15 | 0 | 0.0 | 178 ms | 0 |
| Wed 17 | 0 | 0.0 | 169 ms | 0 |
| Wed 19 | 0 | 0.0 | 65 ms | 0 |
| Wed 21 | 0 | 0.0 | 108 ms | 0 |
| Wed 23 | 0 | 0.0 | 46 ms | 0 |
| Thu 02 | 0 | 0.0 | 116 ms | 0 |
| Thu 04 | 0 | 0.0 | 164 ms | 0 |
| Thu 06 | 0 | 0.0 | 96 ms | 0 |
| Thu 08 | 0 | 0.0 | 201 ms | 0 |
| Thu 10 | 0 | 0.0 | 71 ms | 0 |
| Thu 12 | 0 | 0.0 | 36 ms | 0 |
| Thu 14 | 0 | 0.0 | 144 ms | 0 |
| Thu 16 | 0 | 0.0 | 350 ms | 0 |
| Thu 18 | 0 | 0.0 | 65 ms | 0 |
| Thu 20 | 0 | 0.0 | 47 ms | 0 |
| Thu 22 | 0 | 0.0 | 88 ms | 0 |
| Fri 00 | 0 | 0.0 | 85 ms | 0 |
| Fri 02 | 0 | 0.0 | 72 ms | 0 |
| Fri 04 | 0 | 0.0 | 86 ms | 0 |
| Fri 06 | 0 | 0.0 | 119 ms | 0 |
| Fri 08 | 0 | 0.0 | 63 ms | 0 |
| Fri 10 | 0 | 0.0 | 133 ms | 0 |
| Fri 11 | 0 | 0.0 | 89 ms | 0 |
| Fri 13 | 0 | 0.0 | 145 ms | 0 |
| Fri 15 | 0 | 0.0 | 169 ms | 0 |
| Fri 17 | 0 | 0.0 | 85 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 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for movingimage 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 movingimage goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send movingimage alerts to Slack, Discord or a webhook — free.
We track movingimage (movingimage.com) as part of the AI group. Enterprise Communications Platform with Agentic AI, Video, and Livestreaming. Streamline workflows, create content, and deliver messages securely.
movingimage publishes an official status page at status.movingimage.com; 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 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 96 ms average, 47–169 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 movingimage incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
96 ms on average over the last 24 hours (47–169 ms).
Yes, at https://status.movingimage.com.
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 movingimage here at once, the problem is on movingimage'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 movingimage. 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.