rogo incident

Rogo slow and unavailable for some users

Minor Resolved View vendor source →

rogo experienced a minor incident on September 29, 2026 affecting Rogo Application, lasting 1h 9m. The incident has been resolved; the full update timeline is below.

Started
Sep 29, 2026, 03:45 PM UTC
Resolved
Sep 29, 2026, 04:54 PM UTC
Duration
1h 9m
Detected by Pingoru
Sep 29, 2026, 03:45 PM UTC

Affected components

Rogo Application

Update timeline

  1. investigating Sep 29, 2026, 03:45 PM UTC

    Status: Investigating We're investigating reports of slow load times across Rogo. Affected components Rogo Application (Degraded performance)

  2. investigating Sep 29, 2026, 03:55 PM UTC

    Status: Investigating Some users are seeing errors, including failed logins and pages that don't load. We're continuing to investigate. Affected components Rogo Application (Partial outage)

  3. identified Sep 29, 2026, 04:35 PM UTC

    Status: Identified We've traced the issue to database overload caused by a recently enabled feature. We've disabled that feature and are restoring service. Affected components Rogo Application (Partial outage)

  4. monitoring Sep 29, 2026, 04:44 PM UTC

    Status: Monitoring A fix is in place and error rates are falling. We're monitoring the recovery. Affected components Rogo Application (Degraded performance)

  5. resolved Sep 29, 2026, 04:54 PM UTC

    Status: Resolved Rogo is fully restored. We've also deployed safeguards to prevent this from happening again. Affected components Rogo Application (Operational)