VyroAI

Loading...

The Status Page

The public /status page shows whether VyroAI.vip is working right now, service by service from the build server to bot hosting, and what incidents mean.

Where to look

/status is public — no account needed — and it answers one question: is VyroAI working right now? Each service carries its own state: Operational, Degraded or Down.

The services being watched

The page is not one traffic light but one card per service, up to six, so you can tell which part of VyroAI is unwell. These are the names printed on the cards, so you can match them by eye:

A build that will not start while everything else works is a Build service problem, and it is worth looking here before you blame your code.

The words on an incident

Each incident carries one of four labels, and they are easy to misread:

The 90-day bar

Under each service is a strip of thin bars, one per day, covering the last 90 days. Green days were clean; coloured ones were not. The rolling uptime percentage for that window sits at the top of the service's card, next to its status word — Operational · 99,9 % / 90 d, for example.

Each bar is clickable, and a day is graded one of four ways:

On a phone the strip shows weeks rather than single days, so 90 days still fits the screen.

Incidents

The incident list sits above the service cards, so anything currently wrong is the first thing you see: what happened, when it started and ended, and the uptime during it. When there is nothing to report it says so plainly rather than showing an empty box.

You get told

When a service is down or slowed, a bar appears across the top of the app, so you do not have to go looking. It is red when something is down and amber when it is only degraded. It names the service — Build service is down., for example — and adds either Builds may fail or be slow — chat, editing and your files work normally. or Your projects and files are safe. It has three buttons: Report tells us you are affected, View status opens this page, and × closes the bar.

Closing it sticks. This browser remembers it, so a reload does not bring the bar back, and a service that is only slowed never reopens it. It only comes back when a service goes fully down that was not down when you closed it. Once everything has been healthy for about 15 minutes, the app forgets that you closed it, so the next outage is shown again.

You only see the bar while you are signed in, and never on the sign-in or password-reset pages. A fault in a service that belongs to one tool is only named on that tool's pages: Video generation in the Video Studio, Build service in the Code Studio and AI Chat, Bot hosting in the Code Studio. Database & API, Authentication and File storage sit under everything, so they are named on every page. Signed out, /status is where to look.

If you see it, the problem is ours — waiting is genuinely faster than retrying, and retrying spends credits.

Check here before contacting support about something that suddenly stopped working. It answers most "is it broken?" questions in about five seconds.

Also in Support & Legal

10 of 15 in Support & Legal · Last checked 12 September 2026 · Previous: Content Policy Blocks