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 55 min ago. Last stored result reached it in 39 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 15 | 0 | 0.0 | 40 ms | 0 |
| Mon 18 | 0 | 0.0 | 209 ms | 0 |
| Mon 20 | 0 | 0.0 | 183 ms | 0 |
| Mon 22 | 0 | 0.0 | 64 ms | 0 |
| Tue 00 | 0 | 0.0 | 70 ms | 0 |
| Tue 02 | 0 | 0.0 | 162 ms | 0 |
| Tue 04 | 0 | 0.0 | 33 ms | 0 |
| Tue 06 | 0 | 0.0 | 127 ms | 0 |
| Tue 08 | 0 | 0.0 | 173 ms | 0 |
| Tue 11 | 0 | 0.0 | 189 ms | 0 |
| Tue 13 | 0 | 0.0 | 113 ms | 0 |
| Tue 15 | 0 | 0.0 | 396 ms | 0 |
| Tue 17 | 0 | 0.0 | 119 ms | 0 |
| Tue 19 | 0 | 0.0 | 107 ms | 0 |
| Tue 22 | 0 | 0.0 | 195 ms | 0 |
| Wed 00 | 0 | 0.0 | 124 ms | 0 |
| Wed 02 | 0 | 0.0 | 151 ms | 0 |
| Wed 04 | 0 | 0.0 | 65 ms | 0 |
| Wed 07 | 0 | 0.0 | 69 ms | 0 |
| Wed 09 | 0 | 0.0 | 43 ms | 0 |
| Wed 11 | 0 | 0.0 | 34 ms | 0 |
| Wed 13 | 0 | 0.0 | 31 ms | 0 |
| Wed 15 | 0 | 0.0 | 111 ms | 0 |
| Wed 17 | 0 | 0.0 | 117 ms | 0 |
| Wed 19 | 0 | 0.0 | 67 ms | 0 |
| Wed 22 | 0 | 0.0 | 49 ms | 0 |
| Thu 00 | 0 | 0.0 | 62 ms | 0 |
| Thu 02 | 0 | 0.0 | 510 ms | 0 |
| Thu 04 | 0 | 0.0 | 41 ms | 0 |
| Thu 06 | 0 | 0.0 | 259 ms | 0 |
| Thu 08 | 0 | 0.0 | 90 ms | 0 |
| Thu 10 | 0 | 0.0 | 120 ms | 0 |
| Thu 12 | 0 | 0.0 | 26 ms | 0 |
| Thu 14 | 0 | 0.0 | 79 ms | 0 |
| Thu 16 | 0 | 0.0 | 81 ms | 0 |
| Thu 18 | 0 | 0.0 | 104 ms | 0 |
| Thu 20 | 0 | 0.0 | 50 ms | 0 |
| Thu 23 | 0 | 0.0 | 40 ms | 0 |
| Fri 01 | 0 | 0.0 | 30 ms | 0 |
| Fri 03 | 0 | 0.0 | 112 ms | 0 |
| Fri 05 | 0 | 0.0 | 62 ms | 0 |
| Fri 07 | 0 | 0.0 | 52 ms | 0 |
| Fri 09 | 0 | 0.0 | 494 ms | 0 |
| Fri 11 | 0 | 0.0 | 79 ms | 0 |
| Fri 13 | 0 | 0.0 | 75 ms | 0 |
| Fri 15 | 0 | 0.0 | 301 ms | 0 |
| Fri 17 | 0 | 0.0 | 34 ms | 0 |
| Fri 19 | 0 | 0.0 | 90 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 Magic Hour 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 Magic Hour goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Magic Hour alerts to Slack, Discord or a webhook — free.
Magic Hour, at magichour.ai, is one of the AI services we monitor. Face swap, lip sync, talking photos, and AI image and video tools. Try supported tools free, no sign up. Credit packs without a subscription; unused credits never expire. 5M+ creators.
Magic Hour publishes an official status page at status.magichour.ai; 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 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 124 ms average, 20–494 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Magic Hour incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
124 ms on average over the last 24 hours (20–494 ms).
Yes, at https://status.magichour.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 Magic Hour here at once, the problem is on Magic Hour'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 Magic Hour. 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.