Shockbyte status history
Current state: operational — “All Systems Operational” per https://status.shockbyte.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Shockbyte incidents last?
From 8 incidents with a vendor-posted start and resolve time. Longest on record: [Game Servers] Service Interruption — 21.3 h (2026-07-30 12:00 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.
Incidents on record (8)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-09-13 10:10 UTC | Service Disruption for existing servers | resolved | major | 1 h 55 min |
| 2026-08-19 05:40 UTC | [Game Servers] Service Disruption on New Servers/Instances | resolved | major | 2 h 09 min |
| 2026-07-30 12:00 UTC | [Game Servers] Service Interruption | resolved | critical | 21 h 20 min |
| 2026-07-19 14:43 UTC | [Game Servers, NA East] Service Interruption | resolved | minor | 42 min |
| 2026-07-15 07:47 UTC | [Game Servers, AU] Service Interruption | resolved | none | 57 min |
| 2026-06-20 16:47 UTC | Germany (Frankfurt) Game Servers Down | resolved | critical | 2 h 55 min |
| 2026-05-29 05:08 UTC | [PANEL] Server type version switching non-operational | resolved | minor | 1 h 07 min |
| 2026-04-21 14:27 UTC | Plugins being wiped on server restart | resolved | minor | 50 min |
Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).
Watch Shockbyte with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"shockbyte"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}