Is Virtuagym down?
Last checked 3m agoNo incidents right now.
Virtuagym is operational right now. Last checked 3m ago; the most recent incident resolved 3d ago.
Real-time Virtuagym status, recent outages, and incident history — pulled directly from Virtuagym's official status page at https://status.virtuagym.com every 5 minutes. Pingoru tracks 3 Virtuagym services and has captured 3 incidents in the last 90 days (98.33% uptime). Get email, Slack, Discord, or webhook alerts the moment Virtuagym reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- Mobile Apps
Timeline · 6 updates
- 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.
- investigating · Jun 10, 2026, 08:25 AM UTC
We are continuing to investigate this issue.
- identified · Jun 10, 2026, 08:26 AM UTC
The issue has been identified and a fix is being implemented.
- 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.
- 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.
- 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.
Latest: 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 si…
-
-
Timeline · 1 update
- 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.
Latest: Our activity-instances database experienced connection exhaustion during peak traffic, causing errors on mobile API endpoints (food, activity, plans) and Fitbit sync. Idle connecti…
-
- Android apps – Connectivity Issues ResolvedStarted Jun 10, 2026, 08:23 AM UTC · Resolved Jun 10, 2026, 04:00 PM UTC · 7h 37m
- Started Mar 17, 2026, 04:17 PM UTC · Resolved Mar 16, 2026, 05:30 PM UTC · —