Status page
Atualizado em Nov 15, 2026 Abrir ferramenta
/status says whether the tools and the services behind them are running, with 90 days of history per service and the incidents of the last 30 days. It is public, linked from the Docs menu in the site's top bar and the footer's Resources column on every page outside the workspace, Ctrl+K ("Status") and the dot at the top right of the workspace. When someone asks "is Imagine down?" or "are conversions working?", this is the page.
What the page shows
- Headline: "All systems normal", "N services down", "N services degraded" or "Status unknown" (nothing checked in the last 15 minutes), and when the last check ran. Checks run every 5 minutes.
- Services, one row each: the name, the tools that depend on it, the state word, the 90-day uptime, and a bar of 90 cells (oldest left, today right). A cell's colour is how long the service was out that day, as Statuspage and Better Stack shade theirs (since 2026-10-02): red for an hour or more down, amber for less than an hour down or half an hour or more slow, green otherwise, grey with no checks. Each check stands for five minutes. Hovering a cell (tapping one on a phone) opens a tooltip with the date, the day's state ("No downtime", "Partial outage" for under an hour down, "Major outage" for an hour or more, "Degraded" for slowness only, "No data" before checks began) beside a dot in its colour, and the figures ("99.4% up · 5 min down"). It is the workspace's tooltip surface, not the browser's title popup (since 2026-10-02), and near either end of the bar it hangs inward so it stays on the card. Until 2026-10-02 any single down check turned the whole day red, so a five-minute blip looked like an outage on a service that was long back up.
Days are UTC. In Australia the last cell ("Today") is still yesterday evening until 10:00 local time, so an outage from last night sits in it even when the row reads Up. A red last cell with Up beside it means it was out for an hour or more earlier that UTC day and is back, which is how other status pages show a resolved outage too.
- Incidents · 30 days: one line per outage, not per check and not per service: the services that fell in the same cron run are named together ("Conversion API · Conversion queue · Down"), with when it started and how long it lasted (or "Ongoing"). A service that drops again within 15 minutes of coming back reopens its incident rather than adding another. At most 50 are kept on the page.
- The same blip is one line (2026-11-15). Incidents next to each other in the list, with the same services and the same state and all of them over, are one line with a count and the span they cover: "OpenAI · Degraded · ×16", "5 Nov, 07:00 – 6 Nov, 02:35", and their minutes added up. Anything else in between keeps them apart, and an ongoing incident is always its own line. A finished "slow" of ten minutes or less is left off the list altogether (one or two slow answers to a check; the 90-day bars still count them). The list had 23 lines, most of them five-minute OpenAI blips; it has 9.
incidentLinesinsrc/lib/status/incidents.ts.
The states: Up; Degraded (reachable but slow, over 3 s, rate limited, or refusing our key); Down (not answering, or a provider balance too low for the tool to run); Unknown (not checked in 15 minutes: the cron is not running, or the service has never been checked).
| Row | What is checked | Tools that depend on it |
|---|---|---|
| Workspace | The cron itself ran (zoov.dev answers) | the app |
| Database | A timed read of Supabase | accounts, credits, files |
| Conversion API | v2.winapi.zoov.dev/ping, twice, the second timed |
Converter, Vehicle, Peds, Packs, Optimize |
| Conversion queue | A worker seen in the last minute (ws_workers; a busy worker is seen through its job heartbeats, awaited since 2026-10-15 so a long job no longer reads as "no worker") |
queued conversions |
| Imagine | Meshy's balance; under 50 the tool refuses, so that is Down | Props, Weapons, Clothing, 3D |
| Imagine Pro | Off the page since 2026-11-15 (STATUS_PAUSED in src/lib/config/status.ts). Tripo's balance, the same rule |
the Pro engine |
| OpenAI | GET /v1/models/<the text model the site calls> with our key (the whole model list until 2026-11-15) |
Code, Designer AI, Flare and Sunburst image models |
| Gemini | GET /v1beta/models with our key |
Images, Tattoos, ER:LC |
| Discord | GET /users/@me as the bot |
sign-in, roles |
| Support bot | Syntax's heartbeat, written every minute; under 3 minutes old Up, under 10 Degraded, older Down | Syntax |
| Payments | Stripe GET /v1/balance with our key |
checkout, plans, packs |
Imagine Pro is paused (2026-11-15). Its provider account has been short of balance since 2026-10-20, which is a choice and not an outage, and it kept the headline at "1 service down" and the dot red for 25 days. A service in STATUS_PAUSED has no row, does not count in the headline or the dot, is not checked and posts nothing to #watchdog; its past incidents are hidden with it and its history stays in the tables. Taking the id out of the set brings all of it back. The Pro engine itself is unchanged: it still answers "Service Unavailable" while the balance is under 50.
Slow needs two answers (2026-11-15). A check that answers, but slower than the 3 s bar, is asked once more and the faster answer counts, as a failed check already was. The OpenAI check also stopped listing every model, an answer that passed three seconds often enough to open 68 "Degraded · slow" incidents in 90 days (28 in the last fortnight) that nobody using the tools could notice.
The dot in the workspace
Top right of the app's bar, before the help mark: green when everything is up, amber when something is degraded, red when something is down, grey when nothing is known. Hovering it names what is not up; pressing it opens /status. It asks the API once the page is idle and every five minutes while the tab is visible. Hidden on phones.
Alerts in #watchdog
Every status cron run posts what changed to the owner's #watchdog Discord channel (1554837408476962876), one message per run at most, linking /status. Nothing is posted while nothing changes.
- Down: at once (each probe already tries twice inside the run). "🔴 Imagine Pro · Down · balance".
- Degraded: only after two runs in a row, so one slow answer stays quiet.
- Worse: degraded to down.
- Still down: a reminder every six hours, with when it started.
- Back: after two up runs in a row, with how long it was out. A service that comes up for one run and drops again is never announced as back, so a flapping service posts once, not every five minutes.
- Mention after 30 minutes (2026-11-15, off until set): a service down for thirty minutes and still down posts one more line that mentions one Discord user, "🔴 Conversion API · Down 30m and not back · http 502 · @owner", once per outage. It is on only while the env var
OPS_PAGE_USER_IDholds a Discord user id (digits only); unset, nothing changes. Degraded never mentions anyone. It was added because the channel is read, not watched: on 2026-11-14 the conversion API was down for 16 h 55 min (07:10 to 00:05 UTC,http 502) through a Down post and two Still down reminders that nobody saw until the next morning, and every Convert, Optimize, UV map and Vehicle run failed for that time with "Connection failed · check your network".PAGE_AFTER_MSinsrc/lib/server/status/notify.ts; the outage keepspagedin itsstatus.alertsmemory so a second mention never follows.
The ops-alerts cron (ops-dashboard.md) posts to the same channel; it leaves out the four outages this one covers (WinAPI down, worker offline, Meshy or Tripo empty) and adds "Status checks · Stopped" when nothing has been written here for 20 minutes. Since 2026-10-07 the same cron ends with the account-sharing sweep (security.concurrent_use, profiles-and-verification.md); nothing on this page changed.
Common questions
Is X down?
Open /status. Red or amber on the row means the check saw it; the bar shows whether it is new. Imagine showing Down with everything else green usually means the provider balance is low (the credits doc, "Service Unavailable").
The page says Status unknown.
The cron has not written a check in 15 minutes: the Vercel cron is not running or the route answers 401 (no CRON_SECRET). Staff: /ops and the Vercel cron log.
The support bot shows Unknown. It has never written a heartbeat (the bot has not been restarted since 2026-10-01), or the row is missing. Down means it has not beaten for ten minutes.
The support bot shows Down or Degraded but it is online in Discord.
The heartbeat is a call from the bot to the database, so Down means the bot cannot reach the database or the site, not that it has left Discord. The gateway connection stays open, so the bot still looks online, but anything that needs the database or the site (support answers, tickets, role sync, the games) fails at the same time. On 2026-10-02 (from about 02:20 UTC) the cause was DNS: the box asked only Vultr's resolver 108.61.10.10, which answered SERVFAIL for zoov.dev, and so for db.zoov.dev whenever its cached answer ran out. The bot's log filled with getaddrinfo EAI_AGAIN db.zoov.dev. Fixed the same day by pointing the box at 1.1.1.1 and 8.8.8.8 (winapi Actions > Box inventory, input dns). To check again, run Box inventory: its "Network and the bot's outbound calls" step prints the bot's network errors, which DNS servers the box asks, and a three-round lookup of zoov.dev, db.zoov.dev and others against them, 1.1.1.1 and 8.8.8.8.
Why is a day amber when nothing was down? A check that day answered slowly (over 3 s) or was rate limited. Degraded, not down; uptime does not count it against the service.