Stova Outage History

Started Oct 21, 2026, 03:08 PM UTC· resolved Oct 21, 2026, 10:42 PM UTC

1. identified Oct 21, 2026, 03:08 PM UTC

   We are aware of two critical PHP vulnerabilities (CVE-2026-109618 and CVE-2026-109619) disclosed today. PHP is in use on our platform, and our Security and DevOps teams are actively working on this. We are testing the recommended PHP configuration change as a temporary protection until the fix is in place. The official PHP security release is expected at 14:00 UTC today. Once released, the fix will be tested before being deployed to production. We will post updates here as each step is completed.

2. resolved Oct 21, 2026, 10:42 PM UTC

   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).

Read the full incident report →

Started Oct 06, 2026, 04:45 AM UTC· resolved Oct 06, 2026, 05:37 AM UTC

1. investigating Oct 06, 2026, 04:45 AM UTC

   We are currently investigating issue of registration links loading blank pages on front end for attendees. There is no impact on remaining modules Websites, Survey, Abstracts, Meeting Registration links are accessible on both front and back end.

2. identified Oct 06, 2026, 05:07 AM UTC

   The root cause of registration links loading blank pages was identified. Fix is going through final phase of testing and once completed will be deployed to live environment.

3. resolved Oct 06, 2026, 05:37 AM UTC

   The issue of registration links loading blank pages on front end for attendees was resolved.

Read the full incident report →

Started Oct 02, 2026, 02:48 AM UTC· resolved Oct 02, 2026, 08:58 AM UTC

1. investigating Oct 02, 2026, 02:48 AM UTC

   We are currently investigating email delivery issues for Email Beta registration blasts in APAC and EMEA Regions. System auto-triggered emails, Email Beta registration emails sent via Registrant List and scheduled Email Beta marketing emails blasts are not impacted. There is no impact on non Email Beta Clients with this solution being fully operational.

2. resolved Oct 02, 2026, 08:58 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 31, 2026, 12:41 AM UTC· resolved Aug 31, 2026, 12:49 PM UTC

1. investigating Aug 31, 2026, 12:41 AM UTC

   We are currently investigating the issue of Exago reports not displaying in Clients' accounts on APAC server.

2. investigating Aug 31, 2026, 04:28 AM UTC

   We are continuing the investigation of this issue.

3. identified Aug 31, 2026, 07:05 AM UTC

   The issue has been identified and fix is currently being tested on lower environment prior production release.

4. resolved Aug 31, 2026, 12:49 PM UTC

   A fix has been implemented by the Development team, and the issue has been resolved.

Read the full incident report →

Started Jun 22, 2026, 05:34 PM UTC· resolved Jun 22, 2026, 11:14 PM UTC

1. investigating Jun 22, 2026, 05:34 PM UTC

   We are currently investigating reports of users experiencing 504 Gateway Timeout errors on the NA platform. Our engineering team is actively working to identify the cause and restore normal service. We will provide further updates as more information becomes available.

2. monitoring Jun 22, 2026, 05:40 PM UTC

   A fix has been implemented, and our team is currently monitoring the platform to ensure services remain stable.

3. resolved Jun 22, 2026, 11:14 PM UTC

   Resolved – 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. Our engineering team has confirmed sustained recovery across all impacted components. We sincerely apologise for the disruption caused during this incident and thank you for your patience and understanding throughout.

Read the full incident report →

Started May 25, 2026, 02:58 PM UTC· resolved May 25, 2026, 03:58 PM UTC

1. identified May 25, 2026, 02:58 PM UTC

   We’re currently experiencing degraded performance impacting email delivery for accounts using Email V2 in the EU region. Mailgun has identified the issue, and a fix is being implemented. We apologize for the inconvenience and appreciate your patience.

2. monitoring May 25, 2026, 03:50 PM UTC

   A fix has been implemented, and Mailgun is monitoring the results.

