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 1582 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 7 | 0 | 0.0 | 610 ms | 0 |
| Nov 7 | 0 | 0.0 | 1112 ms | 0 |
| Nov 8 | 0 | 0.0 | 674 ms | 0 |
| Nov 8 | 0 | 0.0 | 661 ms | 0 |
| Nov 8 | 0 | 0.0 | 158 ms | 0 |
| Nov 8 | 0 | 0.0 | 677 ms | 0 |
| Nov 9 | 0 | 0.0 | 661 ms | 0 |
| Nov 9 | 0 | 0.0 | 151 ms | 0 |
| Nov 9 | 0 | 0.0 | 625 ms | 0 |
| Nov 9 | 0 | 0.0 | 1280 ms | 0 |
| Nov 10 | 0 | 0.0 | 312 ms | 0 |
| Nov 10 | 0 | 0.0 | 194 ms | 0 |
| Nov 10 | 0 | 0.0 | 811 ms | 0 |
| Nov 10 | 0 | 0.0 | 551 ms | 0 |
| Nov 11 | 0 | 0.0 | 238 ms | 0 |
| Nov 11 | 0 | 0.0 | 109 ms | 0 |
| Nov 11 | 0 | 0.0 | 788 ms | 0 |
| Nov 11 | 0 | 0.0 | 193 ms | 0 |
| Nov 12 | 0 | 0.0 | 1027 ms | 0 |
| Nov 12 | 0 | 0.0 | 614 ms | 0 |
| Nov 12 | 0 | 0.0 | 948 ms | 0 |
| Nov 12 | 0 | 0.0 | 678 ms | 0 |
| Nov 13 | 0 | 0.0 | 208 ms | 0 |
| Nov 13 | 0 | 0.0 | 157 ms | 0 |
| Nov 13 | 0 | 0.0 | 734 ms | 0 |
| Nov 13 | 0 | 0.0 | 1582 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 VideoGen 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 VideoGen goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send VideoGen alerts to Slack, Discord or a webhook — free.
VideoGen, at videogen.io, is one of the AI services we monitor. Generate videos at scale while staying in control. Purpose-built AI workflows for marketing, e-commerce, training, explainers, and video presentations.
VideoGen publishes an official status page at status.videogen.io; when we can read it, its incident level is folded into the status shown here.
Common problems for 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: 551 ms average, 123–1582 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 VideoGen incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
551 ms on average over the last 24 hours (123–1582 ms).
Yes, at https://status.videogen.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 VideoGen here at once, the problem is on VideoGen'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 VideoGen. 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.