Virtuagym Outage History

Virtuagym is up right now

Virtuagym had 7 outages in the last 2 years totaling 56h 33m of downtime — averaging 0.3 incidents per month.

There were 7 Virtuagym outages since July 1, 2025 totaling 56h 33m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.virtuagym.com

Major March 17, 2026

Activity-Instances Database Connection Exhaustion

Detected by Pingoru
Mar 17, 2026, 04:17 PM UTC
Resolved
Mar 16, 2026, 05:30 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Mar 17, 2026, 04:17 PM UTC

    Our activity-instances database experienced connection exhaustion during peak traffic, causing errors on mobile API endpoints (food, activity, plans) and Fitbit sync. Idle connections accumulated beyond the server's limit, leading to rejected requests and degraded performance. The issue has been resolved by adjusting connection timeout and limit parameters. All services are operating normally.

Read the full incident report →

Major February 5, 2026

Intermittent Database Load Issues

Detected by Pingoru
Feb 05, 2026, 04:03 PM UTC
Resolved
Feb 05, 2026, 08:48 PM UTC
Duration
4h 45m
Affected: WebsiteMobile AppsAPI
Timeline · 4 updates
  1. investigating Feb 05, 2026, 04:03 PM UTC

    We identified an issue affecting payment processing, primarily related to Mollie payments which has increased system load following a third party outage. We are currently investigating.

  2. monitoring Feb 05, 2026, 04:20 PM UTC

    As a result of a payment provider outage, a large number of requests were sent to our payment webhook endpoint, which led to increased database load. We have reduced the number of workers processing these requests to prevent further overload and stabilize the system.

  3. monitoring Feb 05, 2026, 05:58 PM UTC

    Performance levels have now stabilised but we keep on monitoring in the following hours to act if necessary.

  4. resolved Feb 05, 2026, 08:48 PM UTC

    This incident has been resolved.

Read the full incident report →

Major February 5, 2026

Mollie - iDEAL Payments Failing via Invoice Payment Links

Detected by Pingoru
Feb 05, 2026, 10:50 AM UTC
Resolved
Feb 05, 2026, 04:18 PM UTC
Duration
5h 27m
Affected: Website
Timeline · 3 updates
  1. identified Feb 05, 2026, 10:50 AM UTC

    We are investigating an issue where some iDEAL payments made via invoice payment links fail when clients are not logged in. The cause has been identified and a fix is currently being worked on.

  2. monitoring Feb 05, 2026, 02:23 PM UTC

    We have deployed a fix for the issue and are actively monitoring the system to ensure stability. At this time, all services are operating as expected.

  3. resolved Feb 05, 2026, 04:18 PM UTC

    This incident has been resolved.

Read the full incident report →

Major November 18, 2025

Database Performance Issues

Detected by Pingoru
Nov 18, 2025, 08:30 AM UTC
Resolved
Nov 18, 2025, 04:00 PM UTC
Duration
7h 29m
Affected: WebsiteMobile AppsAPI
Timeline · 3 updates
  1. investigating Nov 18, 2025, 08:30 AM UTC

    We are currently investigating an issue with our database performance.

  2. monitoring Nov 18, 2025, 09:00 AM UTC

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

  3. resolved Nov 18, 2025, 04:00 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 5, 2025

Check-in Client Connection Issues Following TLS Protocol Update

Detected by Pingoru
Nov 05, 2025, 10:19 AM UTC
Resolved
Nov 05, 2025, 11:41 AM UTC
Duration
1h 22m
Affected: API
Timeline · 2 updates
  1. investigating Nov 05, 2025, 10:19 AM UTC

    After the scheduled deprecation of outdated TLS 1.0 and 1.1 protocols to enhance platform security, some clients reported that their Check-in Clients could no longer connect, displaying the message “Server couldn’t be reached.” Initial investigation confirmed that affected clients were running outdated Check-in Client versions that do not support the new TLS configuration. While the Virtuagym Portal remains functional, the legacy Check-in applications (pre-1.4.8) are unable to establish connections under the updated standards. Engineering is currently verifying whether any configurations deviate from the tested setups. Customers experiencing connection issues are advised to engage with our hardware and integrations specialist through Customer Success. Further updates will be provided as the team completes troubleshooting and determines whether a rollback or fix is required.

  2. resolved Nov 05, 2025, 11:41 AM UTC

    Following the scheduled maintenance to disable outdated TLS 1.0 and 1.1 protocols on November 5th at 09:00 UTC, a few reports were received indicating that certain Check-in Clients were unable to connect to the server. Investigation determined that these incidents were not caused by the TLS protocol update. The affected setups were running unsupported or misconfigured Check-in Client versions, which were unable to establish secure connections due to local configuration issues. The TLS deprecation has been verified to operate as intended, and no rollback is required. Next Steps: • Monitoring continues to ensure system stability post-upgrade. • Configuration inconsistencies identified during the investigation are being tracked internally for follow-up.

Read the full incident report →

Notice October 20, 2025

Monitoring AWS Outage Impact

Detected by Pingoru
Oct 20, 2025, 09:55 AM UTC
Resolved
Oct 21, 2025, 07:44 AM UTC
Duration
21h 48m
Affected: WebsiteMobile AppsAPI
Timeline · 3 updates
  1. monitoring Oct 20, 2025, 09:55 AM UTC

    We are monitoring a widespread AWS outage (https://health.aws.amazon.com/health/status) that may impact parts of our platform. At this time, we have not observed any platform degradation, but we are actively assessing our systems and will update if any impact occurs.

  2. monitoring Oct 20, 2025, 03:35 PM UTC

    We are continuing to monitor the widespread AWS outage (https://health.aws.amazon.com/health/status). At this time, all components of our platform remain fully operational and we have received no reports of degraded performance or connectivity issues. We will keep monitoring the situation closely and will provide further updates if anything changes.

  3. resolved Oct 21, 2025, 07:44 AM UTC

    The downstream provider has resolved their incident.

Read the full incident report →

Major July 1, 2025

Appointment Schedule Performance

Detected by Pingoru
Jul 01, 2025, 04:48 PM UTC
Resolved
Jul 02, 2025, 08:27 AM UTC
Duration
15h 39m
Affected: Website
Timeline · 3 updates
  1. investigating Jul 01, 2025, 04:48 PM UTC

    We’re currently experiencing an issue where events in the appointment schedule are either not loading or loading very slowly. Our team is actively investigating the root cause and working to resolve the issue as quickly as possible. We’ll share an update as soon as we have more information.

  2. monitoring Jul 01, 2025, 05:38 PM UTC

    We have found the cause and deployed a fix to production. We are now closely monitoring the system to make sure everything is working properly. Thank you for your patience.

  3. resolved Jul 02, 2025, 08:27 AM UTC

    This incident has been resolved.

Read the full incident report →