3. resolved May 25, 2026, 03:58 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 18, 2026, 06:58 AM UTC· resolved May 18, 2026, 07:00 AM UTC

1. investigating May 18, 2026, 06:58 AM UTC

   We are currently investigating reports of 504 Gateway Time-out errors affecting users on app.etouches.com. Some requests may fail to load or time out during this period. Our engineering team is actively looking into the issue. The next update will be posted within 30 minutes or sooner if there is meaningful progress.

2. resolved May 18, 2026, 07:00 AM UTC

   This incident has been resolved.

Read the full incident report →

Started May 15, 2026, 08:08 AM UTC· resolved May 15, 2026, 11:21 AM UTC

1. investigating May 15, 2026, 08:08 AM UTC

   Investigating – 504 Gateway Time-out on North America Server We are investigating reports of 504 Gateway Time-out errors on our North America platform. The issue is being treated with high priority and our engineering team is engaged. Further updates will follow shortly.

2. investigating May 15, 2026, 09:01 AM UTC

   We are continuing to investigate this issue.

3. investigating May 15, 2026, 09:01 AM UTC

   Our engineering team continues to investigate the 504 Gateway Time-out errors affecting the North America platform. Root cause analysis is in progress, and all available resources have been engaged on priority. We do not have an ETA at this time. The next update will be shared within 30 minutes, or sooner if there is meaningful progress. We sincerely apologise for the continued disruption and appreciate your patience.

4. identified May 15, 2026, 09:59 AM UTC

   The issue has been identified and a fix is being implemented.

5. identified May 15, 2026, 10:00 AM UTC

   Monitoring– Our engineering team has identified the root cause of the 504 Gateway Time-out incident on the North America platform and corrective action has been taken. Services are progressively recovering and access is being restored for impacted clients. We are closely monitoring platform performance to ensure full and sustained recovery. A further update will be shared once services are fully stable. We sincerely apologise for the disruption caused and thank you for your patience throughout the incident.

6. monitoring May 15, 2026, 10:50 AM UTC

   A fix has been implemented and we are monitoring the results.

7. monitoring May 15, 2026, 10:52 AM UTC

   We are continuing to monitor for any further issues.

8. resolved May 15, 2026, 11:21 AM UTC

   This incident has been resolved.

Read the full incident report →

Started May 11, 2026, 08:27 AM UTC· resolved May 11, 2026, 08:37 AM UTC

1. investigating May 11, 2026, 08:27 AM UTC

   We are currently investigating reports of 504 Gateway Time-out errors affecting users accessing the platform on the EU server. Our team is aware of the issue and is working to restore service. Users in the EU region may experience intermittent timeouts or failed page loads. We will provide updates every 20 minutes until full service is restored.

2. resolved May 11, 2026, 08:37 AM UTC

   Resolved - The EU server is operating normally. The 504 Gateway Time-out errors have been cleared. Thank you for your patience.

Read the full incident report →

Started May 04, 2026, 11:19 PM UTC· resolved May 28, 2026, 09:50 AM UTC

1. investigating May 04, 2026, 11:19 PM UTC

   We are currently experiencing an intermittent deliverability issue with Email V1 Clients. During this time emails may not be received for some recipients. This will affect Registration, Marketing, Networking & Abstracts. We will provide updates regularly.

2. investigating May 05, 2026, 01:21 AM UTC

   We are continuing investigation of an intermittent Email Delivery Issues for Email V1 Clients.

3. monitoring May 05, 2026, 03:50 AM UTC

   The root cause of this issue has been identified: several of Stova’s IP addresses were added to the Spamhaus blocklist (DNSBLs) utilized by major ISPs. The affected IPs have since been removed from the Spamhaus blocklist. However, as mail systems do not query Spamhaus in real time, service improvements will become visible within 1–24 hours depending on cache clearance, with some instances potentially taking up to 48 hours. As a proactive measure, we have also submitted a request to Microsoft to remove the affected IPs from their blocking system. We will continue to monitor the situation closely and provide updates as needed.

