Fly.io Status · History · Incident #4502
RESOLVEDIngress Traffic issues in GRU
Major · Started Jun 10, 2026 · 7:39 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 #4502
RESOLVEDMajor · Started Jun 10, 2026 · 7:39 PM
Duration
13m
Severity
Major
Detection lead
—
User reports
—
Summary
This incident has been resolved.
Started
Jun 10, 2026 · 7:39 PM
Resolved
Jun 10, 2026 · 7:52 PM
Duration
13m
Severity
Major
Event timeline
Identified
Jun 10 · 7:39 PM Fly.ioSome of our edge nodes in GRU has suffered an error that crashed some of the critical services. We're currently working to bring them back online. Some traffic entering through GRU (i.e. users connecting from around GRU) may be temporarily affected: connections may see increased latency or be occasionally dropped.
Resolved
Jun 10 · 7: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.
By Designmodo
Designmodo Inc. 169 Madison Ave, #79627, New York, NY 10016, United States
Copyright © 2010-2026