История сбоев Virtuagym

1. 21 октября 2026 г. в 11:49 UTCinvestigating

   Уважаемый клиент, Как вы, возможно, видели в новостях, была обнаружена серьезная уязвимость безопасности, которая затрагивает большую долю веб-сайтов и онлайн-сервисов по всему миру, включая наш. Безопасность ваших данных является нашим главным приоритетом. Как и многие другие компании и организации, в том числе несколько государственных служб Нидерландов, мы временно приостановили наш сервис в качестве меры предосторожности, применяя необходимые патчи безопасности. Мы хотим заверить вас, что программное обеспечение и услуги Virtuagym не были скомпрометированы, а также данные ваших пользователей. Эта пауза носит чисто профилактический характер. Что это значит для вас: В то время как сервис отключен, вы и ваши участники не сможете войти в систему, забронировать классы или использовать приложение. Мы рекомендуем: Дайте знать своим членам о временном перерыве. Планирование ручной альтернативы для регистрации и бронирования, если это необходимо Мы знаем, насколько важна наша платформа для вашего бизнеса, и восстановление ее работы является нашим приоритетом. Мы перезапустим сервис только после того, как эти патчи безопасности будут установлены, и мы уверены, что ваши данные защищены. Вы можете следить за последними обновлениями здесь. Мы также отправим вам электронное письмо, как только услуга будет доступна.

2. 21 октября 2026 г. в 13:06 UTCinvestigating

   Мы продолжаем расследование этого вопроса.

3. 21 октября 2026 г. в 15:32 UTCidentified

   Глобальная команда разработчиков PHP выпустила официальное исправление уязвимости, которое привело нас и многие другие компании к отключению нашей системы в качестве меры предосторожности. PHP - это широко используемый язык программирования, на котором в основном построена наша платформа. Система Virtuagym и ваши данные не были взломаны. Наши инженеры сейчас изучают патч и как его применить к нашей платформе. Мы по-прежнему стремимся вернуть сервис как можно скорее, и мы сделаем это только после того, как будем уверены, что уязвимость была полностью устранена.

4. 21 октября 2026 г. в 17:56 UTCidentified

   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. 21 октября 2026 г. в 19:53 UTCidentified

   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. 21 октября 2026 г. в 20:43 UTCidentified

   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. 21 октября 2026 г. в 22:03 UTCidentified

   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. 21 октября 2026 г. в 22:26 UTCidentified

   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. 22 октября 2026 г. в 01:07 UTCidentified

   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. 22 октября 2026 г. в 11:31 UTCresolved

    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. 28 сентября 2026 г. в 13:40 UTCinvestigating

   В настоящее время мы испытываем перебои в графике назначения. Наша команда изучает этот вопрос и работает над тем, чтобы как можно скорее восстановить нормальную производительность.

2. 28 сентября 2026 г. в 15:02 UTCmonitoring

   Мы определили проблему и внедрили исправление. Расписание назначений теперь должно работать так, как ожидалось. Мы продолжим внимательно следить за ситуацией, чтобы убедиться, что проблема не повторится.

3. 29 сентября 2026 г. в 08:07 UTCresolved

   Инцидент был урегулирован.

Автоматический перевод официального обновления инцидента.

1. 18 сентября 2026 г. в 21:22 UTCinvestigating

   В настоящее время мы расследуем всплеск ошибок веб-запросов и запросов api.

2. 18 сентября 2026 г. в 21:31 UTCmonitoring

   Блокировка базы данных помешала завершению любой другой операции. Замок был освобожден, и мы сейчас следим. Все компоненты вернулись к нормальной работе.

3. 18 сентября 2026 г. в 21:35 UTCresolved

   Этот инцидент был урегулирован.

Автоматический перевод официального обновления инцидента.

1. 1 июля 2026 г. в 07:39 UTCinvestigating

   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. 1 июля 2026 г. в 13:34 UTCmonitoring

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

3. 1 июля 2026 г. в 17:53 UTCresolved

   This incident has been resolved.