4. investigating May 07, 2026, 01:44 PM UTC

   The email delivery issue affecting Email V1 clients has expanded. Our EU sending infrastructure is now also affected, in addition to the previously reported NA and APAC regions. Cause: One of our V1 sending IPs has been re-listed on the Spamhaus blocklist, and our EU sending IP has also been listed. We are working directly with Spamhaus to identify the underlying cause and to prevent further listings. Actions taken: Delisting requests have been raised with Spamhaus for all affected sending IPs and domains Direct delisting requests have been submitted to Microsoft to speed up clearance on their internal systems Our development team is reviewing sending patterns and authentication configurations across V1 client traffic to address contributing factors What to expect: Recipient mail systems do not query Spamhaus in real time. They cache results, typically for 1 to 24 hours, with some Microsoft systems taking up to 48 hours. Even after delisting, some emails may continue to bounce during this window until the caches refresh. We are monitoring V1 deliverability across all three regions and will update this page as the situation progresses.

5. investigating May 08, 2026, 09:37 AM UTC

   Identified - The email delivery issue affecting Email V1 clients across NA, APAC, and EU regions is ongoing. Our V1 sending IPs and associated domains remain listed on the Spamhaus blocklist, and Spamhaus has confirmed the listings are due to low reputation signals from associated domains. Cause: There is no direct contact channel with Spamhaus and no guaranteed response time on our delisting tickets. Recipient mail systems also cache blocklist results, typically for 1 to 24 hours, with some Microsoft systems taking up to 48 hours. Even after delisting completes, emails may continue to bounce during this cache window. Actions taken: Delisting requests have been raised with Spamhaus for all affected sending IPs and domains Direct delisting requests have been submitted to Microsoft to speed up clearance on their internal systems Our development team is reviewing sender authentication patterns (SPF, DKIM, DMARC) across V1 client traffic to address contributing factors and reduce the likelihood of re-listing Recovery path: Affected clients have been contacted directly with two migration options to restore reliable sending: migration to our more performant email server (Mailgun-backed) or connection to your own SMTP server. To opt in to either path, or to enquire further, please contact [email protected].

6. identified May 08, 2026, 09:39 AM UTC

   The issue has been identified and a fix is being implemented.

7. identified May 08, 2026, 09:47 AM UTC

   We are continuing to work on a fix for this issue.

8. investigating May 13, 2026, 07:48 AM UTC

   The status of the V1 email delivery issue remains under active investigation. Spamhaus and Microsoft delisting requests remain open across all affected V1 sending IPs and associated domains. Neither provider publishes processing timelines, and we are not in a position to forecast a confirmed delisting date. We will continue to push both tracks and update this page as the position changes. In parallel, our V2 email migration programme is running at pace. V2 is Mailgun-backed with dedicated DKIM and SPF authentication per client domain, and routes around the V1 IP reputation issue entirely. Clients already on V2 are unaffected by the current V1 listings. What clients on V1 should expect: Email delivery from V1 may remain intermittent until Spamhaus delisting completes and recipient mail system caches refresh (typically 1 to 24 hours after delisting, with some Microsoft systems taking up to 48 hours). Bounces and low open rates during this window should be assumed to be incident-related. Recovery path: Clients wishing to opt in to the V2 or V3 (SMTP) migration, or who need delivery logs for affected sends, should contact [email protected] and reference this incident. We are fast-tracking migration requests. We will continue to monitor V1 deliverability across NA, APAC, and EU regions, and update this page as the situation progresses.

9. investigating May 21, 2026, 02:37 PM UTC

   The V1 email delivery issue remains under active investigation. Delisting requests for our NA and EU sending IPs remain open with Spamhaus and Microsoft, and both tracks are being actively pushed. Neither provider publishes processing timelines, so we are not able to confirm a delisting date. Our AU region has progressed and is under verification. Clients who need reliable sending sooner can opt in to our V2 or V3 (SMTP) migration by contacting [email protected] and referencing this incident. We are fast-tracking migration requests. We will continue to monitor and update this page as the position is confirmed.

