White Label Communications Outage History

White Label Communications is up right now

White Label Communications had 13 outages in the last 2 years totaling 78h 47m of downtime — averaging 0.5 incidents per month.

There were 13 White Label Communications outages since August 12, 2024 totaling 78h 47m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://www.whitelabelstatus.com

Minor May 11, 2026

Inbound/Outbound call completion incident.

Detected by Pingoru
May 11, 2026, 03:31 PM UTC
Resolved
May 12, 2026, 04:05 AM UTC
Duration
12h 33m
Affected: Inbound CallingOutbound Calling
Timeline · 5 updates
  1. investigating May 11, 2026, 03:31 PM UTC

    We are currently investigating an issue with inbound and outbound call completion

  2. identified May 11, 2026, 04:41 PM UTC

    The issue has been identified. Services at this time should be stable. We are working on a resolution at this time.

  3. identified May 11, 2026, 08:36 PM UTC

    The Engineering team continues to work on the root cause. Service should still be stable at this time.

  4. monitoring May 12, 2026, 03:05 AM UTC

    A fix has been implimented. All services are operational. We will continue to monitor.

  5. resolved May 12, 2026, 04:05 AM UTC

    This incident has been resolved.

Read the full incident report →

Major March 12, 2026

Call completion failures and degradation

Detected by Pingoru
Mar 12, 2026, 08:54 PM UTC
Resolved
Mar 13, 2026, 10:44 PM UTC
Duration
1d 1h
Affected: Inbound CallingOutbound Calling
Timeline · 5 updates
  1. investigating Mar 12, 2026, 08:54 PM UTC

    We are currently investigating issues in one of our data centers. The engineering team is actively investigating. We will provide any updates as they become available.

  2. identified Mar 12, 2026, 09:53 PM UTC

    We have isolated the incident, and we are working towards a fix.

  3. identified Mar 13, 2026, 12:12 AM UTC

    We are continuing to investigate the underlying issue. At this time, services appear to be stable.

  4. monitoring Mar 13, 2026, 11:59 AM UTC

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

  5. resolved Mar 13, 2026, 10:44 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor December 22, 2025

Atlas Portal Degradation

Detected by Pingoru
Dec 22, 2025, 03:03 PM UTC
Resolved
Dec 22, 2025, 04:26 PM UTC
Duration
1h 23m
Affected: Web Portal
Timeline · 4 updates
  1. investigating Dec 22, 2025, 03:03 PM UTC

    We are currently investigating an issue with accessing the Atlas portal.

  2. identified Dec 22, 2025, 03:22 PM UTC

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

  3. monitoring Dec 22, 2025, 03:36 PM UTC

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

  4. resolved Dec 22, 2025, 04:26 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 20, 2025

AWS portal impairment.

Detected by Pingoru
Oct 20, 2025, 03:04 PM UTC
Resolved
Oct 21, 2025, 12:20 AM UTC
Duration
9h 16m
Affected: Web Portal
Timeline · 3 updates
  1. identified Oct 20, 2025, 03:04 PM UTC

    We are currently aware of an incident in AWS causing degraded portal performance. AWS is working to correct their issues.

  2. monitoring Oct 20, 2025, 10:04 PM UTC

    AWS has implemented a fix and they are observing normal network traffic at this point. We will continue to monitor.

  3. resolved Oct 21, 2025, 12:20 AM UTC

    AWS has noted this incident as resolved.

Read the full incident report →

Minor August 18, 2025

Outbound call failures

Detected by Pingoru
Aug 18, 2025, 02:51 PM UTC
Resolved
Aug 18, 2025, 09:01 PM UTC
Duration
6h 10m
Affected: Inbound CallingOutbound Calling
Timeline · 5 updates
  1. investigating Aug 18, 2025, 02:51 PM UTC

    We are currently investigating an incident with outbound call failures.

  2. investigating Aug 18, 2025, 03:23 PM UTC

    We are seeing some intermittent inbound issues as well with routing, The team is continuing to investigate.

  3. identified Aug 18, 2025, 03:59 PM UTC

    The issue has been identified. Call processing is currently stable.

  4. monitoring Aug 18, 2025, 06:27 PM UTC

    A fix has been implimented and we are monitoring for continued stability.

  5. resolved Aug 18, 2025, 09:01 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 14, 2025

Account creation failures

Detected by Pingoru
Jul 14, 2025, 04:16 PM UTC
Resolved
Jul 14, 2025, 07:21 PM UTC
Duration
3h 5m
Affected: Web Portal
Timeline · 3 updates
  1. identified Jul 14, 2025, 04:16 PM UTC

    The Support and Engineering teams have identified an issue with new account generation and the conversion of quotes to create new accounts. We are working on a solution at this time.

  2. monitoring Jul 14, 2025, 05:40 PM UTC

    A fix has been implimented and we are currently monitoring for any further errors.

  3. resolved Jul 14, 2025, 07:21 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 11, 2025

Pennsylvania PSAP intermittent outage Notification

