Check the status of Clybo’ services

The portal brings together Clybo’ availability checks. It can help you tell the difference between an incident detected in the services and a problem that appears only on your connection or during a particular operation.

Before you start

Availability: visit status.clybo.app. You do not need to sign in, and there are no role or country restrictions.

Step by step

1. Open the status portal

Visit status.clybo.app in any browser. You can change the language at the top. The portal refreshes automatically every 30 seconds.

2. Check the summary and affected service

The summary says whether checks are successful, incidents have been detected or recent data is missing. Below it, you will find the API, the dashboard connection, the club dashboard, the families’ and coaching apps, enrolments and the public website.

• Operational: the service responded successfully to its latest check.
• Incident: a failure was detected in the service check.
• No recent data: there has not been a check yet or the latest one is at least three minutes old. This status does not confirm that the service is unavailable or available.

3. Check history and incidents

Under Our services, choose 12 hours, 30 days or 90 days. The 12-hour view groups checks into 15-minute intervals. Longer views show one bar per UTC calendar day, including today; the day change may therefore differ from your time zone.

In the 30-day and 90-day views, colours summarise recorded results:

• Green: the day has records with no outage lasting more than 5 minutes. It stays green even if some checks are missing or the next day has started.
• Red: an outage lasting more than 5 minutes was recorded, even if the service recovered that same day.
• Grey: no data was recorded for that day. A new day may appear grey until its first check is archived.

Outages of up to 5 minutes, such as a brief redeployment, do not turn the day red. Each outage is measured from its start until recovery or the last recorded check; separate outages are not added together. If an outage lasts more than 5 minutes and crosses midnight UTC, it affects both days.

Daily green is not an availability percentage and does not confirm every minute of the day. The 12-hour view keeps the coverage detail: a gap of two minutes or more makes the affected interval grey if no failure was observed. Hover over a bar to check its date and status. The status and latency next to the service name remain current when you change the period; bars show the selected history.

History accumulates from actual measurements. The period before monitoring was enabled is not filled in as though the services had been available. If daily history cannot be loaded, a notice appears and the last results received are kept; later checks may be missing until the view refreshes. Changing the period does not filter the announcements or the automatic incident list.

The automatic incidents section shows up to 30 recent incidents from the 90 days retained. A resolved incident includes its start and end. If recent data is missing, recovery remains unconfirmed.

4. Read team announcements

Under Incident announcements, you will find the title, affected services, impact, description and team updates. Statuses are Investigating, Cause identified, Monitoring and Resolved. The latest updates appear first. If there are many announcements, use Previous and Next; open incidents appear first.

A reported incident may remain open even if an automatic check succeeds. In that case, the summary says that reported incidents are ongoing. Resolved announcements remain available until the team removes them. If they cannot be updated, a notice explains this; check their dates.

Who publishes incidents

The Clybo’ operations team publishes from Superadministrator → Service status (/estado-servicios). This permission is not for club administrators, coaches or families. It requires platform access, MFA and identity verification when saving.

An operator can create a New incident, enter a title, description, services, impact, status and start time, then select Save draft without making it public. Publish incident displays it on the portal. Add update lets the team report progress, and Save and publish changes publishes edits. The overall status is selected separately from each update’s status.

Remove from portal returns an announcement to draft. Delete incident removes it from the editor and portal after confirmation, while retaining an internal audit record. These actions do not change automatic checks. If another operator has saved changes, the form warns about the conflict and lets you Reload saved version before continuing. If saving fails, your edits are kept while the valid session remains open.

The editor is also prepared but pending activation. If the main API fails, it cannot save changes; the portal keeps announcements already published. The team publishes text in the language it writes in, with no automatic translation. Publishing an announcement does not trigger Telegram alerts.

What to expect

Checks run every minute from a monitoring location. They do not include signing in or every operation at your club, and they do not cover every access network. A green status does not rule out a problem you are experiencing.

Telegram alerts are for the Clybo’ operations team; this first version does not support public subscriptions or configure your club’s alerts.

If something goes wrong

If the page cannot refresh, you will see a notice and the data will become stale. Check the time of the latest check before interpreting the status. If the portal itself will not load, you cannot infer the status of the other services from that.

If Clybo’ still fails while the portal is green, note the time, app, browser and error message, then report it through your usual support channel. Do not share passwords or other people’s private information.

Next step

For questions about your club, see Contact the club from the app.