Virtuagym 中断历史

1. 2026年10月21日 UTC 11:49investigating

   亲爱的顾客 正如你们在新闻中所看到的那样,已经发现了一个重大的安全弱点,它影响到全世界包括我们在内的大量网站和在线服务。 你的数据安全是我们的首要任务 像许多其他公司和组织一样,包括一些荷兰政府服务,我们暂时暂停了我们的服务,作为预防措施,同时我们采用了必要的安全补丁。 我们想向你们保证,Virtuagym软件和服务没有受到破坏,你们成员的数据也没有。 这种暂停纯粹是预防性的。 这对你意味着什么? 当服务下线时,你和你的会员将无法登录,预订课程或使用应用程序. 我们建议: 让会员知道暂时中断的事 如有必要,计划人工替代报到和预订 我们知道我们的平台对你的生意有多重要, 重新建立和运行它是我们的最高优先事项。 我们只有在这些安全补丁到位后才能重启服务,我们确信你的数据会受到保护. 您可以在此查看最新消息 。 服务一到,我们就会再发邮件给你.

2. 2026年10月21日 UTC 13:06investigating

   我们正在继续调查这一问题.

3. 2026年10月21日 UTC 15:32identified

   全球PHP开发团队发布了一个官方的补丁,以弥补导致我们和许多其他公司作为防范措施将我们的系统下线的脆弱性。 PHP是被广泛使用的编程语言,我们的平台主要以这种语言为基础. Virtuagym系统和你的数据没有被泄露 我们的工程师正在调查这个补丁 以及如何把它应用到我们的平台上 我们依然致力于尽快恢复服务, 并且只有在我们相信脆弱性已经完全解决之后.

4. 2026年10月21日 UTC 17:56identified

   Our team is making good progress on the updates for the PHP vulnerabilities. These are the vulnerabilities that led us, like many other companies, to pause our service as a precaution. We’re now in the first phase of testing, making sure the updates can be applied without significantly affecting the service. Virtuagym and your data have not been compromised. We’ll post another update here as soon as testing is complete.

5. 2026年10月21日 UTC 19:53identified

   Testing of the security updates has gone well. Based on where we are now, we expect the full service to be back online between: 22:00 – 22:30 CEST (Amsterdam) 21:00 – 21:30 BST (London) 16:00 – 16:30 EDT (New York) 07:00 – 07:30 AEDT (Sydney/Melbourne), Thursday 22 October 09:00 – 09:30 NZDT (Auckland), Thursday 22 October We’re running a final round of tests now. These will confirm whether we can go ahead and bring the service back.

6. 2026年10月21日 UTC 20:43identified

   During our final round of testing, we found an issue that we want to resolve before bringing the service back online. This means we need a little more time for additional testing, and the service won’t be back within the time window we shared earlier. The issue is not a new security risk. Our system and your data have not been compromised. We just want to be sure everything works as it should once we go live. Our team remains fully focused on patching the vulnerabilities and restoring the service as soon as possible. We’ll keep you informed on our progress here. We’re sorry for the inconvenience and thank you for your patience.

7. 2026年10月21日 UTC 22:03identified

   Additional testing is complete, and we expect the service to be back online within the next 10 to 25 minutes: 00:10 – 00:25 CEST (Amsterdam), Thursday 22 October 23:10 – 23:25 BST (London), Wednesday 21 October 18:10 – 18:25 EDT (New York), Wednesday 21 October 09:10 – 09:25 AEDT (Sydney/Melbourne), Thursday 22 October 11:10 – 11:25 NZDT (Auckland), Thursday 22 October We’ll post another update here as soon as the service is fully available.

8. 2026年10月21日 UTC 22:26identified

   Good news: Virtuagym is back online and most services are available again. During the interruption, our team implemented the necessary patches for the PHP vulnerabilities that have affected websites and online services worldwide. These are the vulnerabilities that led us, like many other companies, to pause our service as a precaution. Our system and your data have not been compromised. You and your members don’t need to take any further action. A few features will stay offline a little longer: Booking through the new schedule widgets, and bookings made by external systems directly in the new schedule. Booking classes through the Virtuagym apps works as normal. The Goals feature is temporarily unavailable. External integrations with the Lead module, such as lead forms on your website, are temporarily unavailable. Our team is actively working on resolving these remaining issues and will restore each service individually as soon as the necessary security updates have been completed. Everything else, including check-in, automated payment runs, the webshop, and class booking and cancellations, works as normal. We’ll continue to monitor service performance closely and post updates here on our status page as each feature comes back. Thank you for your patience and understanding. Best regards, The Virtuagym team

