Fly.io Status · History · Incident #4063
RESOLVEDPrivate networking issues in SYD
Major · Started May 27, 2026 · 11:54 AM
$HTTP_PROTOCOL = (isset($_SERVER['HTTPS']) && ($_SERVER['HTTPS'] == 'on' || $_SERVER['HTTPS'] == 1)) || (isset($_SERVER['HTTP_X_FORWARDED_PROTO']) && $_SERVER['HTTP_X_FORWARDED_PROTO'] == 'https') ? 'https://' : 'http://'; $SITE_URL = $HTTP_PROTOCOL . $_SERVER['SERVER_NAME'] . '/'; ?>
Fly.io Status · History · Incident #4063
RESOLVEDMajor · Started May 27, 2026 · 11:54 AM
Duration
58m
Severity
Major
Detection lead
—
User reports
—
Summary
This incident has been resolved.
Started
May 27, 2026 · 11:54 AM
Resolved
May 27, 2026 · 12:52 PM
Duration
58m
Severity
Major
Event timeline
Identified
May 27 · 11:54 AM Fly.ioDue 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.
Monitoring
May 27 · 12:13 PM Fly.ioA fix has been implemented and we are monitoring the results.
Resolved
May 27 · 12:52 PM Fly.ioThis incident has been resolved.
Pulsetic catches degradations minutes before vendors acknowledge them.
Stay online, all the time, with Pulsetic's uptime prime. Try Free
By Designmodo
MONITORING
STATUS
SERVICE
COMPARE
ACCOUNT