Starmind Outage History

Starmind is up right now

Pingoru has recorded 48 incidents for Starmind: 1 in the last 12 months and 0 in the last 90 days.

Source: status.starmind.com

48incidents recorded
1last 12 months
0last 90 days
2 hourstypical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Starmind 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 202600 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 202600 of 508 (0%)

Incidents, newest first

Major December 14, 2025 Partial Outage in Swiss Datacenter 2h 13m Application (API & Frontend), SSO Services

Started Dec 14, 2025, 04:14 PM UTC· resolved Dec 14, 2025, 06:27 PM UTC

  1. investigating Dec 14, 2025, 04:14 PM UTC

    We are currently investigating this issue.

  2. identified Dec 14, 2025, 04:40 PM UTC

    The issue has been identified and a fix is being implemented.

  3. identified Dec 14, 2025, 04:40 PM UTC

    We are continuing to work on a fix for this issue.

  4. resolved Dec 14, 2025, 06:27 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical January 24, 2025 Database overload from cronjobs –

Started Jan 24, 2025, 01:30 AM UTC· resolved Jan 24, 2025, 01:30 AM UTC

  1. resolved Jan 27, 2025, 09:19 AM UTC

    We run multiple overnight jobs to insure the proper functioning of our service. Those jobs overlapped during the night creating too much load on our database. We took measures so that this should not be the case in the future. This affected our european customes.

Read the full incident report →

Critical November 14, 2024 Azure database disruptions –

Started Nov 14, 2024, 11:30 PM UTC· resolved Nov 14, 2024, 11:30 PM UTC

  1. resolved Nov 18, 2024, 08:38 AM UTC

    Our database server malfunctioned during the night because of too much load and did not accept connections anymore. The issue has been resolved in the morning around 10 and services were restored.

Read the full incident report →