Level365 Outage History

Level365 is up right now

Level365 had 11 outages in the last 2 years totaling 75h 12m of downtime — averaging 0.5 incidents per month.

There were 11 Level365 outages since October 28, 2024 totaling 75h 12m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.level365.com

Minor September 10, 2026

Investigating issues with Level365 Web App Login

Detected by Pingoru
Sep 10, 2026, 01:44 PM UTC
Resolved
Sep 11, 2026, 07:07 PM UTC
Duration
1d 5h
Affected: Web App / Portal
Timeline · 6 updates
  1. investigating Sep 10, 2026, 01:44 PM UTC

    We are currently investigating reports of some users being unable to log in to the Level365 Web App (app.level365.com). Our team is actively working to identify the cause, and further updates will be provided as more information becomes available.

  2. investigating Sep 10, 2026, 02:57 PM UTC

    We are continuing to investigate reports of issues with the Web App related to logging in and components not loading properly once logged in. Further updates will be provided as more information becomes available.

  3. identified Sep 10, 2026, 05:46 PM UTC

    We are continuing to investigate reports of some users being unable to log in to the Level365 Web App (app.level365.com). Our team has identified the cause and is working on a fix. We will provide a further update once it has been implemented.

  4. identified Sep 10, 2026, 08:15 PM UTC

    We are continuing to work on a fix for the login issues affecting some users of the Level365 Web App (app.level365.com). We will provide a further update once the fix has been implemented.

  5. monitoring Sep 11, 2026, 12:32 PM UTC

    A fix has been implemented for intermittent issues affecting some users of the Level365 Web App (app.level365.com). We are continuing to monitor the situation. If you experience any new issues, please contact our support team at support.level365.com.

  6. resolved Sep 11, 2026, 07:07 PM UTC

    We have monitored and confirmed that all services are functioning as expected, with no new reports of issues. This incident is now resolved. If you experience any further problems, please contact our support team at support.level365.com.

Read the full incident report →

Notice August 26, 2026

Investigating Post-Maintenance Service Issues

Detected by Pingoru
Aug 26, 2026, 12:32 PM UTC
Resolved
Aug 26, 2026, 04:15 PM UTC
Duration
3h 43m
Affected: Core UCaaS Services
Timeline · 4 updates
  1. investigating Aug 26, 2026, 12:32 PM UTC

    We are investigating reports of calling issues following the completion of our recent scheduled maintenance. Some users may experience intermittent interruptions when making or receiving calls. Our team is actively working to restore normal calling service as quickly as possible. We will provide another update as more information becomes available.

  2. identified Aug 26, 2026, 02:40 PM UTC

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

  3. resolved Aug 26, 2026, 04:15 PM UTC

    This incident has been resolved. All reported calling issues have been resolved, and no additional issues have been reported. We apologize for any inconvenience this may have caused. If you need further assistance, please contact our Support Team at support.level365.com.

  4. postmortem Sep 09, 2026, 01:24 PM UTC

    On August 12, Level365 performed standard maintenance on core servers as part of ongoing work to increase infrastructure capacity. During the maintenance, device registrations were temporarily moved to an alternate server to maintain connectivity and minimize service interruptions. Following the maintenance, we identified that a small number of devices were having difficulty registering with the platform. Our investigation found that the alternate server had incomplete device-level information due to a data replication issue. This only affected a small subset of devices but prevented those devices from registering properly and receiving calls. Once identified, our team worked directly with affected users to restore their devices. We also identified the underlying replication issue and deployed a corrective fix to address any remaining registration problems and to prevent this from occurring again in the future.

Read the full incident report →

Notice March 6, 2026

Outbound Calling Disruption

Detected by Pingoru
Mar 06, 2026, 06:59 PM UTC
Resolved
Mar 06, 2026, 06:59 PM UTC
Duration
—
Affected: Core UCaaS ServicesVoice Providers
Timeline · 1 update
  1. resolved Mar 06, 2026, 06:59 PM UTC

    This morning, a carrier level issue was identified that affected some outbound calls. Traffic was quickly rerouted and service was restored within approximately 10 minutes. We have continued to monitor and everything has remained stable.

