# Check service status

> Public channel — documentation of app 3.6.3. Follow the availability notices of each service.

Source: [Check service status](/en/aide/etat-des-services/)

An outage that affects everyone shows up at a glance on [vibestarter.pro/statut](https://vibestarter.pro/en/status). It’s the first thing to check when nothing responds: there’s no need to look on your side for what’s broken on ours.

1.  **Something stops responding** Sign-in, online backup, asset bank, Discord bot
    
    _check_
    
2.  **Status page** vibestarter.pro/statut
    
    _all operational_
    
3.  **The problem is on your side** The troubleshooting pages, then support
    

The status page quickly separates a general outage from a local problem.

## What the page shows

It displays three services and refreshes itself every minute.

| Service | What it covers |
| --- | --- |
| VibeStarter API | Sign-in, account, credits, asset bank |
| Cloud | Online backup of your project code |
| Discord bot | The bot that admits members and handles bug tickets |

Each service has a status — **Operational**, **Degraded** or **Down** —, its latency, the time of its last check and its uptime over 90 days. A section lists incidents from the last 14 days.

The switch to **Degraded** is immediate, on the first failed check. Three consecutive failures are needed to switch to **Down**, and the return to normal shows right away. A service can therefore appear degraded for a moment without you having noticed anything. In the 90-day uptime, only **Down** minutes count as unavailable: a degraded service counts as available.

If the page itself can’t query our services, it says so: it displays a major incident instead of an empty table.

## What the page doesn’t show

It monitors **only** VibeStarter services. You will never see:

-   **Roblox** — an outage of Roblox or Roblox Studio is checked with Roblox.
-   **AI providers** — Anthropic, OpenAI, xAI, Google and OpenCode each publish their own status.
-   **Email** — an email that doesn’t arrive can’t be read on this page.

To work out which of these parties is involved, see the diagram on [Get help](/en/aide/).

## When to check it

-   Before writing to support, when the problem looks general rather than specific to your machine.
-   When sign-in fails even though your link is valid.
-   When an online backup of a project stays stuck.
-   When the Discord bot stops responding, especially when you’re opening a ticket.

If everything is operational, the problem is on your side or with a third party: go back to [The app won’t start](/en/aide/demarrage/), [I can’t sign in](/en/aide/connexion/) or [The connection to Roblox Studio doesn’t work](/en/aide/studio/).

## Going further

-   [Get help](/en/aide/)
-   [Find your logs and report a bug](/en/aide/journaux/)
-   [Your code is saved automatically](/en/application/projet/sauvegarde/)