Virtuagym Outage History

Virtuagym is up right now

Virtuagym had 10 outages in the last 2 years totaling 77h 24m of downtime — averaging 0.4 incidents per month.

There were 10 Virtuagym outages since October 20, 2025 totaling 77h 24m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.virtuagym.com

Critical September 28, 2026

Appointment Schedule Performance

Detected by Pingoru
Sep 28, 2026, 01:40 PM UTC
Resolved
Sep 29, 2026, 08:07 AM UTC
Duration
18h 27m
Affected: WebsiteMobile AppsAPI
Timeline · 3 updates
  1. investigating Sep 28, 2026, 01:40 PM UTC

    We’re currently experiencing an outage in the Appointment Schedule. Our team is investigating the issue and working to restore normal performance as soon as possible.

  2. monitoring Sep 28, 2026, 03:02 PM UTC

    We identified the issue and deployed a fix. The Appointment Schedule should now be working as expected again. We’ll continue to monitor the situation closely to make sure the issue does not occur again.

  3. resolved Sep 29, 2026, 08:07 AM UTC

    The incident has been resolved.

Read the full incident report →

Major September 18, 2026

Error spikes on web and api requests

Detected by Pingoru
Sep 18, 2026, 09:22 PM UTC
Resolved
Sep 18, 2026, 09:35 PM UTC
Duration
12m
Affected: WebsiteMobile AppsAPI
Timeline · 3 updates
  1. investigating Sep 18, 2026, 09:22 PM UTC

    We are currently investigating a spike in web and api request errors.

  2. monitoring Sep 18, 2026, 09:31 PM UTC

    A database lock prevented any other operation from completing. The lock has been released and we are now monitoring. All components are back to normal operation.

  3. resolved Sep 18, 2026, 09:35 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 1, 2026

SEPA file generation

Detected by Pingoru
Jul 01, 2026, 07:39 AM UTC
Resolved
Jul 01, 2026, 05:53 PM UTC
Duration
10h 13m
Affected: Website
Timeline · 3 updates
  1. investigating Jul 01, 2026, 07:39 AM UTC

    We're currently investigating an issue that is preventing customers from downloading SEPA files. We expect to identify the reason and issue a fix as soon as possible. Apologies for the inconvenience that this is bringing.

  2. monitoring Jul 01, 2026, 01:34 PM UTC

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

  3. resolved Jul 01, 2026, 05:53 PM UTC

    This incident has been resolved.

Read the full incident report →

Major June 10, 2026

Android apps – Connectivity Issues

Detected by Pingoru
Jun 10, 2026, 08:23 AM UTC
Resolved
Jun 10, 2026, 04:00 PM UTC
Duration
7h 37m
Affected: Mobile Apps
Timeline · 6 updates
  1. investigating Jun 10, 2026, 08:23 AM UTC

    We are currently experiencing an issue affecting all Android applications, including Fitness, Food, Coach, Touch, and Custom Mobile Apps (CMA). Due to a connectivity problem, users may be unable to log in, sync data, view schedules, or access other app features and services. Our team has identified the cause and released a fix, which is currently being rolled out through updated app versions. For our standard Android apps (Fitness, Food, Coach, and Touch), the update is currently being made available to users. Custom Mobile Apps (CMA) are also affected. The rollout of updated CMA versions is currently in progress and remains our highest priority. We will continue to provide updates on this page as more information becomes available. We sincerely apologize for the inconvenience and appreciate your patience while we work to fully resolve this issue.

  2. investigating Jun 10, 2026, 08:25 AM UTC

    We are continuing to investigate this issue.

  3. identified Jun 10, 2026, 08:26 AM UTC

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

  4. identified Jun 10, 2026, 11:19 AM UTC

    The Food and Coach Android apps are operational again. A number of Custom Mobile Apps (CMA) have also been updated and are operational. The rollout for the remaining Android apps and CMA versions is still in progress.

  5. identified Jun 10, 2026, 03:10 PM UTC

    Rollout of the updated Android app versions is progressing as planned. Additional apps are continuing to become available through the Google Play Store. Affected users will need to update their app once the updated version becomes available. We will continue to provide updates as the rollout progresses.

  6. resolved Jun 10, 2026, 04:00 PM UTC

    The Android connectivity issue has been resolved, and affected apps are operational again. The issue was caused by an external change affecting Android applications. Service has since been restored, and users should now be able to log in, sync data, access schedules, and use app functionality normally. As an additional preventative measure, we will continue rolling out updated app versions across all Android apps and Custom Mobile Apps (CMAs) to reduce the risk of similar issues occurring in the future. If you are still experiencing issues, please contact our support team at [email protected]. We sincerely apologize for the inconvenience and thank you for your patience throughout this incident.

Read the full incident report →

Major March 16, 2026

Activity-Instances Database Connection Exhaustion

Detected by Pingoru
Mar 16, 2026, 05:30 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 →