Statscore Outage History

Statscore is up right now

Pingoru has recorded 3 incidents for Statscore: 3 in the last 12 months and 1 in the last 90 days.

Source: status.statscore.com

3incidents recorded
3last 12 months
1last 90 days
2 hourstypical duration
Incidents per month
012AprMayJunJulAugSepOctNov0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOctNov0%
Pingoru began tracking Statscore in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202611 of 720 (0%)
May 202600 of 744 (0%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202616 of 744 (1%)
November 202600 of 72 (0%)

Incidents, newest first

Minor October 20, 2026 Cloud service provider availability incident 6h 9m SportsAPI, ScoutsFeed, LivematchPro (Versions: 1.0 and 2.0), PrematchPro (Versions: 1.0 and 2.0) and 5 more

Started Oct 20, 2026, 07:15 AM UTC· resolved Oct 20, 2026, 01:24 PM UTC

  1. investigating Oct 20, 2026, 07:15 AM UTC

    We’re experiencing issues with cloud service provider. We will inform you when the incident is resolved.

  2. identified Oct 20, 2026, 09:03 AM UTC

    The Google Cloud status page has been updated to report further information, follow this link for details https://status.cloud.google.com/incidents/Xs2XTHzAVC9YnafnPyzj

  3. resolved Oct 20, 2026, 01:24 PM UTC

    Resolved

Read the full incident report →

Minor April 24, 2026 SSL certificate issue 1h 8m LivematchPro (Versions: 1.0 and 2.0), PrematchPro (Versions: 1.0 and 2.0), ScoreFrame

Started Apr 24, 2026, 06:03 AM UTC· resolved Apr 24, 2026, 07:11 AM UTC

  1. investigating Apr 24, 2026, 06:03 AM UTC

    Certificate manager misconfiguration was identified for several subdomains and fix has been applied.

  2. resolved Apr 24, 2026, 07:11 AM UTC

    Resolved

Read the full incident report →

Minor February 3, 2026 Resolved 7m LeagueCenter

Started Feb 03, 2026, 11:00 AM UTC· resolved Feb 03, 2026, 11:08 AM UTC

  1. investigating Feb 03, 2026, 11:00 AM UTC

    The issue has been resolved by rolling back the most recent deployment.

  2. resolved Feb 03, 2026, 11:08 AM UTC

    Resolved

Read the full incident report →