Pcgamingwiki Outage History

8 incidents recorded over the last 365 days, 8 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 Pcgamingwiki Incident

Pcgamingwiki incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Nov 4, 2026Service Community seems to be down4 minResolved
Sep 15, 2026Service Community seems to be down9h 14mResolved
Sep 9, 2026Service Community seems to be down2 minResolved
Sep 9, 2026Service Community seems to be down6 minResolved
Sep 8, 2026Service Community seems to be down8 minResolved
Sep 4, 2026Service Community seems to be down27 minResolved
Sep 4, 2026Service Community seems to be down9 minResolved
Sep 4, 2026Service Community seems to be down1h 18mResolved

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 Pcgamingwiki 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 Pcgamingwiki 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 Pcgamingwiki 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 Pcgamingwiki outage in this window ran 9h 14m, against a mean recovery of 1h 26m. If you depend on Pcgamingwiki 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.