Stova Outage History

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

Stova incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 21, 2026PHP Security Vulnerabilities (CVE-2026-109618 / CVE-2026-109619)The PHP 8.4.27 upgrade has been released to all Stova servers, resolving the issue of two critical PHP vulnerabilities (CVE-2026-109618 and CVE-2026-109619).7h 33mResolved
Oct 6, 2026Registration form links load blank sites for attendees on front endThe issue of registration links loading blank pages on front end for attendees was resolved.52 minResolved
Oct 2, 2026Email Delivery Issues for Email Beta Registration Blasts in APAC and EMEA RegionsThis incident has been resolved.6h 10mResolved
Aug 31, 2026Investigating issues with Exago reports on APAC serverA fix has been implemented by the Development team, and the issue has been resolved.12h 7mResolved
Jun 22, 2026504 Gateway Time-out errors on NA platformResolved – The 504 Gateway Time-out incident on the North America platform has now been fully resolved. We have been closely monitoring performance and services have been stable since the fix was implemented 5 hrs ago…5h 40mResolved
May 25, 2026Email delivery issues affecting accounts using Email V2 in the EU region.This incident has been resolved.1h 0mResolved
May 18, 2026Investigating - 504 Gateway Time-out errors on NA platformThis incident has been resolved.2 minResolved
May 15, 2026504 Gateway Time-out errors on North America platformThis incident has been resolved.2h 19mResolved
May 11, 2026EU Server - 504 Gateway Time-outResolved - The EU server is operating normally. The 504 Gateway Time-out errors have been cleared. Thank you for your patience.9 minResolved
May 4, 2026Investigating - Email Delivery Issues for Email V1 ClientsResolved - Email Delivery Issues for Email V1 Clients We have moved to a durable resolution for this issue. Rather than rely on temporary measures, we are migrating affected accounts to a more performant email server…562h 31mResolved
Feb 24, 2026Event Emails scheduled blasts delays in APACThis incident has been resolved.2h 15mResolved
Jan 29, 2026Investigating North America server downgraded performanceThis incident is resolved now.18 minResolved
Jan 28, 2026Degraded Performance accessing Websites and navigating the North American ServerThe issue of degraded performance accessing the Websites module and navigating the North American server was resolved now.2h 3mResolved
Jan 7, 2026Degraded Performance accessing Websites on the North American ServerThis incident has been resolved.37 minResolved

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 Stova 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 Stova 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 Stova 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 Stova outage in this window ran 23d 10h, against a mean recovery of 1d 19h. If you depend on Stova 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.