Nebula Outage History

Nebula is up right now

Nebula had 19 outages in the last 2 years totaling 135h 22m of downtime — averaging 0.8 incidents per month.

There were 19 Nebula outages since July 30, 2025 totaling 135h 22m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.nebulacloud.com

Minor June 24, 2026

Disruption to dashboards and calling.

Detected by Pingoru
Jun 24, 2026, 03:28 PM UTC
Resolved
Jun 25, 2026, 07:54 AM UTC
Duration
16h 26m
Affected: Core NetworkDashboard
Timeline · 6 updates
  1. investigating Jun 24, 2026, 03:28 PM UTC

    We're investigating reports of dashboards failing to load and inbound and outbound not working. Next update within 15 minutes.

  2. identified Jun 24, 2026, 03:32 PM UTC

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

  3. identified Jun 24, 2026, 03:44 PM UTC

    A fix has been implemented and we're seeing services returning to normal. Next update 10 minutes.

  4. monitoring Jun 24, 2026, 03:48 PM UTC

    All services are now running as expected and we are monitoring the results.

  5. monitoring Jun 24, 2026, 04:22 PM UTC

    Please note wallboards remain offline while we continue our investigation. These will be restored as soon as possible.

  6. resolved Jun 25, 2026, 07:54 AM UTC

    This incident is being marked as resolved. Service to wallboards have also been restored.

Read the full incident report →

Major May 14, 2026

Issues with outbound calling

Detected by Pingoru
May 14, 2026, 10:05 AM UTC
Resolved
May 14, 2026, 10:28 AM UTC
Duration
23m
Affected: Core Network
Timeline · 3 updates
  1. identified May 14, 2026, 10:05 AM UTC

    We have identified an issue with outbound calls connecting and are working on a fix. We will provide another update within 10 minutes.

  2. monitoring May 14, 2026, 10:10 AM UTC

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

  3. resolved May 14, 2026, 10:28 AM UTC

    This incident has been resolved.

Read the full incident report →

Major March 18, 2026

Issues with desktop app and online portal access.

Detected by Pingoru
Mar 18, 2026, 09:32 AM UTC
Resolved
Mar 18, 2026, 02:28 PM UTC
Duration
4h 56m
Affected: DashboardDesktop Applications
Timeline · 5 updates
  1. investigating Mar 18, 2026, 09:32 AM UTC

    We're investigating reports of issues logging into our desktop apps and online portals. Calls and all other services remain unaffected.

  2. identified Mar 18, 2026, 09:39 AM UTC

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

  3. identified Mar 18, 2026, 09:42 AM UTC

    Dashboards should be restored. Apps will follow shortly as systems are reinitialised.

  4. monitoring Mar 18, 2026, 09:45 AM UTC

    Desktop App access should also be restored. Users should restart their apps if access does not resume automatically.

  5. resolved Mar 18, 2026, 02:28 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 11, 2026

Delay on outbound calls connecting

Detected by Pingoru
Mar 11, 2026, 12:01 PM UTC
Resolved
Mar 11, 2026, 02:41 PM UTC
Duration
2h 40m
Affected: Core NetworkMobile ApplicationsDesktop Applications
Timeline · 6 updates
  1. investigating Mar 11, 2026, 12:01 PM UTC

    We're investigating reports of severe post dial delay on outbound calling. Will update in next 20 minutes.

  2. investigating Mar 11, 2026, 12:06 PM UTC

    Inbound calls and dashboards remain unaffected. We are investigating with urgency.

  3. identified Mar 11, 2026, 12:08 PM UTC

    We have identified the issue and are implementing a fix. Service should be restored shortly.

  4. monitoring Mar 11, 2026, 12:14 PM UTC

    The fix has been implemented and we're seeing service restored to all users. We'll continue to monitor closely for a period before marking this as resolved.

  5. resolved Mar 11, 2026, 02:41 PM UTC

    This incident has been resolved.

  6. postmortem Mar 11, 2026, 02:42 PM UTC

    At 12:01 PM GMT today, some users experienced an interruption when placing outbound calls. Inbound routing, internal extension calling, and online dashboards remained fully operational throughout. All services were restored by 12:14 PM GMT. The issue was caused by an isolated storage component within our Fraud Protection engine. This feature monitors real-time spend, providing an extra layer of security for our customers and partners. The issue was identified, acted upon and resolved within 13 minutes.

Read the full incident report →

Minor February 2, 2026

