StreamGuys Outage History
9 incidents recorded over the last 365 days, 2 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 StreamGuys Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 21, 2026 | Scheduled maintenance — PHP security patch rolloutThe scheduled maintenance has been completed. | 8h 0m | Scheduled |
| Jul 21, 2026 | Internet Gateway MigrationThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Mar 16, 2026 | SGreports MaintenanceThe scheduled maintenance has been completed. | 7h 0m | Scheduled |
| Feb 19, 2026 | SGrecast OS & Security UpdatesThe scheduled maintenance has been completed. | 3h 0m | Scheduled |
| Jan 27, 2026 | SGrecast OS & Security UpdatesThe scheduled maintenance has been completed. | 4h 0m | Scheduled |
| Jan 21, 2026 | SGreports Scheduled MaintenanceThe scheduled maintenance is completed. | 5h 0m | Scheduled |
| Nov 24, 2025 | SGreports OutageThe reporting systems are showing healthy, with backfill processes underway. We will continue to monitor extra-closely while the backfill process completes. Expect to see full data sets within the next 24 to 28 hours… | 6h 11m | Resolved |
| Nov 18, 2025 | SGreports v2 Hardware MaintenanceThe scheduled maintenance has been completed. | 5h 0m | Scheduled |
| Nov 11, 2025 | Intermittent DNS ResolutionIntermittent DNS resolution failures for streamguys1.com zone affecting some streaming clients. Issue identified and resolved within 10 minutes. | -5379 min | Resolved |
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 StreamGuys 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 StreamGuys 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 StreamGuys 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 StreamGuys outage in this window ran 8h, against a mean recovery of 4h 54m. If you depend on StreamGuys 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.