Shockbyte experienced a minor incident on July 31, 2026 affecting Quebec, CA and Virginia, US and 1 more component, lasting —. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jul 30, 2026, 12:00 PM UTC
Status: Investigating We are seeing issues on game servers on our Hillsboro cluster, we are investigating. Affected components Oregon, US (Partial outage)
- identified Jul 30, 2026, 01:10 PM UTC
Status: Identified We're seeing issues throughout all our game server regions, we have identified the issue and are working on a solution as quick as possible. Affected components Melbourne, AU (Degraded performance) Roubaix, FR (Degraded performance) Texas, US (Degraded performance) Tokyo, JP (Degraded performance) Virginia, US (Degraded performance) Quebec, CA (Degraded performance) London, UK (Degraded performance) Amsterdam, NL (Degraded performance) Gravelines, FR (Degraded performance) Oregon, US (Degraded performance) Singapore, SG (Degraded performance) California, US (Degraded performance) Florida, US (Degraded performance) Mumbai, IN (Degraded performance) Sydney, AU (Degraded performance) Frankfurt, DE (Degraded performance)
- identified Jul 30, 2026, 02:34 PM UTC
Status: Identified We have resolved the issues impacting our wider services. We are rolling out fixes to Oregon US and Melbourne AU. Affected components Quebec, CA (Operational) London, UK (Operational) Sydney, AU (Operational) Frankfurt, DE (Operational) Texas, US (Operational) Mumbai, IN (Operational) Melbourne, AU (Degraded performance) Roubaix, FR (Operational) Virginia, US (Operational) Florida, US (Operational) Singapore, SG (Operational) Amsterdam, NL (Operational) Gravelines, FR (Operational) Oregon, US (Full outage) California, US (Operational) Tokyo, JP (Operational)
- monitoring Jul 30, 2026, 07:04 PM UTC
Status: Monitoring The root cause has been identified and resolved. Game servers in Oregon (US) and Melbourne (AU) are now operational again. Affected components Mumbai, IN (Operational) Sydney, AU (Operational) California, US (Operational) Singapore, SG (Operational) London, UK (Operational) Roubaix, FR (Operational) Oregon, US (Operational) Texas, US (Operational) Melbourne, AU (Operational) Amsterdam, NL (Operational) Gravelines, FR (Operational) Virginia, US (Operational) Quebec, CA (Operational) Frankfurt, DE (Operational) Florida, US (Operational) Tokyo, JP (Operational)
- resolved Jul 31, 2026, 09:20 AM UTC
Status: Resolved This incident has since been resolved. Affected components Frankfurt, DE (Operational) Virginia, US (Operational) Tokyo, JP (Operational) Mumbai, IN (Operational) Oregon, US (Operational) Quebec, CA (Operational) Melbourne, AU (Operational) Amsterdam, NL (Operational) California, US (Operational) Roubaix, FR (Operational) Texas, US (Operational) Florida, US (Operational) Singapore, SG (Operational) London, UK (Operational) Sydney, AU (Operational) Gravelines, FR (Operational)