Brief interruption on apps, dashboards

Detected by Pingoru
Feb 02, 2026, 11:03 AM UTC
Resolved
Feb 02, 2026, 11:52 AM UTC
Duration
48m
Affected: Dashboard
Timeline · 3 updates
  1. identified Feb 02, 2026, 11:03 AM UTC

    We are investigating reports of a brief period of disruption on selected accounts at around 10:48am, which affected apps, handsets, and dashboards. Service was restored in these areas automatically within 5 minutes, and we are currently investigating reports of slow load times on portals and apps. Calls are unaffected at this time.

  2. monitoring Feb 02, 2026, 11:10 AM UTC

    Load times have returned to normal in all areas and we are monitoring.

  3. resolved Feb 02, 2026, 11:52 AM UTC

    We are marking this incident as resolved. Our service encountered an external DDoS attack. Our internal systems automatically mitigated the impact and rerouted the affected traffic with services returning to normal within a 5 minute period. All services remain operational.

Read the full incident report →

Minor January 23, 2026

Issues logging into apps and dashboards

Detected by Pingoru
Jan 23, 2026, 09:45 AM UTC
Resolved
Jan 23, 2026, 10:03 AM UTC
Duration
18m
Affected: Core NetworkDashboardMobile ApplicationsDesktop Applications
Timeline · 3 updates
  1. identified Jan 23, 2026, 09:45 AM UTC

    We're investigating an issue with accessing apps and dashboards and are investigating with priority.

  2. monitoring Jan 23, 2026, 09:50 AM UTC

    Traffic has been restored to normal by our automated measures and we are still investigating.

  3. resolved Jan 23, 2026, 10:03 AM UTC

    This incident has been marked as resolved. There was momentary interruption to some accounts while our auto-scaling measures kicked in due to run rate traffic peaking this morning. Service for all accounts were restored automatically by our redundancy measures, and the configuration of this auto-scaling service has been updated to ensure no service impact in future cases. We apologise for the brief disruption caused.

Read the full incident report →

Minor January 14, 2026

Post-dial delay and audio issues on softphone apps and handsets

Detected by Pingoru
Jan 14, 2026, 03:40 PM UTC
Resolved
Jan 15, 2026, 09:11 AM UTC
Duration
17h 31m
Affected: Core NetworkMobile ApplicationsDesktop Applications
Timeline · 7 updates
  1. identified Jan 14, 2026, 03:40 PM UTC

    We're investigating issues of mobile and desktop apps being unresponsive. We're investigating with priority.

  2. investigating Jan 14, 2026, 03:47 PM UTC

    We've updated the title to reflect reports of handsets also not working. We are investigating with priority and will provide further information as soon as possible.

  3. identified Jan 14, 2026, 04:02 PM UTC

    We've identified the issue and are working on a fix.

  4. identified Jan 14, 2026, 04:07 PM UTC

    The issue is isolated to single zone. We are working on restoring service the affected accounts with urgency.

  5. monitoring Jan 14, 2026, 04:19 PM UTC

    A fix has been implemented and we're seeing service has resumed, with all traffic returning to normal. We are continuing to monitor.

  6. resolved Jan 15, 2026, 09:11 AM UTC

    This incident has been resolved.

  7. postmortem Jan 15, 2026, 05:57 PM UTC

    Following our initial report regarding the incident on January 12, 2026, our Engineering team implemented several emergency infrastructure upgrades. These improvements successfully mitigated the original risk and provided the enhanced visibility required to monitor this segment of our network more closely. On the afternoon of January 14, 2026, the same Memory Cache Layer within a single zone experienced a secondary disruption. This resulted in a 40-minute service outage affecting handsets, mobile applications, and in-call media, for accounts in that zone. Thanks to the telemetry tools installed earlier this week, our team was able to rapidly isolate a specific software bug within this layer. This bug was triggered by recent increases in network traffic. We have since successfully replicated, retested, and deployed a permanent fix across all zones. We will continue to monitor the network closely to ensure continued stability.

Read the full incident report →

Minor January 13, 2026

Degraded performance on inbound and outbound calling for some accounts

