Viirtue Outage History

Viirtue is up right now

Viirtue had 12 outages in the last 2 years totaling 36h 24m of downtime — averaging 0.5 incidents per month.

There were 12 Viirtue outages since October 13, 2025 totaling 36h 24m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.viirtue.com

Notice September 2, 2026

Intermittent outage of ViiBE web portals (*.viibewithus.com)

Detected by Pingoru
Sep 02, 2026, 11:48 PM UTC
Resolved
Sep 03, 2026, 12:57 AM UTC
Duration
1h 8m
Affected: ViiBE
Timeline · 4 updates
  1. investigating Sep 02, 2026, 11:48 PM UTC

    Starting at approximately 22:46 UTC (6:46 PM ET) on September 2, ViiBE portals are intermittently unreachable. Users may see connection failures or a "no healthy upstream" error. The cause is a production Kubernetes node that is repeatedly going unhealthy, which is disrupting the ingress gateway that serves these sites. We have identified the failing node and are working to move traffic off it. Next update in 30 minutes.

  2. investigating Sep 02, 2026, 11:49 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Sep 03, 2026, 12:15 AM UTC

    As of 5:12 PM PT, ViiBE services have restarted and the portals are loading again. A production Kubernetes node in the cloud provider failed and repeatedly dropped offline, which took the ingress gateway and several backend services with it. We added capacity, removed the failing node, and moved all workloads to healthy nodes. We are monitoring closely while services finish recovering.

  4. resolved Sep 03, 2026, 12:57 AM UTC

    A production Kubernetes node in the cloud provider failed and repeatedly dropped offline, which took the ingress gateway and several backend services with it. We added capacity, removed the failing node, and moved all workloads to healthy nodes.

Read the full incident report →

Notice July 4, 2026

Florida Data Center - Network Congestion

Detected by Pingoru
Jul 04, 2026, 01:20 AM UTC
Resolved
Jul 04, 2026, 02:21 AM UTC
Duration
1h 1m
Affected: Florida Data Center
Timeline · 2 updates
  1. monitoring Jul 04, 2026, 01:20 AM UTC

    The network congestion event between the New Jersey and Florida data centers has been resolved. During the event, some geo-routed calls failed, and registration statuses were reported incorrectly across the cluster. Our engineering team will continue to closely monitor network health to ensure service remains stable.

  2. resolved Jul 04, 2026, 02:21 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 16, 2026

Las Vegas - Network Interruption

Detected by Pingoru
Jun 16, 2026, 02:45 AM UTC
Resolved
Jun 16, 2026, 02:03 PM UTC
Duration
11h 17m
Affected: LV Core ServerLV QoS ServerLV Recording Server
Timeline · 2 updates
  1. investigating Jun 16, 2026, 02:45 AM UTC

    We experienced a brief network interruption at our Las Vegas location from 02:07 UTC to 02:12 UTC. Connectivity has been restored and all services are operational. We are monitoring closely and following up with the provider.

  2. resolved Jun 16, 2026, 02:03 PM UTC

    The network interruption was caused by a switch port flap in the providers network. This has been monitored and is confirmed stable.

Read the full incident report →

Minor June 3, 2026

Incident: Error When Opening Faxes

Detected by Pingoru
Jun 03, 2026, 01:58 PM UTC
Resolved
Jun 03, 2026, 03:12 PM UTC
Duration
1h 13m
Affected: Fax
Timeline · 3 updates
  1. 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.

  2. 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.

  3. 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.

Read the full incident report →

Major May 16, 2026

ViiBE inaccessible

Detected by Pingoru
May 16, 2026, 04:14 PM UTC
Resolved
May 16, 2026, 04:40 PM UTC
Duration
26m
Affected: ViiBE
Timeline · 4 updates
  1. investigating May 16, 2026, 04:14 PM UTC

    We are currently investigating this issue.

  2. identified May 16, 2026, 04:37 PM UTC

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

  3. resolved May 16, 2026, 04:40 PM UTC

    This incident has been resolved.

  4. 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.

