Is Viirtue down?

Last checked 3m ago
Current status
Viirtue is up

No incidents right now.

Official status page: https://status.viirtue.com · Polled every 5 minutes · 47 components tracked

Viirtue is operational right now. Last checked 3m ago; the most recent incident resolved 6d 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 19 incidents in the last 90 days (100.00% uptime). Get email, Slack, Discord, or webhook alerts the moment Viirtue reports a new incident — free for 5 monitors, no credit card.

Users who monitor Viirtue also follow these Cloud Infrastructure services: Amazon Web Services DigitalOcean Cisco Umbrella Wasabi Vercel Hetzner HashiCorp Egnyte Dyn Genesys Cloud View all 6,000+ providers
Viirtue uptime 100.00% uptime · past 90 days
Mon Wed Fri
JunJulAugSep
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 1h 8m
    Started Sep 02, 2026, 11:48 PM UTC · Resolved Sep 03, 2026, 12:57 AM UTC
    ViiBE
    Timeline · 4 updates
    • 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.

    • investigating · Sep 02, 2026, 11:49 PM UTC

      We are continuing to investigate this issue.

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

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

    Latest: 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, re…

  2. Resolved 14h 52m
    Started Aug 11, 2026, 02:10 PM UTC · Resolved Aug 12, 2026, 05:03 AM UTC
    FL2 Core ServerNJ2 Core Server
    Timeline · 11 updates
    • investigating · Aug 11, 2026, 02:10 PM UTC

      We have identified a incident affecting call queueing on the Apollo Cluster, we are investigating and will provide updates as they are available.

    • identified · Aug 11, 2026, 02:19 PM UTC

      We have found that the issue is primarily with queueing on the Florida Core, we are working to resolve the issue with our infrastructure team

    • identified · Aug 11, 2026, 02:59 PM UTC

      Our Infrastructure team is actively working to resolve the issue and is treating it as a high priority. We will provide our next update within the hour, or sooner if there are any significant developments.

    • monitoring · Aug 11, 2026, 03:37 PM UTC

      After implementing a VPN routing tunnel we've observed improved performance with the server and are monitoring the issue.

    • monitoring · Aug 11, 2026, 04:24 PM UTC

      We are still seeing continued issues with the Florida server, our infrastructure team is monitoring and assessing next steps

    • monitoring · Aug 11, 2026, 04:38 PM UTC

      We are still monitoring the issue but we have identified that the Vegas server is now affected as it processes the backlog of requests coming from FL. We expect improved performance as this backlog is processed.

    • monitoring · Aug 11, 2026, 05:41 PM UTC

      Good afternoon team, Thank you for your patience on this issue. After continued troubleshooting we have identified a long term fix, and we currently are investigating implementation. The issue identified was a network issue locally to the Florida core, which caused backlog queueing. Once the fix is implemented, we will post a further update.

    • monitoring · Aug 11, 2026, 06:37 PM UTC

      We are working on implementing another VPN re-route to alleviate the queueing issue. We will update when this has been completed.

    • monitoring · Aug 11, 2026, 07:39 PM UTC

      We have successfully implemented the alternate route and are seeing the queuing clear. We will continue to monitor the this afternoon but function should be restored.

    • monitoring · Aug 11, 2026, 09:57 PM UTC

      We are actively monitoring the incident but we believe the current effect should be minimal.

    • resolved · Aug 12, 2026, 05:03 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  3. Resolved 1h 1m
    Started Jul 04, 2026, 01:20 AM UTC · Resolved Jul 04, 2026, 02:21 AM UTC
    Florida Data Center
    Timeline · 2 updates
    • 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.

    • resolved · Jul 04, 2026, 02:21 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

Outage history

Past 90 days · 3 incidents View full outage history →