Detected by Pingoru
Jan 13, 2026, 12:47 PM UTC
Resolved
Jan 13, 2026, 03:25 PM UTC
Duration
2h 37m
Affected: Core NetworkDashboardMobile ApplicationsDesktop Applications
Timeline · 4 updates
  1. investigating Jan 13, 2026, 12:47 PM UTC

    We are currently investigating this issue.

  2. identified Jan 13, 2026, 12:57 PM UTC

    We've rerouted traffic and are monitoring the results.

  3. monitoring Jan 13, 2026, 01:00 PM UTC

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

  4. resolved Jan 13, 2026, 03:25 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor December 19, 2025

Calls continuing to ring after pickup and audio disruption on some accounts.

Detected by Pingoru
Dec 19, 2025, 11:28 AM UTC
Resolved
Dec 19, 2025, 07:13 PM UTC
Duration
7h 45m
Affected: Core Network
Timeline · 6 updates
  1. investigating Dec 19, 2025, 11:28 AM UTC

    We're investigating some reports of calls continuing to ring after being picked up by an extension and audio disruption, on some end user accounts. We are seeing traffic flowing normally on most. Our team are investigating with priority. Will provide a further update in 20 minutes.

  2. identified Dec 19, 2025, 11:30 AM UTC

    Our team have identified the affected services and are working to resolve. Will provide a further update within 20 minutes.

  3. identified Dec 19, 2025, 11:51 AM UTC

    We are still working on the issue and are seeing improvements in some cases. Will provide a further update in 20 minutes.

  4. monitoring Dec 19, 2025, 11:54 AM UTC

    Expected performance has resumed across the affected zone and we are seeing service return to normal for those affected accounts. We will continue monitoring for an extended period.

  5. resolved Dec 19, 2025, 07:13 PM UTC

    After a successful period of monitoring, we are marking this incident as resolved. We will publish further detail within then next few working days.

  6. postmortem Dec 22, 2025, 04:41 PM UTC

    At 11:08am on 19 December, we identified that some calls received by end users continued to ring after pickup. Upon immediate investigation, we identified a series of transient faults in the data store cache triggered a crash in the connected proxies of one of our three zones. Reinitialising the proxies enabled service to resume at approximately 11:30am \(service restoration\). Further troubleshooting indicated the data store cache was not able to handle a long log messages \(fault cause\). To resolve proxy crashes caused by the data store’s inability to process large log messages, we optimised the configuration by increasing the output buffer and client limits while implementing stricter memory monitoring \(service resolution\).

Read the full incident report →

Notice November 24, 2025

Resolved - Temporary disruption to audio

Detected by Pingoru
Nov 24, 2025, 10:53 AM UTC
Resolved
Nov 24, 2025, 11:04 AM UTC
Duration
10m
Affected: Core Network
Timeline · 2 updates
  1. monitoring Nov 24, 2025, 10:53 AM UTC

    Our team are investigating a brief period of disruption seen across a limited number of customers between 10:45-10:48 this morning, however our redundancy measures automatically re-routed affected traffic and all service was restored to the affected zone. We will continue monitoring to ensure no further degradation of service.

  2. resolved Nov 24, 2025, 11:04 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 18, 2025

Disruption to inbound and outbound calls

Detected by Pingoru
Nov 18, 2025, 10:51 AM UTC
Resolved
Nov 18, 2025, 02:22 PM UTC
Duration
3h 31m
Affected: Core Network
Timeline · 4 updates
  1. identified Nov 18, 2025, 10:50 AM UTC

    We have identified an issue causing degradation on calls and are working to resolve ASAP. We have rerouted affected traffic and seeing those services returning to normal however this may take a short period to complete. Will provide a further update in 20 minutes.

  2. identified Nov 18, 2025, 10:51 AM UTC

    We've seen reports of services returning to normal. We are continuing to monitor the affected zone closely.

  3. monitoring Nov 18, 2025, 11:06 AM UTC

    All services have returned to normal and we're hearing positive reports from our customers of the same. We are continuing to monitor all affected parts of the network for a prolonged period before marking as resolved.

  4. resolved Nov 18, 2025, 02:22 PM UTC

    After a successful period of monitoring we are marking this incident as resolved.

Read the full incident report →

Minor November 3, 2025

Degraded performance on apps and dashboards

Detected by Pingoru
Nov 03, 2025, 09:14 AM UTC
Resolved
Nov 03, 2025, 10:55 AM UTC
Duration
1h 41m
Affected: DashboardMobile ApplicationsDesktop Applications
Timeline · 4 updates
  1. investigating Nov 03, 2025, 09:14 AM UTC

    Our team are investigating disrupted performance on apps and dashboards.

  2. identified Nov 03, 2025, 09:21 AM UTC

    Service should be restored to normal and we are monitoring affected services closely.

  3. monitoring Nov 03, 2025, 09:21 AM UTC

    Service should be restored to normal and we are monitoring affected services closely.

  4. resolved Nov 03, 2025, 10:55 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 31, 2025