1. 10 июня 2026 г. в 08:23 UTCinvestigating

   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. 10 июня 2026 г. в 08:25 UTCinvestigating

   We are continuing to investigate this issue.

3. 10 июня 2026 г. в 08:26 UTCidentified

   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. 10 июня 2026 г. в 11:19 UTCidentified

   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. 10 июня 2026 г. в 15:10 UTCidentified

   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. 10 июня 2026 г. в 16:00 UTCresolved

   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. 17 марта 2026 г. в 16:17 UTCresolved

   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. 5 февраля 2026 г. в 16:03 UTCinvestigating

   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. 5 февраля 2026 г. в 16:20 UTCmonitoring

   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. 5 февраля 2026 г. в 17:58 UTCmonitoring

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

4. 5 февраля 2026 г. в 20:48 UTCresolved

   This incident has been resolved.

1. 5 февраля 2026 г. в 10:50 UTCidentified

   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. 5 февраля 2026 г. в 14:23 UTCmonitoring

   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. 5 февраля 2026 г. в 16:18 UTCresolved

   This incident has been resolved.

1. 18 ноября 2025 г. в 08:30 UTCinvestigating

   We are currently investigating an issue with our database performance.

2. 18 ноября 2025 г. в 09:00 UTCmonitoring

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

3. 18 ноября 2025 г. в 16:00 UTCresolved

   This incident has been resolved.

1. 5 ноября 2025 г. в 10:19 UTCinvestigating

   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. 5 ноября 2025 г. в 11:41 UTCresolved

   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. 20 октября 2025 г. в 09:55 UTCmonitoring

   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. 20 октября 2025 г. в 15:35 UTCmonitoring

   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. 21 октября 2025 г. в 07:44 UTCresolved

   The downstream provider has resolved their incident.

1. 1 июля 2025 г. в 16:48 UTCinvestigating

   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. 1 июля 2025 г. в 17:38 UTCmonitoring

   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. 2 июля 2025 г. в 08:27 UTCresolved

   This incident has been resolved.

1. 22 марта 2025 г. в 22:30 UTCidentified

   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. 23 марта 2025 г. в 18:35 UTCmonitoring

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

3. 1 апреля 2025 г. в 06:53 UTCresolved

   This incident has been resolved.

1. 18 марта 2025 г. в 10:04 UTCinvestigating

   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. 18 марта 2025 г. в 11:05 UTCmonitoring

   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. 19 марта 2025 г. в 11:07 UTCresolved

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

1. 17 марта 2025 г. в 10:04 UTCinvestigating

   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. 17 марта 2025 г. в 11:22 UTCmonitoring

   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. 18 марта 2025 г. в 06:23 UTCresolved

   This incident has been resolved.

1. 14 марта 2025 г. в 10:30 UTCinvestigating

   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. 14 марта 2025 г. в 10:50 UTCmonitoring

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

3. 15 марта 2025 г. в 18:56 UTCresolved

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

1. 13 марта 2025 г. в 09:58 UTCidentified

   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. 13 марта 2025 г. в 10:14 UTCmonitoring

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

3. 13 марта 2025 г. в 15:40 UTCresolved

   The replication is running as expected.

1. 5 февраля 2025 г. в 09:18 UTCinvestigating

   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. 11 февраля 2025 г. в 10:25 UTCresolved

   This incident has been resolved.

1. 10 января 2025 г. в 09:37 UTCinvestigating

   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. 13 января 2025 г. в 09:13 UTCmonitoring

   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. 14 января 2025 г. в 08:58 UTCresolved

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

1. 18 декабря 2024 г. в 16:21 UTCinvestigating

   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. 18 декабря 2024 г. в 18:21 UTCidentified

   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. 19 декабря 2024 г. в 11:51 UTCidentified

   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. 19 декабря 2024 г. в 16:16 UTCidentified

   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. 20 декабря 2024 г. в 16:33 UTCidentified

   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. 23 декабря 2024 г. в 14:27 UTCresolved

   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.