Shockbyte Outage History
26 incidents recorded over the last 365 days, 26 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Shockbyte Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 26, 2026 | [Upstream] SteamCMD OutageThe upstream issue is now resolved. | 2h 1m | Resolved |
| Oct 26, 2026 | [Game Servers, US West] Upgrades to New HardwareMaintenance has started | 2h 13m | Resolved |
| Oct 22, 2026 | [Game Servers, US West] Upgrades to New HardwareMaintenance has started | 10h 3m | Resolved |
| Oct 20, 2026 | Test IncidentNothing continued to happen | 49 min | Resolved |
| Oct 19, 2026 | [Game Servers, US West] Upgrades to New HardwareMaintenance has started | 9h 4m | Resolved |
| Oct 15, 2026 | [Game Servers, US West] Upgrades to New HardwareMaintenance has started | 4h 43m | Resolved |
| Oct 8, 2026 | [Game Servers, NA] Server Availabilty IssuesThe affected infrastructure is back to full health. The remaining game servers are starting up, and customers have full control of their servers. | 4h 17m | Resolved |
| Oct 6, 2026 | [Games Servers, Texas] Network Routing Performance DegradationThis issue has been resolved. | 4h 52m | Resolved |
| Oct 4, 2026 | [Game Servers, NA] Partial Service OutageThis incident is now resolved, and all affected servers are back online. | 2h 2m | Resolved |
| Oct 2, 2026 | Steam Games Failing to Update/InstallThis incident has since been resolved. | 7h 52m | Resolved |
| Oct 1, 2026 | [Game Servers, US East] Upgrades to New HardwareMaintenance has started | 2h 20m | Resolved |
| Sep 29, 2026 | [Game Servers, North America West] - Scheduled Infrastructure MaintenanceThe maintenance in Oregon, US is taking longer than expected to complete. | 5h 26m | Resolved |
| Sep 29, 2026 | [Game Servers, US East] Upgrades to New HardwareMaintenance has started | 2h 18m | Resolved |
| Sep 22, 2026 | [Game Servers, PL] Intermittent Network Issues The incident was resolved by the upstream provider at 23:50 UTC. | 7h 46m | Resolved |
| Sep 13, 2026 | Service Disruption for existing serversThis issue should now be resolved. | 1h 55m | Resolved |
| Sep 10, 2026 | [Game Servers, North America East] - Scheduled Infrastructure MaintenanceMaintenance has started | 436h 2m | Resolved |
| Sep 10, 2026 | [Game Servers, Europe] - Scheduled Infrastructure MaintenanceMaintenance has been completed in all regions except Frankfurt, Germany which is still ongoing. | 337h 48m | Resolved |
| Sep 10, 2026 | [Game Servers, APAC & Australia] - Scheduled Infrastructure Maintenance Maintenance complete for our Mumbai, India region. | 314h 57m | Resolved |
| Aug 19, 2026 | [Game Servers] Service Disruption on New Servers/InstancesThis incident is now resolved. If you are still running into issues with your server, please reach out to our support team. | 2h 9m | Resolved |
| Jul 30, 2026 | [Game Servers] Service InterruptionThis incident has since been resolved. | 21h 20m | Resolved |
| Jul 27, 2026 | [Game Servers, US East] Upgrades to New HardwareMaintenance has started | 368h 3m | Resolved |
| Jul 19, 2026 | [Game Servers, NA East] Service InterruptionThis incident is now resolved. | 42 min | Resolved |
| Jul 15, 2026 | [Game Servers, AU] Service InterruptionThis incident is now resolved. All affected services are back up and running. | 57 min | Resolved |
| Jun 20, 2026 | Germany (Frankfurt) Game Servers DownThis incident is now resolved. | 2h 55m | Resolved |
| May 29, 2026 | [PANEL] Server type version switching non-operationalThis issue is now resolved. | 1h 7m | Resolved |
| Apr 21, 2026 | Plugins being wiped on server restartThis incident is now resolved, and we're working to restore the server files of a few affected customers. | 50 min | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Shockbyte incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Shockbyte Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Shockbyte acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Shockbyte outage in this window ran 18d 4h, against a mean recovery of 2d 11h. If you depend on Shockbyte in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.