Fly.io Status · History · Incident #4114
RESOLVEDIncreased latency in SJC
Minor · Started May 28, 2026 · 9:08 PM
$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 #4114
RESOLVEDMinor · Started May 28, 2026 · 9:08 PM
Duration
1h 58m
Severity
Minor
Detection lead
—
User reports
—
Summary
This incident has been resolved.
Started
May 28, 2026 · 9:08 PM
Resolved
May 28, 2026 · 11:07 PM
Duration
1h 58m
Severity
Minor
Event timeline
Investigating
May 28 · 9:08 PM Fly.ioWe are currently investigating increased latency in SJC.
Monitoring
May 28 · 9:56 PM Fly.ioWe have implemented a mitigation for the issue and are monitoring for stability. This issue happened on the edge hosts in SJC, which means that any traffic near/around SJC would have been affected during the incident. We will provide a more detailed write-up on our Infra Log (https://fly.io/infra-log/) later once we have a better picture of the entire incident.
Identified
May 28 · 10:25 PM Fly.ioWe're still seeing connection issues originating from SJC/LAX/West Coast US and are still investigating.
Monitoring
May 28 · 10:33 PM Fly.ioA fix has been implemented and we are monitoring the results.
Monitoring
May 28 · 10:34 PM Fly.ioWe are continuing to monitor for any further issues.
Resolved
May 28 · 11:07 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