White Label Communications Outage History

White Label Communications is up right now

White Label Communications had 19 outages in the last 2 years totaling 163h 0m of downtime — averaging 0.8 incidents per month.

There were 19 White Label Communications outages since December 23, 2024 totaling 163h 0m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://www.whitelabelstatus.com

Notice October 17, 2026

Boomea Call Center Issues

Detected by Pingoru
Oct 17, 2026, 01:53 PM UTC
Resolved
Oct 19, 2026, 06:02 PM UTC
Duration
2d 4h
Affected: Outbound CallingCall Center
Timeline · 8 updates
  1. investigating Oct 17, 2026, 01:53 PM UTC

    Hello Partners, We are aware of an issue with the Boomea Call Center where an agent is not able to login/out of the call center after last night's maintenance to upgrade the platform to 5.4. We are actively working on this with our vendor to resolve the issue. There is a temporary workaround to use a ring group strategy rather than queues until this is fixed.

  2. identified Oct 17, 2026, 02:26 PM UTC

    Hello Partners, We are continuing to work with our vendor to resolve the issue. We have identified the issue is only occurring with the Boomea desktop client. An agent logging in to the queue using a desk phone or softphone client will work. Issues being reported and currently investigating: Agent Login/out Click 2 Call Quick Call My Phone Page Further updates will be provided shortly. Regards, WLC Management

  3. identified Oct 17, 2026, 04:00 PM UTC

    Hello Partners, Most of the issues with Boomea have been resolved. We have had a couple of reports where call transfers are failing. We are currently reviewing and continuing to work with engineering and the vendor on this matter. Regards, WLC Management

  4. identified Oct 17, 2026, 07:48 PM UTC

    Hello Partners, At this time, the engineering team is still working to resolve the issue. Regards, WLC Management

  5. identified Oct 18, 2026, 01:08 AM UTC

    Hello Partners, Engineering is continuing to investigate the issue. They believe this may be affecting a small set of customers using Allworx PBX. They are still in the process of coming up with a resolution. If you have any customers experiencing any issues outside of this, please contact support so we can investigate. Further updates will be provided tomorrow morning starting at 9AM. Regards, WLC Management

  6. identified Oct 18, 2026, 03:25 PM UTC

    Hello Partners, Engineering has deployed a patch to our staging environment, and we are currently testing to verify this fixes the issue with the Allworx PBX and does not affect anything else after we deploy this to production. We expect all of our testing to be completed by late afternoon. We'll have another update then to advise if this patch can be deployed to production. Regards, WLC Management

  7. monitoring Oct 18, 2026, 09:25 PM UTC

    Hello Partners, Engineering has completed rolling out a patch, which fixed an issue with the Allworx transfer interop problem. We will monitor over the next 24 hours to make sure no further issues come up. If you are experiencing any issues, please let support know. Regards, WLC Management

  8. resolved Oct 19, 2026, 06:02 PM UTC

    The maintenance is complete and issues that arose over the weekend have been addressed. If you have an agent not behaving correctly, please have them log out first. If you have any issues, please reach out to the support team. Regards, WLC Management

Read the full incident report →

Minor September 16, 2026

Boomea Call center and Queue routing

Detected by Pingoru
Sep 16, 2026, 01:34 PM UTC
Resolved
Sep 17, 2026, 02:33 AM UTC
Duration
12h 59m
Affected: Call Center
Timeline · 7 updates
  1. investigating Sep 16, 2026, 01:34 PM UTC

    We are currently investigating an issue impacting the boomea call center console and Queue calls.

  2. investigating Sep 16, 2026, 03:01 PM UTC

    We are continuing to investigate the issue.

  3. investigating Sep 16, 2026, 04:03 PM UTC

    We are continuing to investigate the issues. If you are experiencing issues, please have all queue agents log out using the Star codes to start a fresh session. *62 log out *60 Log in *61 Set ready If you are having continued issues, please report your impacted customers to [email protected]

  4. identified Sep 16, 2026, 05:30 PM UTC

    The issue has been identified and a fix is being worked on. If you have agents unable to log in at this time please provide the account and impacted users to the support team.

  5. monitoring Sep 16, 2026, 06:33 PM UTC

    The support team has an available correction for any partners still experiencing issues with the call center. Please contact [email protected] for assistance.

  6. monitoring Sep 16, 2026, 08:19 PM UTC

    We are seeing service restored. If you are still having issues with any agents, please contact support. We will be performing queue restarts this evening. If you have any questions, please contact us.

  7. resolved Sep 17, 2026, 02:33 AM UTC

    This incident is being noted as resolved. Please contact support if there are any continued issues.

Read the full incident report →

Notice August 21, 2026

UI/UX update reloads

Detected by Pingoru
Aug 21, 2026, 12:13 PM UTC
Resolved
Aug 21, 2026, 12:13 PM UTC
Duration
—
Affected: Web Portal
Timeline · 1 update
  1. resolved Aug 21, 2026, 12:13 PM UTC

    With the new ui release, some users are experiencing a one-time sign-in issue where the login page spins but does not load. This is a local cache issue. Use CTRL+F5 to reload the page and clear cache. Login should then work as expected. If CTRL+F5 does not work, open an incognito window of the browser and login there. If you continue to have issues, please reach out to support.

