Is Viirtue down?
Last checked 6m agoNo incidents right now.
Viirtue is operational right now. Last checked 6m ago; the most recent incident resolved 10d ago.
Real-time Viirtue status, recent outages, and incident history — pulled directly from Viirtue's official status page at https://status.viirtue.com every 5 minutes. Pingoru tracks 47 Viirtue services and has captured 13 incidents in the last 90 days (99.85% uptime). Get email, Slack, Discord, or webhook alerts the moment Viirtue reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- Fax
Timeline · 3 updates
- investigating · Jun 03, 2026, 01:58 PM UTC
Description: We are currently investigating an issue causing UUID errors when attempting to open faxes within the web portal. Updates to follow. Impact: Customers may experience issues with opening faxes. No reports of sending issues at this time. Next Update: We will provide our next update by 11:00AM EST or sooner if new information becomes available.
- monitoring · Jun 03, 2026, 02:29 PM UTC
We have worked with our fax vendor, identified a root cause, and deployed a solution to the faxes not appearing in the portal. Our team is monitoring the results, and we will continue to track this event.
- resolved · Jun 03, 2026, 03:12 PM UTC
This incident has been resolved. Please reach out to the Viirtue support team if you have any further questions or concerns.
Latest: This incident has been resolved. Please reach out to the Viirtue support team if you have any further questions or concerns.
-
- ViiBE
Timeline · 4 updates
- investigating · May 16, 2026, 04:14 PM UTC
We are currently investigating this issue.
- identified · May 16, 2026, 04:37 PM UTC
The issue has been identified and a fix is being implemented.
- resolved · May 16, 2026, 04:40 PM UTC
This incident has been resolved.
- postmortem · May 16, 2026, 04:43 PM UTC
During a routine Kubernetes cluster upgrade activity, a critical workload dependency impacting RabbitMQ availability failed to initialize successfully. Investigation determined the issue was caused by the removal of an upstream container image from Docker Hub, preventing the cluster from pulling the required image during workload startup. The issue was identified quickly, and service was restored by updating the workload configuration to reference an alternate trusted image source containing the same image artifact. Total impact duration was minimal, and no data loss occurred. This incident highlighted a broader software supply chain dependency risk associated with externally hosted container images. As a result, we are reviewing additional safeguards around image provenance, availability, and internal artifact mirroring to further reduce exposure to upstream registry changes.
Latest: During a routine Kubernetes cluster upgrade activity, a critical workload dependency impacting RabbitMQ availability failed to initialize successfully. Investigation determined the…
-
- iOSAndroid
Timeline · 2 updates
- identified · Apr 20, 2026, 03:01 AM UTC
We are aware of an issue causing MobileConnect devices to register with an incorrect suffix, and we have escalated it with our partners. In the meantime, for any call queue users utilizing MobileConnect, the “m” device must be added to the queue to ensure they can receive queue calls until the issue is resolved.
- resolved · Apr 20, 2026, 04:43 AM UTC
The incident has been resolved. If you experience any issues receiving calls on the MobileConnect app, please log out of the app and then log back in.
Latest: The incident has been resolved. If you experience any issues receiving calls on the MobileConnect app, please log out of the app and then log back in.
-
- Manager PortalNJ2 Core Server
Timeline · 1 update
- resolved · Apr 08, 2026, 02:51 PM UTC
The Core2-NJ portal became unavailable due to an invalid Apache certificate. The certificate was promptly removed, and service was restored within minutes.
Latest: The Core2-NJ portal became unavailable due to an invalid Apache certificate. The certificate was promptly removed, and service was restored within minutes.
-
- Incident: Error When Opening Faxes ResolvedStarted Jun 03, 2026, 01:58 PM UTC · Resolved Jun 03, 2026, 03:12 PM UTC · 1h 13m
- ViiBE inaccessible ResolvedStarted May 16, 2026, 04:14 PM UTC · Resolved May 16, 2026, 04:40 PM UTC · 26m
- MobileConnect Suffix ResolvedStarted Apr 20, 2026, 03:01 AM UTC · Resolved Apr 20, 2026, 04:43 AM UTC · 1h 42m
- Apollo - Core2-NJ Portal Down ResolvedStarted Apr 08, 2026, 02:51 PM UTC · Resolved Apr 08, 2026, 02:51 PM UTC · —