Read the full incident report →

Minor November 21, 2025

Degraded performance with faxing

Detected by Pingoru
Nov 21, 2025, 09:37 AM UTC
Resolved
Nov 21, 2025, 09:54 PM UTC
Duration
12h 16m
Affected: Fax Services
Timeline · 7 updates
  1. investigating Nov 21, 2025, 09:37 AM UTC

    We aqre currently investigating degraded performance on our fax platform

  2. investigating Nov 21, 2025, 01:17 PM UTC

    We are continuing to investigate this issue.

  3. investigating Nov 21, 2025, 01:18 PM UTC

    We are currently investigating reports of issues impacting some fax services. Our team is actively reviewing the situation to identify the cause and restore full functionality as quickly as possible. Thank you for your patience as we work to resolve this.

  4. investigating Nov 21, 2025, 07:07 PM UTC

    We are continuing to troubleshoot the issue impacting some fax services. Our team is actively working toward resolving this as quickly as possible. Thank you for your patience as we work to resolve this.

  5. monitoring Nov 21, 2025, 07:29 PM UTC

    Issue has been identified and a fix has been deployed. We are monitoring services to ensure the issue is resolved.

  6. monitoring Nov 21, 2025, 09:31 PM UTC

    We are continuing to monitor to ensure the issue is resolved. Please note that some faxes may be delayed or require additional attempts as the system processes the queued messages. Thank you for your patience as we work to resolve this.

  7. resolved Nov 21, 2025, 09:54 PM UTC

    This incident has been resolved. All services are confirmed to be working normally, and the backlog of fax messages has been cleared. We will continue to monitor to ensure continued stability. Thank you for your patience as we worked to resolve this issue.

Read the full incident report →

Minor November 18, 2025

Cloudflare Global Outage Advisory

Detected by Pingoru
Nov 18, 2025, 02:22 PM UTC
Resolved
Nov 18, 2025, 06:03 PM UTC
Duration
3h 40m
Affected: Data Providers
Timeline · 2 updates
  1. identified Nov 18, 2025, 02:22 PM UTC

    Cloudflare is currently experiencing a global service outage, which may cause intermittent or unexpected behavior with certain external services. This is a widespread incident affecting a number of services, including (for example) Microsoft 365 and other major platforms that rely on Cloudflare’s network. Level365's core services are not impacted, but some clients may experience side effects related to the broader Cloudflare disruption. If you experience any issues, please contact our support team at support.level365.com. Cloudflare has identified the problem and is implementing a fix. We are actively monitoring the situation and expect service to be restored shortly. You may also follow Cloudflare’s incident updates here: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7

  2. resolved Nov 18, 2025, 06:03 PM UTC

    Cloudflare has reported that the earlier global service outage has been fully resolved. Any intermittent issues affecting external services relying on Cloudflare should now be returning to normal operation. Level365 core services were not impacted by this incident. If you notice anything unexpected or need assistance, please reach out to our support team at support.level365.com. For additional details, you may follow Cloudflare’s incident report here: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7

Read the full incident report →

Minor September 23, 2025

Investigating – Device Registration Issues

Detected by Pingoru
Sep 23, 2025, 11:46 AM UTC
Resolved
Sep 23, 2025, 02:13 PM UTC
Duration
2h 27m
Affected: Core UCaaS ServicesProvisioning
Timeline · 4 updates
  1. investigating Sep 23, 2025, 11:46 AM UTC

    We are currently investigating issues with device registrations affecting some devices following the recent platform maintenance. Our team is actively working to identify the cause, and further updates will be provided as more information becomes available.

  2. monitoring Sep 23, 2025, 12:32 PM UTC

    A fix has been implemented and affected devices have successfully re-registered. We will continue to monitor device performance and stability.

  3. resolved Sep 23, 2025, 02:13 PM UTC

    This incident has been resolved. The impacted devices have remained online since the fix was implemented, and no further issues have been observed. We apologize for any inconvenience this may have caused. If you need any additional assistance, please contact our Support Team at support.level365.com.

  4. postmortem Sep 23, 2025, 02:18 PM UTC

    Following the recent scheduled maintenance, some devices did not immediately re-register due to re-syncing with our connections to upstream ISP providers, resulting in temporary service interruptions for affected users. Once the paths were fully re-synced, connections were reestablished and the devices came back online. Our team has reviewed the incident and is making adjustments to reduce the likelihood of similar registration delays in the future. We apologize for the inconvenience and appreciate your patience.