Read the full incident report →

Minor April 20, 2026

MobileConnect Suffix

Detected by Pingoru
Apr 20, 2026, 03:01 AM UTC
Resolved
Apr 20, 2026, 04:43 AM UTC
Duration
1h 42m
Affected: iOSAndroid
Timeline · 2 updates
  1. 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.

  2. 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.

Read the full incident report →

Minor April 8, 2026

Apollo - Core2-NJ Portal Down

Detected by Pingoru
Apr 08, 2026, 02:51 PM UTC
Resolved
Apr 08, 2026, 02:51 PM UTC
Duration
—
Affected: Manager PortalNJ2 Core Server
Timeline · 1 update
  1. 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.

Read the full incident report →

Notice December 2, 2025

Zeus - Core1-TPA Crash

Detected by Pingoru
Dec 02, 2025, 08:12 PM UTC
Resolved
Dec 02, 2025, 08:12 PM UTC
Duration
—
Affected: FL Core Server
Timeline · 1 update
  1. resolved Dec 02, 2025, 08:12 PM UTC

    At approximately 2:46 PM EST, the core1-TPA server experienced a crash but recovered quickly and is now fully operational. Any calls handled by this server at the time of the crash would have failed.

Read the full incident report →

Minor November 21, 2025

Mobile Connect

Detected by Pingoru
Nov 21, 2025, 03:05 PM UTC
Resolved
Nov 21, 2025, 04:03 PM UTC
Duration
58m
Affected: iOSAndroidWindowsMacOS
Timeline · 4 updates
  1. investigating Nov 21, 2025, 03:05 PM UTC

    We are aware of an issue affecting new registrations and outbound calls for Mobile Connect users. Our engineers are actively working to resolve it.

  2. identified Nov 21, 2025, 03:26 PM UTC

    We discovered an issue in the Mobile Connect middleware update deployed last night. To prevent any disruption to your service, we are rolling back to the last known stable version. Our team is actively monitoring the process and will share updates as soon as they are available.

  3. monitoring Nov 21, 2025, 03:37 PM UTC

    The rollback has been completed and registrations for mobile connect are starting to show as valid. We are monitoring progress. Please open and close the mobile connect application if you experience an issue to force re-registration.

  4. resolved Nov 21, 2025, 04:03 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 10, 2025

Core crash

Detected by Pingoru
Nov 10, 2025, 09:02 PM UTC
Resolved
Nov 11, 2025, 12:38 AM UTC
Duration
3h 35m
Affected: NJ2 Core ServerLV Core Server
Timeline · 3 updates
  1. investigating Nov 10, 2025, 09:02 PM UTC

    At about 3:40 pm est our NJ and LV core crashed for a unknown reason, and we dropped about 1k live calls. The server auto recovered and is operational again. We are currently investigating the cause for this crash and will take necessary corrective action.

  2. resolved Nov 11, 2025, 12:38 AM UTC

    This incident has been resolved.

  3. postmortem Nov 11, 2025, 12:39 AM UTC

    The crash condition observed has been identified as a bug by NetSapiens related to v44. They have tagged it with Jira NMS-3558 in which a rare condition causes the sipbx service to crash. We are actively working with the vendor to implement a patch as soon as one is available.

Read the full incident report →

Minor October 13, 2025

Portal health

Detected by Pingoru
Oct 13, 2025, 03:29 PM UTC
Resolved
Oct 13, 2025, 03:37 PM UTC
Duration
8m
Affected: Manager Portal
Timeline · 2 updates
  1. investigating Oct 13, 2025, 03:29 PM UTC

    We are currently investigating the issue and working to restore service

  2. resolved Oct 13, 2025, 03:37 PM UTC

    Portal service should be restored at this time.

Read the full incident report →