Flightcontrol incident

Private networking issues in SYD

Minor Resolved View vendor source →

Flightcontrol experienced a minor incident on May 30, 2026 affecting SYD - Sydney, Australia, lasting 8m. The incident has been resolved; the full update timeline is below.

Started
May 30, 2026, 01:29 PM UTC
Resolved
May 30, 2026, 01:37 PM UTC
Duration
8m
Detected by Pingoru
May 30, 2026, 01:29 PM UTC

Affected components

SYD - Sydney, Australia

Update timeline

  1. identified May 30, 2026, 01:29 PM UTC

    Due to an upstream provider issue, Private Networking (6PN) is currently degraded in SYD region. Communication between Machines in SYD region and Machines in other regions may fail at this time. Newly created Machines in SYD may fail to sync to other regions (may not show up in Machines API List endpoint, or state may be incorrect). Additionally, TLS certificate resolution and Machines API authentication may currently be degraded in the SYD region. We are working with our upstream providers to resolve this issue.

  2. monitoring May 30, 2026, 01:32 PM UTC

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

  3. resolved May 30, 2026, 01:37 PM UTC

    This incident has been resolved.