Is Shockbyte down?

Last checked 3m ago
Current status
Shockbyte is up

No incidents right now.

Shockbyte is operational right now. Last checked 3m ago; the most recent incident resolved 6d ago.

Real-time Shockbyte status, recent outages, and incident history: pulled directly from Shockbyte's official status page at status.shockbyte.com every 5 minutes. Pingoru tracks 32 Shockbyte services and has captured 9 incidents in the last 90 days (99.31% uptime). Get email, Slack, Discord, or webhook alerts the moment Shockbyte reports a new incident, free for 3 monitors, no credit card.

Users who monitor Shockbyte also follow these Cloud Infrastructure services: Amazon Web Services DigitalOcean Cisco Umbrella Wasabi Vercel Hetzner HashiCorp Egnyte Dyn Genesys Cloud View all 8,000+ providers
Shockbyte uptime 99.31% uptime · past 90 days
Mon Wed Fri
AugSepOctNov
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 2h 1m
    Started Oct 26, 2026, 02:14 PM UTC · Resolved Oct 26, 2026, 04:15 PM UTC
    Timeline · 3 updates
    • identified · Oct 26, 2026, 02:14 PM UTC

      Status: Identified We're aware of an upstream issue which is affecting Steam. Game servers may be unable to update during this time. We're waiting for further developments.

    • resolved · Oct 26, 2026, 04:15 PM UTC

      Status: Resolved The upstream issue is now resolved.

    • resolved · Oct 26, 2026, 04:15 PM UTC

      Status: Resolved The upstream issue is now resolved.

    Latest: Status: Resolved The upstream issue is now resolved.

  2. Resolved 49m
    Started Oct 20, 2026, 09:16 AM UTC · Resolved Oct 20, 2026, 10:06 AM UTC
    Timeline · 2 updates
    • investigating · Oct 20, 2026, 09:16 AM UTC

      Status: Investigating This is only used for testing, Nothing happened

    • resolved · Oct 20, 2026, 10:06 AM UTC

      Status: Resolved Nothing continued to happen

    Latest: Status: Resolved Nothing continued to happen

  3. Resolved 4h 17m
    Started Oct 08, 2026, 02:32 PM UTC · Resolved Oct 08, 2026, 06:49 PM UTC
    Quebec, CAVirginia, USFlorida, USCalifornia, USMelbourne, AUTexas, USOregon, USWashington D.C., US
    Timeline · 7 updates
    • investigating · Oct 08, 2026, 02:32 PM UTC

      Status: Investigating We're aware of an issue impacting server availability in some regions, including California. Affected components Florida, US (Degraded performance) California, US (Degraded performance) Washington D.C., US (Degraded performance) Quebec, CA (Degraded performance) Oregon, US (Degraded performance) Texas, US (Degraded performance) Virginia, US (Degraded performance)

    • investigating · Oct 08, 2026, 02:42 PM UTC

      Status: Investigating We're continuing to work to identify the root cause. Affected components California, US (Degraded performance) Washington D.C., US (Operational) Quebec, CA (Operational) Melbourne, AU (Degraded performance) Oregon, US (Operational) Texas, US (Operational) Virginia, US (Degraded performance) Florida, US (Operational)

    • identified · Oct 08, 2026, 03:34 PM UTC

      Status: Identified We have identified the issue and are working on a solution. Affected components Washington D.C., US (Operational) Quebec, CA (Operational) Melbourne, AU (Degraded performance) Oregon, US (Operational) Texas, US (Operational) Virginia, US (Degraded performance) Florida, US (Operational) California, US (Degraded performance)

    • identified · Oct 08, 2026, 05:06 PM UTC

      Status: Identified We are beginning to bring affected servers back online in batches. Affected components Quebec, CA (Operational) Melbourne, AU (Operational) Oregon, US (Operational) Texas, US (Operational) Virginia, US (Operational) Florida, US (Operational) California, US (Degraded performance) Washington D.C., US (Operational)

    • monitoring · Oct 08, 2026, 05:50 PM UTC

      Status: Monitoring We have restored access to the Control Panel for affected customers, and we're continuing to start up servers. Customers may now start up their own servers. Affected components California, US (Degraded performance) Washington D.C., US (Operational) Quebec, CA (Operational) Melbourne, AU (Operational) Oregon, US (Operational) Texas, US (Operational) Virginia, US (Operational) Florida, US (Operational)

    • resolved · Oct 08, 2026, 06:49 PM UTC

      Status: Resolved The affected infrastructure is back to full health. The remaining game servers are starting up, and customers have full control of their servers. Affected components Virginia, US (Operational) Florida, US (Operational) California, US (Operational) Washington D.C., US (Operational) Quebec, CA (Operational) Melbourne, AU (Operational) Oregon, US (Operational) Texas, US (Operational)

    • resolved · Oct 08, 2026, 06:49 PM UTC

      Status: Resolved The affected infrastructure is back to full health. The remaining game servers are starting up, and customers have full control of their servers. Affected components Virginia, US (Operational) Florida, US (Operational) California, US (Operational) Washington D.C., US (Operational) Quebec, CA (Operational) Melbourne, AU (Operational) Oregon, US (Operational) Texas, US (Operational)

    Latest: Status: Resolved The affected infrastructure is back to full health. The remaining game servers are starting up, and customers have full control of their servers. Affected componen…

  4. Resolved 4h 52m
    Started Oct 06, 2026, 04:04 AM UTC · Resolved Oct 06, 2026, 08:56 AM UTC
    Texas, US
    Timeline · 6 updates
    • identified · Oct 06, 2026, 04:04 AM UTC

      Status: Identified We are aware of upstream issues affecting a few network routes in North America, which may result in players in the region having trouble connecting to their game servers in Dallas, Texas. We have identified the faulty upstreams and are working on a fix. Affected components Texas, US (Degraded performance)

    • monitoring · Oct 06, 2026, 04:11 AM UTC

      Status: Monitoring We have withdrawn from the affected network upstreams and are seeing no further network issues to the affected routes. We will continue monitoring. If you continue to have issues connecting to game servers, please try again after ~5 minutes. Thank you for your patience. Affected components Texas, US (Degraded performance)

    • identified · Oct 06, 2026, 04:24 AM UTC

      Status: Identified We are still investigating continued network degradation in the region. We apologise for any inconvenience caused and will continue to post updates. Affected components Texas, US (Partial outage)

    • monitoring · Oct 06, 2026, 05:42 AM UTC

      Status: Monitoring We are continuing to monitor the fixes in place. Affected components Texas, US (Operational)

    • resolved · Oct 06, 2026, 08:56 AM UTC

      Status: Resolved This issue has been resolved. Affected components Texas, US (Operational)

    • resolved · Oct 06, 2026, 08:56 AM UTC

      Status: Resolved This issue has been resolved. Affected components Texas, US (Operational)

    Latest: Status: Resolved This issue has been resolved. Affected components Texas, US (Operational)

  5. Resolved 2h 2m
    Started Oct 04, 2026, 04:25 PM UTC · Resolved Oct 04, 2026, 06:27 PM UTC
    Quebec, CA
    Timeline · 4 updates
    • investigating · Oct 04, 2026, 04:25 PM UTC

      Status: Investigating We're aware of an issue affecting some servers in our Quebec, Canada region. We're working to determine the root cause. Affected components Quebec, CA (Degraded performance)

    • identified · Oct 04, 2026, 04:41 PM UTC

      Status: Identified We have identified the root cause of the incident and applied a fix. Customer servers are beginning to recover. Affected components Quebec, CA (Degraded performance)

    • resolved · Oct 04, 2026, 06:27 PM UTC

      Status: Resolved This incident is now resolved, and all affected servers are back online. Affected components Quebec, CA (Operational)

    • resolved · Oct 04, 2026, 06:27 PM UTC

      Status: Resolved This incident is now resolved, and all affected servers are back online. Affected components Quebec, CA (Operational)

    Latest: Status: Resolved This incident is now resolved, and all affected servers are back online. Affected components Quebec, CA (Operational)

See the full Shockbyte outage history

4 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Shockbyte outage history →

Or sign up free to get alerts when Shockbyte breaks · 10 free monitors · No credit card

Incident record

Since April 2026 · incident.io · 32 components checked every 5 minutes
38incidents recorded
35last 12 months
9last 90 days
106 minutestypical duration, 12 months

The longest incident in the last year, [Game Servers] Service Interruption on July 30, 2026, ran for 21 hours. 43 maintenance windows announced in the same period.

Most affected components, last 12 months

  • Control Panel4
  • Quebec, CA3
  • Texas, US3
  • Virginia, US3
  • Amsterdam, NL2

Latest incidents

  • [Upstream] SteamCMD Outage October 26, 2026 · 2 hours · degraded service

    Status: Identified We're aware of an upstream issue which is affecting Steam. Game servers may be unable to update during this time. We're waiting for further…

  • Test Incident October 20, 2026 · 49 minutes · degraded service

    Status: Investigating This is only used for testing, Nothing happened

  • [Game Servers, NA] Server Availabilty Issues October 8, 2026 · 4 hours · degraded service

    Status: Investigating We're aware of an issue impacting server availability in some regions, including California. Affected components Florida, US (Degraded…

Outage history

Past 90 days · 9 incidents View full outage history →