Detected by Pingoru
Jul 11, 2025, 08:23 PM UTC
Resolved
Jul 11, 2025, 09:02 PM UTC
Duration
39m
Timeline · 2 updates
  1. monitoring Jul 11, 2025, 08:23 PM UTC

    The Pennsylvania Emergency Management Agency has sent out a statewide notice of an intermittent outage with the PA 911 system. Individuals experiencing issues contacting 911 are asked to contact their local 911 center via their non-emergency numbers. Please check your local county's social media and website for more information.

  2. resolved Jul 11, 2025, 09:02 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 4, 2025

Grand Rapids based registration and calling issues

Detected by Pingoru
Jun 04, 2025, 03:06 PM UTC
Resolved
Jun 04, 2025, 05:05 PM UTC
Duration
1h 59m
Affected: RegistrationCentralInbound CallingOutbound Calling
Timeline · 4 updates
  1. investigating Jun 04, 2025, 03:06 PM UTC

    We are currently investigating an issue with calling and registration related to accounts homed in the Grand Rapids Data-center.

  2. identified Jun 04, 2025, 03:22 PM UTC

    We have identified an issue with one of our Upstream providers, Lumen. We will be steering traffic around this upstream link while we work with the provider and resolve the issue.

  3. monitoring Jun 04, 2025, 03:41 PM UTC

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

  4. resolved Jun 04, 2025, 05:05 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 9, 2025

Atlas reseller portal access

Detected by Pingoru
May 09, 2025, 12:43 PM UTC
Resolved
May 09, 2025, 03:24 PM UTC
Duration
2h 41m
Affected: Web Portal
Timeline · 5 updates
  1. investigating May 09, 2025, 12:43 PM UTC

    We are currently investigating an issue with the reseller-level logins to the Atlas Portal. All Voice services are active at this time.

  2. investigating May 09, 2025, 01:13 PM UTC

    We are continuing to investigate the issue. At this time please use the unbranded domains to access your portal. Support can provide you with the link if you do not know your unbranded domain.

  3. identified May 09, 2025, 02:18 PM UTC

    The issue has been identified and we are seeing a positive response for branded URL access.

  4. monitoring May 09, 2025, 02:40 PM UTC

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

  5. resolved May 09, 2025, 03:24 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 3, 2025

CNAM Deliver 520 Error

Detected by Pingoru
Mar 03, 2025, 03:26 PM UTC
Resolved
Mar 03, 2025, 06:33 PM UTC
Duration
3h 6m
Affected: CNAM Delivery
Timeline · 4 updates
  1. investigating Mar 03, 2025, 03:26 PM UTC

    We are currently working with our CNAM vendor to investigate an issue with SNAM delivery.

  2. identified Mar 03, 2025, 04:29 PM UTC

    The issue has been identified and we are seeing CNAM delivery return to normal.

  3. monitoring Mar 03, 2025, 05:20 PM UTC

    The carrier has a fix in place, and we are monitoring for stability at this time.

  4. resolved Mar 03, 2025, 06:33 PM UTC

    The carrier is noting that this issue has been resolved at this time.

Read the full incident report →

Minor February 21, 2025

Boomea Application Connectivity

Detected by Pingoru
Feb 21, 2025, 08:10 PM UTC
Resolved
Feb 21, 2025, 08:59 PM UTC
Duration
48m
Affected: UC Client
Timeline · 4 updates
  1. investigating Feb 21, 2025, 08:10 PM UTC

    We are currently investigating an issue involving the Boome UC client. All voice services are active at this time. Only the boomea application is Impacted.

  2. identified Feb 21, 2025, 08:17 PM UTC

    The Development team and Engineering teams have identified the issue are are monitoring services being restored.

  3. monitoring Feb 21, 2025, 08:26 PM UTC

    A fix has been implemented and we are currently monitoring for stability.

  4. resolved Feb 21, 2025, 08:59 PM UTC

    This incident is being marked Resolved at this time.

Read the full incident report →

Notice October 5, 2024

Issue using voicemail access, *97

Detected by Pingoru
Oct 05, 2024, 02:50 PM UTC
Resolved
Oct 05, 2024, 09:44 PM UTC
Duration
6h 54m
Timeline · 3 updates
  1. investigating Oct 05, 2024, 02:50 PM UTC

    We are currently investigating reports of users having issues using the *97 code to access voicemail.

  2. monitoring Oct 05, 2024, 03:45 PM UTC

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

  3. resolved Oct 05, 2024, 09:44 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 12, 2024

CNAM Delivery Errors

Detected by Pingoru
Aug 12, 2024, 06:20 PM UTC
Resolved
Aug 12, 2024, 10:39 PM UTC
Duration
4h 18m
Affected: CNAM Delivery
Timeline · 3 updates
  1. investigating Aug 12, 2024, 06:20 PM UTC

    We are currently investigating an issue with CNAM delivery on inbound calls. The carrier is aware and looking into this issue currently. We will provide updates as they become available.

  2. identified Aug 12, 2024, 10:38 PM UTC

    The CNAM carrier was able to identify the issue and put a fix in place.

  3. resolved Aug 12, 2024, 10:39 PM UTC

    At this time we are seeing good CNAM dips after the implemented fix. We are making the incident as resolved.

Read the full incident report →