Read the full incident report →

Major September 21, 2025

Investigating Service Outage

Detected by Pingoru
Sep 21, 2025, 11:42 AM UTC
Resolved
Sep 21, 2025, 03:17 PM UTC
Duration
3h 35m
Affected: Core UCaaS ServicesWeb App / PortalFax ServicesCall RecordingProvisioningAPIVideo CollaborationSecondary Services
Timeline · 4 updates

Read the full incident report →

Notice June 13, 2025

Data Center Disruption

Detected by Pingoru
Jun 13, 2025, 07:44 AM UTC
Resolved
Jun 13, 2025, 02:06 PM UTC
Duration
6h 21m
Affected: Core UCaaS Services
Timeline · 3 updates
  1. identified Jun 13, 2025, 11:44 AM UTC

    One of our data center providers experienced a catastrophic failure during scheduled maintenance. This failure has taken our East Data Center offline. Due to our platform's design, this should not result in any direct client impact. If you experience any issues or have questions, please contact [email protected].

  2. monitoring Jun 13, 2025, 12:31 PM UTC

    Our vendor has resolved their issue and we are continuing to monitor the situation.

  3. resolved Jun 13, 2025, 02:06 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 23, 2025

Text Messaging to AT&T Failing to Complete

Detected by Pingoru
Apr 23, 2025, 12:36 PM UTC
Resolved
Apr 23, 2025, 05:19 PM UTC
Duration
4h 42m
Affected: Secondary Services
Timeline · 3 updates
  1. identified Apr 23, 2025, 12:36 PM UTC

    We have received notification from an underlying carrier used for text messaging that messages to AT&T destinations may fail to complete. We are working with the affected carrier to restore functionality.

  2. monitoring Apr 23, 2025, 01:52 PM UTC

    Our carrier has mitigated the issue and are observing expected SMS and MMS behavior. We will continue to monitor for traffic stability.

  3. resolved Apr 23, 2025, 05:19 PM UTC

    We have been monitoring outgoing messaging traffic and all traffic is flowing as expected. This issue is resolved. If you are still experiencing issues with messaging, please contact Level365 support.

Read the full incident report →

Notice March 3, 2025

Investigating issues with Inbound Caller Name Displaying

Detected by Pingoru
Mar 03, 2025, 03:30 PM UTC
Resolved
Mar 03, 2025, 06:31 PM UTC
Duration
3h
Timeline · 3 updates
  1. investigating Mar 03, 2025, 03:30 PM UTC

    We are investigating issues with Inbound Caller Name Displaying and will provide updates here soon.

  2. monitoring Mar 03, 2025, 05:47 PM UTC

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

  3. resolved Mar 03, 2025, 06:31 PM UTC

    Inbound CallerID Name is now working properly. If you are still experiencing issues with this, please contact support.

Read the full incident report →

Notice October 28, 2024

Investigating issues with our DC datacenter connectivity

Detected by Pingoru
Oct 28, 2024, 07:31 PM UTC
Resolved
Oct 29, 2024, 01:33 AM UTC
Duration
6h 1m
Timeline · 3 updates
  1. investigating Oct 28, 2024, 07:31 PM UTC

    We are investigating issues with with our DC datacenter connectivity. It appears to be a facility issue. We are continuing to investigate and will provide updates here soon.

  2. identified Oct 28, 2024, 07:46 PM UTC

    The issue has been identified as a outage in the DC datacenter area.

  3. resolved Oct 29, 2024, 11:30 AM UTC

    Data Center provider has resolved the core issue. We are awaiting more details at this time, however service is considered restored

Read the full incident report →