Razer Outage History
Razer is up right nowPingoru has recorded 42 incidents for Razer: 0 in the last 12 months and 0 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 | 0 | 0 of 744 (0%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 0 | 0 of 744 (0%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 0 | 0 of 527 (0%) |
Incidents, newest first
Minor October 20, 2025 Razer Gold - Degradation of service 9h 15m Razer Gold & Silver
Started Oct 20, 2025, 04:13 PM UTC· resolved Oct 21, 2025, 01:28 AM UTC
- identified Oct 20, 2025, 04:13 PM UTC
Razer Gold and Silver service degradation Identified
- resolved Oct 21, 2025, 01:28 AM UTC
Services has been restored.
Major October 20, 2025 RazerID : Degradation of service 20h 23m Razer ID, Razer Synapse
Started Oct 20, 2025, 08:02 AM UTC· resolved Oct 21, 2025, 04:26 AM UTC
- investigating Oct 20, 2025, 08:02 AM UTC
RazerID service degradation observed. We are currently investigating the issue.
- investigating Oct 20, 2025, 08:03 AM UTC
We are continuing to investigate this issue.
- identified Oct 20, 2025, 08:26 AM UTC
team is working with the Cloud Service Provider to recover the service. Service degradation is still observed.
- identified Oct 20, 2025, 03:16 PM UTC
The Cloud Service Provider is still working towards a full resolution. Service degradation continues to be observed.
- monitoring Oct 20, 2025, 09:08 PM UTC
The cloud service provider has implemented fixes, and we are seeing recovery in the previously degraded services.
- resolved Oct 21, 2025, 04:26 AM UTC
This incident has been resolved.
Minor February 10, 2025 RazerID: Login issues 1h 39m Razer Central
Started Feb 10, 2025, 12:38 PM UTC· resolved Feb 10, 2025, 02:17 PM UTC
- investigating Feb 10, 2025, 12:38 PM UTC
There is degradation of service on RazerID for user's who are logged in via software clients. Users may experience login issues. The team is investigating it.
- identified Feb 10, 2025, 12:58 PM UTC
The issue has been identified and a fix is being implemented.
- resolved Feb 10, 2025, 02:17 PM UTC
Fix was deployed and service has been restored.