9. 2026年10月22日 UTC 01:07identified

   The Lead module and the new schedule are fully operational again. This includes: Lead forms and other external integrations with the Lead module Booking through the new schedule widgets, and bookings made by external systems in the new schedule We don’t expect any further limitations on these services. The Goals feature is still temporarily unavailable. We’ll post an update here as soon as it’s back. Once more we want to thank you for your patience.

10. 2026年10月22日 UTC 11:31resolved

    The Virtuagym platform is now fully operational. The Goals feature is live again, and this was the last service still affected by the pause. To confirm once more: the Virtuagym system and your data have not been compromised. Like many other companies worldwide, we paused our service purely as a precaution, while we applied the security patches for the PHP vulnerabilities. You and your members don’t need to take any action. We’re closing this incident. We’ll keep monitoring the platform closely and will post here if anything changes. Once again, thank you for your patience and understanding.

自动翻译自官方事件更新。

1. 2026年9月28日 UTC 13:40investigating

   我们的任用计划目前处于停工状态。 我们的小组正在调查这一问题,并努力尽快恢复正常表现.

2. 2026年9月28日 UTC 15:02monitoring

   我们查明了问题,并确定了解决办法。 任用时间表现在应再次如预期的那样运作。 我们将继续密切监测情况.

3. 2026年9月29日 UTC 08:07resolved

   此事已决.

自动翻译自官方事件更新。

1. 2026年9月18日 UTC 21:22investigating

   我们目前正在调查网络和API请求错误的激增.

2. 2026年9月18日 UTC 21:31monitoring

   数据库锁使其他操作无法完成。 锁已经打开了,我们正在监视 所有组件恢复正常运行.

3. 2026年9月18日 UTC 21:35resolved

   这一事件已经得到解决.

自动翻译自官方事件更新。

1. 2026年7月1日 UTC 07:39investigating

   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. 2026年7月1日 UTC 13:34monitoring

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

3. 2026年7月1日 UTC 17:53resolved

   This incident has been resolved.

1. 2026年6月10日 UTC 08:23investigating

   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.

2. 2026年6月10日 UTC 08:25investigating

   We are continuing to investigate this issue.

3. 2026年6月10日 UTC 08:26identified

   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.

4. 2026年6月10日 UTC 11:19identified

   Updated versions of the Food and Coach Android apps are now available, and users who install the latest version can use the apps normally again. A number of Custom Mobile Apps (CMA) have also been updated and are operational. To restore functionality, affected users must update their app to the latest version available in the Google Play Store. The rollout for the remaining Android apps and CMA versions is still in progress.

5. 2026年6月10日 UTC 15:10identified

   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. 2026年6月10日 UTC 16:00resolved

   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.

1. 2026年3月17日 UTC 16:17resolved

   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.

1. 2026年2月5日 UTC 16:03investigating

   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. 2026年2月5日 UTC 16:20monitoring

   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. 2026年2月5日 UTC 17:58monitoring

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

4. 2026年2月5日 UTC 20:48resolved

   This incident has been resolved.

1. 2026年2月5日 UTC 10:50identified

   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. 2026年2月5日 UTC 14:23monitoring

   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. 2026年2月5日 UTC 16:18resolved

   This incident has been resolved.

1. 2025年11月18日 UTC 08:30investigating

   We are currently investigating an issue with our database performance.

2. 2025年11月18日 UTC 09:00monitoring

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

3. 2025年11月18日 UTC 16:00resolved

   This incident has been resolved.

1. 2025年11月5日 UTC 10:19investigating

   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. 2025年11月5日 UTC 11:41resolved

   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.

1. 2025年10月20日 UTC 09:55monitoring

   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. 2025年10月20日 UTC 15:35monitoring

   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. 2025年10月21日 UTC 07:44resolved

   The downstream provider has resolved their incident.

1. 2025年7月1日 UTC 16:48investigating

   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. 2025年7月1日 UTC 17:38monitoring

   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. 2025年7月2日 UTC 08:27resolved

   This incident has been resolved.

1. 2025年3月22日 UTC 22:30identified

   We are currently experiencing an email sending outage due to an issue with a downstream provider. Our team is actively working to restore email sending capabilities as quickly as possible.