Disruption to chat messages on desktop apps

Detected by Pingoru
Oct 31, 2025, 10:59 AM UTC
Resolved
Oct 31, 2025, 12:30 PM UTC
Duration
1h 31m
Affected: Core NetworkDashboardMobile ApplicationsDesktop ApplicationsBilling APICallSwitch - Core NetworkCustomer Services
Timeline · 4 updates
  1. investigating Oct 31, 2025, 10:59 AM UTC

    We are currently investigating reports of presence / chat messages not updating on desktop apps only (mobile apps are unaffected). There is no impacts to calls, all other app features, or dashboards / portal, which remain fully operational. We will provide a further update shortly.

  2. identified Oct 31, 2025, 11:11 AM UTC

    We have identified the root cause impacting chat messages on desktop apps and are currently deploying a fix. Once deployed, we will confirm this and move to a monitoring status.

  3. monitoring Oct 31, 2025, 11:35 AM UTC

    A fix for chat on desktop apps has been successfully tested and deployed, and we will monitor this update in our live environment for a fixed period.

  4. resolved Oct 31, 2025, 12:30 PM UTC

    Following a successful monitoring period, this incident has been resolved.

Read the full incident report →

Notice October 24, 2025

RESOLVED - Temporary disruption to isolated accounts

Detected by Pingoru
Oct 24, 2025, 07:42 AM UTC
Resolved
Oct 24, 2025, 07:42 AM UTC
Duration
—
Affected: Core Network
Timeline · 1 update
  1. resolved Oct 24, 2025, 07:42 AM UTC

    Following essential maintenance works last night, some accounts on a single zone required a clear of routing cache within our database. This caused temporary disruption between 08:15am and 08:35am, however all services have returned to normal operation.

Read the full incident report →

Minor October 20, 2025

AWS OUTAGE - SMS and Call Services Affected

Detected by Pingoru
Oct 20, 2025, 09:57 AM UTC
Resolved
Oct 20, 2025, 04:35 PM UTC
Duration
6h 38m
Affected: Core NetworkDashboard
Timeline · 4 updates
  1. identified Oct 20, 2025, 09:57 AM UTC

    Our team are aware of issues with AWS affecting some services which this morning were limited to SMS delivery, such as 2FA and mobile verification codes. While AWS are reporting recovery in some areas of their network, we have begun to see calls impacted for some customers and are investigating this with urgency. https://www.bbc.co.uk/news/live/c5y8k7k6v1rt We apologise for the delayed acknowledgement of this issue, as our status page provider was also affected by the above outage.

  2. identified Oct 20, 2025, 10:13 AM UTC

    We continue to investigate the issue however our mitigation steps have been successful and we're seeing services restored to across affected zone. Next update in 20 minutes.

  3. monitoring Oct 20, 2025, 10:32 AM UTC

    We've seen all areas of our network return to normal service, in the wake of the recovery of multiple providers following the AWS outage. We'll continue to track all third party services and will close this incident as resolved following a prolonged monitoring period. We greatly appreciate your patience and understanding during this time.

  4. resolved Oct 20, 2025, 04:35 PM UTC

    After a period of successful monitoring we're closing this incident as resolved.

Read the full incident report →

Minor October 17, 2025

Degraded Performance on Dashboards and Apps - Calls Unaffected

Detected by Pingoru
Oct 17, 2025, 11:00 AM UTC
Resolved
Oct 17, 2025, 03:59 PM UTC
Duration
4h 59m
Affected: DashboardMobile ApplicationsDesktop Applications
Timeline · 4 updates
  1. investigating Oct 17, 2025, 11:00 AM UTC

    Our team are investigating degraded performance across dashboards and softphone applications, including chat and presence. Calls and hardware functions are not affected, and all other services are fully operational. We're actively working to address and will update within 20 minutes.

  2. identified Oct 17, 2025, 11:22 AM UTC

    Our team have identified the origin of the issue and are working to restore service ASAP.

  3. monitoring Oct 17, 2025, 12:20 PM UTC

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

  4. resolved Oct 17, 2025, 03:59 PM UTC

    This incident has been resolved.

Read the full incident report →