55 Tech - Notice history

All systems operational

Websocket - Operational

100% - uptime
Jul 2025 · 99.94%Aug · 100.0%Sep · 100.0%

Previous page

Next page

Jul 2025
Aug 2025
Sep 2025

Notice history

Sep 2025

/v4/tournaments is down
  • Resolved
    Resolved
    GET /tournaments is back up. This incident was automatically resolved by Instatus monitoring.
  • Investigating
    Investigating
    GET /tournaments is down at the moment. This incident was automatically created by Instatus monitoring.
/v4/markets is down
  • Resolved
    Resolved
    GET /markets is back up. This incident was automatically resolved by Instatus monitoring.
  • Investigating
    Investigating
    GET /markets is down at the moment. This incident was automatically created by Instatus monitoring.
/v4/languages is down
  • Resolved
    Resolved
    GET /languages is back up. This incident was automatically resolved by Instatus monitoring.
  • Investigating
    Investigating
    GET /languages is down at the moment. This incident was automatically created by Instatus monitoring.
/v4/tournaments is down
  • Resolved
    Resolved
    GET /tournaments is back up. This incident was automatically resolved by Instatus monitoring.
  • Investigating
    Investigating
    GET /tournaments is down at the moment. This incident was automatically created by Instatus monitoring.
/v4/sports is down
  • Resolved
    Resolved
    GET /sports is back up. This incident was automatically resolved by Instatus monitoring.
  • Investigating
    Investigating
    GET /sports is down at the moment. This incident was automatically created by Instatus monitoring.

Aug 2025

No notices reported this month

Jul 2025

/v4/participants is down
  • Resolved
    Resolved
    GET /participants is back up. This incident was automatically resolved by Instatus monitoring.
  • Investigating
    Investigating
    GET /participants is down at the moment. This incident was automatically created by Instatus monitoring.
Issues with websocket and /bookmakers API
  • Resolved
    Resolved
    This incident has been resolved.
  • Identified
    Identified
    We are continuing to work on a fix for this incident.
  • Investigating
    Investigating
    We are currently investigating this incident.

Jul 2025 to Sep 2025

Next