SpyCloud Outage History
5 incidents recorded over the last 365 days, 4 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 SpyCloud Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 21, 2026 | PHP NewsSpyCloud is not affected by the critical PHP vulnerabilities CVE-2026-109618 and CVE-2026-109619 disclosed on October 21, 2026, as none of our products, infrastructure, or other assets use PHP. We are monitoring… | 292h 8m | Resolved |
| Sep 8, 2026 | spycloud.com Website IssueThis incident has been resolved. | 14 min | Resolved |
| Aug 15, 2026 | CAP, INV, SIP API Performance FixThe scheduled maintenance has been completed. | 5 min | Scheduled |
| Jul 16, 2026 | Console.SpyCloud.comThe service disruption has been resolved. We're sorry for any inconvenience this may have caused. | 1h 56m | Resolved |
| Nov 18, 2025 | Intermittent Service Degradation – Portal, Console, & SpyCloud.comThe behavior tied to today's Cloudflare incident has been resolved. All websites have been restored. | 5h 36m | 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 SpyCloud 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 SpyCloud 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 SpyCloud 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 SpyCloud outage in this window ran 12d 4h, against a mean recovery of 2d 11h. If you depend on SpyCloud 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.