10. investigating May 21, 2026, 02:38 PM UTC

    We are continuing to investigate this issue.

11. resolved May 28, 2026, 09:50 AM UTC

    Resolved - 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 (V2 or V3 SMTP) that provides stronger, more reliable deliverability and routes around the V1 reputation issue entirely. Our support team is reaching out directly to affected clients to begin this migration, which can typically be completed within 24 to 48 hours once DNS updates are in place. Clients who want to start sooner can contact [email protected] and reference this incident, and we will prioritise the setup. We are marking this incident resolved here, as all further action is moving to direct migration with affected clients. For any questions, please contact [email protected]

Read the full incident report →

Started Feb 24, 2026, 03:12 AM UTC· resolved Feb 24, 2026, 05:27 AM UTC

1. investigating Feb 24, 2026, 03:12 AM UTC

   We have been investigating reports of a delay in sending outbound emails in APAC. This will affect Registration event emails scheduled via schedule email blast feature. We will provide updates regularly.

2. identified Feb 24, 2026, 03:43 AM UTC

   The issue causing delays in processing event email scheduled blasts has been identified and a fix is being implemented.

3. monitoring Feb 24, 2026, 04:29 AM UTC

   A fix for the issue has been applied and we can see the Registration event emails scheduled via schedule email blasts sending without delays again. We continue to monitor the fix.

4. resolved Feb 24, 2026, 05:27 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 29, 2026, 08:39 AM UTC· resolved Jan 29, 2026, 08:58 AM UTC

1. investigating Jan 29, 2026, 08:39 AM UTC

   We are currently investigating this issue.

2. resolved Jan 29, 2026, 08:58 AM UTC

   This incident is resolved now.

Read the full incident report →

Started Jan 28, 2026, 10:46 PM UTC· resolved Jan 29, 2026, 12:49 AM UTC

1. investigating Jan 28, 2026, 10:46 PM UTC

   We're experiencing degraded performance accessing the Websites module and navigating the North American server. We are currently looking into the issue. We will continue to post updates throughout the process.

2. identified Jan 28, 2026, 11:02 PM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring Jan 28, 2026, 11:07 PM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved Jan 29, 2026, 12:49 AM UTC

   The issue of degraded performance accessing the Websites module and navigating the North American server was resolved now.

Read the full incident report →

Started Jan 07, 2026, 09:10 PM UTC· resolved Jan 07, 2026, 09:47 PM UTC

1. investigating Jan 07, 2026, 09:17 PM UTC

   We're experiencing degraded performance accessing the Websites module on the North American server and are currently looking into the issue. We will continue to post updates throughout the process.

2. identified Jan 07, 2026, 09:21 PM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring Jan 07, 2026, 09:32 PM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved Jan 07, 2026, 09:47 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 20, 2025, 07:38 PM UTC· resolved Oct 20, 2025, 10:38 PM UTC

1. investigating Oct 20, 2025, 07:38 PM UTC

   We have been investigating reports of a delay in sending outbound emails, this will affect Registration, Marketing, Networking & Abstracts. We will provide updates regularly as we have more information.

2. resolved Oct 20, 2025, 10:38 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 20, 2025, 04:59 PM UTC· resolved Oct 20, 2025, 09:09 PM UTC

1. investigating Oct 20, 2025, 04:59 PM UTC

   We’re currently experiencing degraded performance issues related to the Abstracts Module. Our team is currently working to restore normal performance levels. We apologize for any inconvenience and will continue to provide updates.

2. investigating Oct 20, 2025, 06:21 PM UTC

   Our team is continuing to investigate this issue. We apologize for the inconvenience and will continue to provide updates as we have more information.

3. resolved Oct 20, 2025, 09:09 PM UTC

   This incident has been resolved.

Read the full incident report →