Read the full incident report →

Minor August 18, 2026

HTTPS Fax server interruption.

Detected by Pingoru
Aug 18, 2026, 06:38 PM UTC
Resolved
Aug 18, 2026, 07:21 PM UTC
Duration
42m
Affected: Fax
Timeline · 4 updates
  1. investigating Aug 18, 2026, 06:38 PM UTC

    We are currently investigating an issue with the faxback HTTPS fax server.

  2. identified Aug 18, 2026, 06:42 PM UTC

    The issue has been identified, and the service has been restarted. Observing normal behavior has returned.

  3. monitoring Aug 18, 2026, 06:44 PM UTC

    The fix has been implimented and service has been confirmed restored. Moving to monitoring.

  4. resolved Aug 18, 2026, 07:21 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 22, 2026

Call completion failures and degradation

Detected by Pingoru
Jun 22, 2026, 07:21 PM UTC
Resolved
Jun 23, 2026, 03:23 AM UTC
Duration
8h 2m
Affected: RegistrationInbound CallingOutbound Calling
Timeline · 3 updates
  1. identified Jun 22, 2026, 07:21 PM UTC

    We have identified a similar issue that necessitates a failover of the LAS zone. Failover has been initiated. If you're having ongoing issues, please reach out to the support team.

  2. monitoring Jun 22, 2026, 08:45 PM UTC

    We continue to monitor the health of the system in its failed over state. LAS zone will be restored to full service this evening.

  3. resolved Jun 23, 2026, 03:23 AM UTC

    The LAS zone has been returned to normal operation. Calls are completing normally at this time in all 3 zones.

Read the full incident report →

Minor June 18, 2026

Intermittent inbound queue call impartment

Detected by Pingoru
Jun 18, 2026, 05:25 PM UTC
Resolved
Jun 18, 2026, 08:42 PM UTC
Duration
3h 17m
Affected: Call Center
Timeline · 4 updates
  1. investigating Jun 18, 2026, 05:25 PM UTC

    We are currently investigating an intermittent issue with inbound queue calls not being offered to available agents. Engineering is actively investigating the issue. If you are experiencing any issues, please open a ticket with [email protected]

  2. identified Jun 18, 2026, 06:50 PM UTC

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

  3. monitoring Jun 18, 2026, 07:18 PM UTC

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

  4. resolved Jun 18, 2026, 08:42 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 17, 2026

Intermittent inbound queue call impairment

Detected by Pingoru
Jun 17, 2026, 07:48 PM UTC
Resolved
Jun 18, 2026, 02:20 AM UTC
Duration
6h 32m
Affected: Call Center
Timeline · 4 updates
  1. investigating Jun 17, 2026, 07:48 PM UTC

    We are currently investigating an intermittent issue with inbound queue calls not being offered to available agents. Engineering is actively investigating the issue. If you are experiencing any issues, please open a ticket with [email protected]

  2. identified Jun 17, 2026, 08:39 PM UTC

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

  3. monitoring Jun 17, 2026, 09:37 PM UTC

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

  4. resolved Jun 18, 2026, 02:20 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 16, 2026

Inbound Queue call offers.

Detected by Pingoru
Jun 16, 2026, 05:20 PM UTC
Resolved
Jun 17, 2026, 12:09 PM UTC
Duration
18h 49m
Affected: Call Center
Timeline · 4 updates
  1. investigating Jun 16, 2026, 05:20 PM UTC

    We are currently investigating an intermittent issue with inbound queue calls not being offered to available agents. Engineering is actively investigating the issue. If you are experiencing any issues, please open a ticket with [email protected]

  2. identified Jun 16, 2026, 05:51 PM UTC

    The issue has been identified, and we are working to implement a fix. If you are having ongoing issues, please let the support team know.

  3. monitoring Jun 16, 2026, 06:04 PM UTC

    A fix has been implemented. Please contact support with any continued issues. We will continue to monitor.

  4. resolved Jun 17, 2026, 12:09 PM UTC

    This incident has been resolved.

Read the full incident report →

Major June 8, 2026

Atlas Web Portal Access.

Detected by Pingoru
Jun 08, 2026, 06:40 PM UTC
Resolved
Jun 09, 2026, 01:24 PM UTC
Duration
18h 44m
Affected: Web Portal
Timeline · 5 updates
  1. investigating Jun 08, 2026, 06:40 PM UTC

    We are currently investigating an issue with accessing the Atlas Wed Portal.

  2. investigating Jun 08, 2026, 06:54 PM UTC

    The Atlas web portal is operational. We are continuing to review the events.

  3. identified Jun 08, 2026, 07:47 PM UTC

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

  4. monitoring Jun 08, 2026, 08:39 PM UTC

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

  5. resolved Jun 09, 2026, 01:24 PM UTC

    This incident has been resolved.

Read the full incident report →

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 →

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 →