Nebula incident

Issues with inbound and outbound calling

Minor Resolved View vendor source →

Nebula experienced a minor incident on September 11, 2026 affecting Core Network and Desktop Applications, lasting 1h 56m. The incident has been resolved; the full update timeline is below.

Started
Sep 11, 2026, 02:15 PM UTC
Resolved
Sep 11, 2026, 04:11 PM UTC
Duration
1h 56m
Detected by Pingoru
Sep 11, 2026, 02:15 PM UTC

Affected components

Core NetworkDesktop Applications

Update timeline

  1. investigating Sep 11, 2026, 02:15 PM UTC

    We are currently investigating this issue.

  2. investigating Sep 11, 2026, 02:15 PM UTC

    We are continuing to investigate this issue.

  3. identified Sep 11, 2026, 02:18 PM UTC

    The issue has been identified and we are working on a fix.

  4. monitoring Sep 11, 2026, 02:31 PM UTC

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

  5. monitoring Sep 11, 2026, 02:38 PM UTC

    We have seen all traffic return to normal and are monitoring all services closely.

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

    This incident has been resolved.

  7. postmortem Sep 14, 2026, 01:28 PM UTC

    On the afternoon of Friday 11th September, Google Cloud \(GCP\) confirmed an infrastructure issue causing latency and packet loss. This resulted in one of our core databases resetting itself, disrupting calls for a brief period. Service was fully restored within 16 minutes of identification of the issue. Over the weekend, we reconfigured the database so calls are prioritised during initialisation. These changes remove the risk of recurrence in these circumstances.