GameBoost Outage History

19 incidents recorded over the last 365 days, 19 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.

Live GameBoost status99.19% uptime history

Every Recorded GameBoost Incident

GameBoost incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 29, 2026Chat API is down147h 12mResolved
Oct 22, 2026Main is down318h 46mResolved
Oct 14, 2026Main is down516h 48mResolved
Oct 13, 2026Chat API is down545h 12mResolved
Sep 22, 2026Main is down1058h 11mResolved
Sep 18, 2026Chat API is down1146h 0mResolved
Sep 13, 2026Main is down1257h 33mResolved
Sep 4, 2026Main is down1480h 56mResolved
Aug 27, 2026Main is down1565h 54mResolved
Aug 20, 2026Main is down1741h 52mResolved
Aug 19, 2026Main is down1761h 2mResolved
Aug 13, 2026Main is down1916h 33mResolved
Aug 2, 2026Main is down2160h 20mResolved
Jul 30, 2026Chat API is down1495h 25mResolved
Jul 29, 2026Main is down1521h 38mResolved
Jul 23, 2026Main is down1666h 28mResolved
Jul 17, 2026Main is down1814h 8mResolved
Jul 2, 2026Main is down2177h 0mResolved
Jun 11, 2026Main is down1944h 32mResolved

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 GameBoost 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 GameBoost 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 GameBoost 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 GameBoost outage in this window ran 90d 17h, against a mean recovery of 57d 12h. If you depend on GameBoost 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.