Stagetimer Outage History
Stagetimer is up right nowPingoru has recorded 27 incidents for Stagetimer: 27 in the last 12 months and 11 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 0 | 0 of 720 (0%) |
| May 2026 | 12 | 0 of 744 (0%) |
| June 2026 | 2 | 0 of 720 (0%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 9 | 1 of 744 (0%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 2 | 0 of 545 (0%) |
Incidents, newest first
Minor October 7, 2026 Public API: incident detected for 1m 1m Public API
Started Oct 07, 2026, 05:21 PM UTC· resolved Oct 07, 2026, 05:22 PM UTC
No vendor updates were posted for this incident.
Minor October 7, 2026 Public API: down for 1 minutes 1m Public API
Started Oct 07, 2026, 05:21 PM UTC· resolved Oct 07, 2026, 05:22 PM UTC
No vendor updates were posted for this incident.
Major August 13, 2026 Node Server 5 (Singapore): incident detected for 16m 16m Node Server 5 (Singapore)
Started Aug 13, 2026, 01:53 AM UTC· resolved Aug 13, 2026, 02:09 AM UTC
No vendor updates were posted for this incident.
Major August 13, 2026 Node Server 5 (Singapore): down for 17 minutes 17m Node Server 5 (Singapore)
Started Aug 13, 2026, 01:53 AM UTC· resolved Aug 13, 2026, 02:10 AM UTC
No vendor updates were posted for this incident.
Minor August 13, 2026 Node Server 5 (Singapore): incident detected for 1m 1m Node Server 5 (Singapore)
Started Aug 13, 2026, 01:50 AM UTC· resolved Aug 13, 2026, 01:51 AM UTC
No vendor updates were posted for this incident.
Major August 12, 2026 Node Server 5 (Singapore): incident detected for 18m 18m Node Server 5 (Singapore)
Started Aug 12, 2026, 11:32 PM UTC· resolved Aug 12, 2026, 11:50 PM UTC
No vendor updates were posted for this incident.
Major August 12, 2026 Node Server 5 (Singapore): down for 38 minutes 38m Node Server 5 (Singapore)
Started Aug 12, 2026, 11:32 PM UTC· resolved Aug 13, 2026, 12:10 AM UTC
No vendor updates were posted for this incident.
Major August 12, 2026 Node Server 5 (Singapore): incident detected for 10m 10m Node Server 5 (Singapore)
Started Aug 12, 2026, 11:08 PM UTC· resolved Aug 12, 2026, 11:19 PM UTC
No vendor updates were posted for this incident.
Major August 12, 2026 Node Server 5 (Singapore): down for 20 minutes 20m Node Server 5 (Singapore)
Started Aug 12, 2026, 11:08 PM UTC· resolved Aug 12, 2026, 11:28 PM UTC
No vendor updates were posted for this incident.
Minor August 12, 2026 Node Server 5 (Singapore): incident detected for 8m 8m Node Server 5 (Singapore)
Started Aug 12, 2026, 10:58 PM UTC· resolved Aug 12, 2026, 11:07 PM UTC
No vendor updates were posted for this incident.
Minor August 12, 2026 Node Server 5 (Singapore): down for 0 seconds 11m Node Server 5 (Singapore)
Started Aug 12, 2026, 10:58 PM UTC· resolved Aug 12, 2026, 11:09 PM UTC
No vendor updates were posted for this incident.
Minor June 24, 2026 Node Server 5 (Singapore): incident detected for 2m 2m Node Server 5 (Singapore)
Started Jun 24, 2026, 10:33 AM UTC· resolved Jun 24, 2026, 10:35 AM UTC
No vendor updates were posted for this incident.
Minor June 24, 2026 Node Server 5 (Singapore): down for 2 minutes 2m Node Server 5 (Singapore)
Started Jun 24, 2026, 10:33 AM UTC· resolved Jun 24, 2026, 10:35 AM UTC
No vendor updates were posted for this incident.
Minor May 5, 2026 Node Server 2 (Helsinki): incident detected for 2m 2m Node Server 2 (Helsinki)
Started May 05, 2026, 12:14 PM UTC· resolved May 05, 2026, 12:16 PM UTC
No vendor updates were posted for this incident.
Minor May 5, 2026 Node Server 2 (Helsinki): down for 2 minutes 2m Node Server 2 (Helsinki)
Started May 05, 2026, 12:14 PM UTC· resolved May 05, 2026, 12:16 PM UTC
No vendor updates were posted for this incident.
Minor May 4, 2026 Socket Service: incident detected for 3m 3m Socket Service
Started May 04, 2026, 04:01 PM UTC· resolved May 04, 2026, 04:04 PM UTC
No vendor updates were posted for this incident.
Minor May 4, 2026 Socket Service: down for 3 minutes 3m Socket Service
Started May 04, 2026, 04:01 PM UTC· resolved May 04, 2026, 04:04 PM UTC
No vendor updates were posted for this incident.
Minor May 4, 2026 Redis Service: incident detected for 5m 5m Redis Service
Started May 04, 2026, 03:59 PM UTC· resolved May 04, 2026, 04:05 PM UTC
No vendor updates were posted for this incident.
Minor May 4, 2026 MongoDB: incident detected for 5m 5m MongoDB
Started May 04, 2026, 03:59 PM UTC· resolved May 04, 2026, 04:04 PM UTC
No vendor updates were posted for this incident.
Minor May 4, 2026 Node Server (Load Balancer): incident detected for 5m 5m Server
Started May 04, 2026, 03:59 PM UTC· resolved May 04, 2026, 04:04 PM UTC
No vendor updates were posted for this incident.
Minor May 4, 2026 MongoDB: down for 5 minutes 5m MongoDB
Started May 04, 2026, 03:59 PM UTC· resolved May 04, 2026, 04:04 PM UTC
No vendor updates were posted for this incident.
Minor May 4, 2026 Node Server (Load Balancer): down for 5 minutes 5m Server
Started May 04, 2026, 03:59 PM UTC· resolved May 04, 2026, 04:04 PM UTC
No vendor updates were posted for this incident.
Minor May 4, 2026 Redis Service: down for 5 minutes 5m Redis Service
Started May 04, 2026, 03:59 PM UTC· resolved May 04, 2026, 04:04 PM UTC
No vendor updates were posted for this incident.
Minor May 4, 2026 Public API: incident detected for 6m 6m Public API
Started May 04, 2026, 03:58 PM UTC· resolved May 04, 2026, 04:05 PM UTC
No vendor updates were posted for this incident.
Minor May 4, 2026 Public API: down for 6 minutes 6m Public API
Started May 04, 2026, 03:58 PM UTC· resolved May 04, 2026, 04:04 PM UTC
No vendor updates were posted for this incident.