2. 2025年3月23日 UTC 18:35monitoring

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

3. 2025年4月1日 UTC 06:53resolved

   This incident has been resolved.

1. 2025年3月18日 UTC 10:04investigating

   Due to increased database load, we are currently experience some slowness of the app and web platform. The performance is improving for the last 30 minutes and will keep updating the status page as we move through the process.

2. 2025年3月18日 UTC 11:05monitoring

   The performance is back to the expected levels. We'll continue monitoring the situation and will implement new measures if necessary while updating this page.

3. 2025年3月19日 UTC 11:07resolved

   The platform database load levels are stabilized for the last 12 hours. We sincerely apologize for any inconvenience this issue may have caused.

1. 2025年3月17日 UTC 10:04investigating

   We're experiencing general Database Load issues due to high traffic that might impact general operations. We're looking into stabilizing these operations with the utmost urgency and will provide an update as soon as possible.

2. 2025年3月17日 UTC 11:22monitoring

   A fix has been implemented and now the connection pooling to the Database is improved. We'll continue monitoring the situation and will implement new measures if necessary while updating this page.

3. 2025年3月18日 UTC 06:23resolved

   This incident has been resolved.

1. 2025年3月14日 UTC 10:30investigating

   We are currently investigating an issue that prevents our replication system from operating correctly. This causes some partial degradation of services for our website.

2. 2025年3月14日 UTC 10:50monitoring

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

3. 2025年3月15日 UTC 18:56resolved

   After extensive monitoring and some configuration changes as a result, the incident is now resolved.

1. 2025年3月13日 UTC 09:58identified

   We have identified an issue with database replication. This may affect some features in our web application such as SEPA downloads. We have identified a solution and it is being implemented.

2. 2025年3月13日 UTC 10:14monitoring

   Replication has been restored. We are now monitoring the replication status for anomalies.

3. 2025年3月13日 UTC 15:40resolved

   The replication is running as expected.

1. 2025年2月5日 UTC 09:18investigating

   Due to a technical issue, credit handouts for a small number of clubs are currently experiencing delays. Our team is actively working to resolve this, and we expect normal operations to resume shortly. We apologize for any inconvenience and appreciate your understanding.

2. 2025年2月11日 UTC 10:25resolved

   This incident has been resolved.

1. 2025年1月10日 UTC 09:37investigating

   We're experiencing general Database Load issues due to high traffic that might impact general operations. We're looking into stabilizing these operations with the utmost urgency and will provide an update as soon as possible.

2. 2025年1月13日 UTC 09:13monitoring

   A fix has been implemented and Database Load levels have stabilised. We'll continue monitoring the situation and will implement new measures if necessary while updating this page.

3. 2025年1月14日 UTC 08:58resolved

   The measures we implemented have successfully stabilized database load levels. We sincerely apologize for any inconvenience this issue may have caused our clients.

1. 2024年12月18日 UTC 16:21investigating

   We are experiencing issues with the appointment schedule, where some events have changed in activity since today. The team is investigating the situation to determine the root cause.

2. 2024年12月18日 UTC 18:21identified

   We have identified the root cause of the issue and will continue working on a fix tomorrow morning. Resolving this is our top priority, and we are committed to addressing it as quickly as possible. Currently, 40 portals are affected, but no data has been lost. Once the fix is implemented, the events will be displayed as originally intended. Thank you for your patience as we work to resolve this matter.

3. 2024年12月19日 UTC 11:51identified

   We have developed a fix that will address the majority of the affected events. It is currently under review and testing. We will provide an update once the fix has been deployed.

4. 2024年12月19日 UTC 16:16identified

   We have successfully deployed a fix that resolves the majority of the impacted events—over 4,000 events across 40 different portals. These events are now displayed as they originally were, based on the correct data. We still see 160 events that are not yet displaying correctly, and we are currently working on determining how to resolve these as well. We will provide an update tomorrow once we have more clarity on how to address the remaining events.

5. 2024年12月20日 UTC 16:33identified

   We have found a solution to restore the remaining 160 events. Our team is currently working on a fix, which will be deployed on Monday. Once completed, all events will be displayed correctly. We will provide a final update on Monday after the remaining events have been resolved.

6. 2024年12月23日 UTC 14:27resolved

   We’ve just rolled out a fix that has also restored the remaining events. All events should now be displayed correctly based on accurate data. Thank you for your patience and understanding. If you experience any further issues, please don't hesitate to contact our support team.