Stagetimer Outage History

Stagetimer is up right now

Stagetimer had 25 outages in the last 2 years totaling 3h 42m of downtime — averaging 1 incident per month.

There were 25 Stagetimer outages since March 3, 2026 totaling 3h 42m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://stats.uptimerobot.com/jJ140cjvEB

Major August 13, 2026

Node Server 5 (Singapore): incident detected for 16m

Detected by Pingoru: Aug 13, 2026, 01:53 AM UTC
Resolved: Aug 13, 2026, 02:09 AM UTC
Duration: 16m

Affected: Node Server 5 (Singapore)

Read the full incident report →

Major August 13, 2026

Node Server 5 (Singapore): down for 17 minutes

Detected by Pingoru: Aug 13, 2026, 01:53 AM UTC
Resolved: Aug 13, 2026, 02:10 AM UTC
Duration: 17m

Affected: Node Server 5 (Singapore)

Read the full incident report →

Minor August 13, 2026

Node Server 5 (Singapore): incident detected for 1m

Detected by Pingoru: Aug 13, 2026, 01:50 AM UTC
Resolved: Aug 13, 2026, 01:51 AM UTC
Duration: 1m

Affected: Node Server 5 (Singapore)

Read the full incident report →

Major August 12, 2026

Node Server 5 (Singapore): incident detected for 18m

Detected by Pingoru: Aug 12, 2026, 11:32 PM UTC
Resolved: Aug 12, 2026, 11:50 PM UTC
Duration: 18m

Affected: Node Server 5 (Singapore)

Read the full incident report →

Major August 12, 2026

Node Server 5 (Singapore): down for 38 minutes

Detected by Pingoru: Aug 12, 2026, 11:32 PM UTC
Resolved: Aug 13, 2026, 12:10 AM UTC
Duration: 38m

Affected: Node Server 5 (Singapore)

Read the full incident report →

Major August 12, 2026

Node Server 5 (Singapore): incident detected for 10m

Detected by Pingoru: Aug 12, 2026, 11:08 PM UTC
Resolved: Aug 12, 2026, 11:19 PM UTC
Duration: 10m

Affected: Node Server 5 (Singapore)

Read the full incident report →

Major August 12, 2026

Node Server 5 (Singapore): down for 20 minutes

Detected by Pingoru: Aug 12, 2026, 11:08 PM UTC
Resolved: Aug 12, 2026, 11:28 PM UTC
Duration: 20m

Affected: Node Server 5 (Singapore)

Read the full incident report →

Minor August 12, 2026

Node Server 5 (Singapore): incident detected for 8m

Detected by Pingoru: Aug 12, 2026, 10:58 PM UTC
Resolved: Aug 12, 2026, 11:07 PM UTC
Duration: 8m

Affected: Node Server 5 (Singapore)

Read the full incident report →

Minor August 12, 2026

Node Server 5 (Singapore): down for 0 seconds

Detected by Pingoru: Aug 12, 2026, 10:58 PM UTC
Resolved: Aug 12, 2026, 11:09 PM UTC
Duration: 11m

Affected: Node Server 5 (Singapore)

Read the full incident report →

Minor June 24, 2026

Node Server 5 (Singapore): incident detected for 2m

Detected by Pingoru: Jun 24, 2026, 10:33 AM UTC
Resolved: Jun 24, 2026, 10:35 AM UTC
Duration: 2m

Affected: Node Server 5 (Singapore)

Read the full incident report →

Minor June 24, 2026

Node Server 5 (Singapore): down for 2 minutes

Detected by Pingoru: Jun 24, 2026, 10:33 AM UTC
Resolved: Jun 24, 2026, 10:35 AM UTC
Duration: 2m

Affected: Node Server 5 (Singapore)

Read the full incident report →

Minor May 5, 2026

Node Server 2 (Helsinki): incident detected for 2m

Detected by Pingoru: May 05, 2026, 12:14 PM UTC
Resolved: May 05, 2026, 12:16 PM UTC
Duration: 2m

Affected: Node Server 2 (Helsinki)

Read the full incident report →

Minor May 5, 2026

Node Server 2 (Helsinki): down for 2 minutes

Detected by Pingoru: May 05, 2026, 12:14 PM UTC
Resolved: May 05, 2026, 12:16 PM UTC
Duration: 2m

Affected: Node Server 2 (Helsinki)

Read the full incident report →

Minor May 4, 2026

Socket Service: incident detected for 3m

Detected by Pingoru: May 04, 2026, 04:01 PM UTC
Resolved: May 04, 2026, 04:04 PM UTC
Duration: 3m

Affected: Socket Service

Read the full incident report →

Minor May 4, 2026

Socket Service: down for 3 minutes

Detected by Pingoru: May 04, 2026, 04:01 PM UTC
Resolved: May 04, 2026, 04:04 PM UTC
Duration: 3m

Affected: Socket Service

Read the full incident report →

Minor May 4, 2026

Redis Service: incident detected for 5m

Detected by Pingoru: May 04, 2026, 03:59 PM UTC
Resolved: May 04, 2026, 04:05 PM UTC
Duration: 5m

Affected: Redis Service

Read the full incident report →

Minor May 4, 2026

MongoDB: incident detected for 5m

Detected by Pingoru: May 04, 2026, 03:59 PM UTC
Resolved: May 04, 2026, 04:04 PM UTC
Duration: 5m

Affected: MongoDB

Read the full incident report →

Minor May 4, 2026

Node Server (Load Balancer): incident detected for 5m

Detected by Pingoru: May 04, 2026, 03:59 PM UTC
Resolved: May 04, 2026, 04:04 PM UTC
Duration: 5m

Affected: Node Server (Load Balancer)

Read the full incident report →

Minor May 4, 2026

MongoDB: down for 5 minutes

Detected by Pingoru: May 04, 2026, 03:59 PM UTC
Resolved: May 04, 2026, 04:04 PM UTC
Duration: 5m

Affected: MongoDB

Read the full incident report →

Minor May 4, 2026

Node Server (Load Balancer): down for 5 minutes

Detected by Pingoru: May 04, 2026, 03:59 PM UTC
Resolved: May 04, 2026, 04:04 PM UTC
Duration: 5m

Affected: Node Server (Load Balancer)

Read the full incident report →

Minor May 4, 2026

Redis Service: down for 5 minutes

Detected by Pingoru: May 04, 2026, 03:59 PM UTC
Resolved: May 04, 2026, 04:04 PM UTC
Duration: 5m

Affected: Redis Service

Read the full incident report →

Minor May 4, 2026

Public API: incident detected for 6m

Detected by Pingoru: May 04, 2026, 03:58 PM UTC
Resolved: May 04, 2026, 04:05 PM UTC
Duration: 6m

Affected: Public API

Read the full incident report →

Minor May 4, 2026

Public API: down for 6 minutes

Detected by Pingoru: May 04, 2026, 03:58 PM UTC
Resolved: May 04, 2026, 04:04 PM UTC
Duration: 6m

Affected: Public API

Read the full incident report →

Minor March 16, 2026

Node Server (Load Balancer): incident detected for 1m

Detected by Pingoru: Mar 16, 2026, 06:53 PM UTC
Resolved: Mar 16, 2026, 06:54 PM UTC
Duration: 1m

Affected: Node Server (Load Balancer)

Read the full incident report →

Major March 3, 2026

Node Server 3 (Falkenstein): incident detected for 21m

Detected by Pingoru: Mar 03, 2026, 01:06 PM UTC
Resolved: Mar 03, 2026, 01:27 PM UTC
Duration: 21m

Affected: Node Server 3 (Falkenstein)

Read the full incident report →