FROM ALL SOURCES
No sign of a widespread Fly.io problem right now; every source we read is quiet.
confidence: medium Vendor: operational · users: normal · routing: no data.
- Vendor status page Operational · 1 open incident
- User reports 0 in 15 min vs ~0 typical
- Routing / BGP no ASN mapped, so no routing view
- News & network weather no recent mentions
- Providers it may run on (inferred) no mapped dependencies
- CISA KEV (context) no recent entries for this vendor
| Clock | Started | Running |
|---|---|---|
| Vendor clock when the vendor's open incident started | 9 days | |
| Crowd clock when user reports began rising above normal | not seen | n/a |
| Network clock when routing anomaly data first flagged it | not seen | n/a |
| ORBIT clock when our checker first recorded the change | not seen | n/a |
Evidence
- Official page: Operational (“All Systems Operational”). evidence confidence: high
- Vendor stage: resolved on “LAX region outage”. evidence confidence: high
- User reports are within normal range (0 in 15 min). evidence confidence: low
What we don't know: what is happening inside Fly.io's own systems, how many users are actually affected (reports are self-selected and unverified), and anything from routing / bgp, providers it may run on (inferred). Routing data shows reachability, not whether the app works.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Generated .
Cloudy_Day's take
Stage vs. health
The vendor's stage is “resolved”. Stage tells you where they are in their process; health is what users experience. Right now vendor: operational · users: normal · routing: no data. Vendor status and outside signals roughly agree.
Who depends on whom
1 other service in our catalog may lean on Fly.io, so trouble here can show up elsewhere first. Dependency chains are where single points of failure hide.
Identity & trust lens
Even without an identity system involved, outages push people toward workarounds: password resets, unofficial apps and “status” links in DMs. Each one is a trust decision. Use official channels.
For users
Nothing points to a broad problem. If it's broken for you, try “Is it just me?” and check your own network first.
For security teams
Treat this as an availability event unless an official source says otherwise. Check which of your systems sit on Fly.io, watch for outage-themed phishing aimed at your users, and log what you see with timestamps (all four clocks).
What to watch next
Any new vendor incident, a jump in user reports above baseline, or trouble at the providers Fly.io may depend on.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Independent researcher; not affiliated with Fly.io. No blame or attack claims without an official source. Generated .
INCIDENT REPLAY
LAX region outage
critical resolved · started · resolved
9 updates
- investigating
We are investigating an upstream provider outage in LAX region. Apps and Managed Postgres clusters in LAX region may be unreachable at this time.
- identified
A subset of Apps and Managed Postgres clusters in the LAX region are unavailable due to an upstream datacenter power outage.
- identified
A subset of Apps and Managed Postgres clusters in the LAX region are unavailable due to an upstream datacenter power outage.
- identified
We are seeing hosts start to come back online. Apps and Managed Postgres clusters may still be unreachable at this time.
- identified
All hosts are back online and we are restarting services. Apps and Managed Postgres will start becoming available shortly.
- monitoring
Apps and Managed Postgres clusters in the LAX region should now all be accessible. Some app metrics are still recovering. We're continuing to monitor the region health.
- monitoring
All services in the LAX region are operating normally. We’re continuing to monitor while we await final confirmation from our datacenter provider that the issue is fully resolved.
- monitoring
The LAX region is currently online and functioning correctly. However, the datacenter is experiencing reduced redundancy, so we are continuing to monitor for any possible issues.
- resolved
The LAX datacenter has remained stable, and all hosts in the region are healthy. This incident is now resolved.
Community comments (0)
Comments are opinions of visitors, not statements by Cloudy_Day. Every comment is held for review before it appears. Links are removed, and personal data is redacted. Community guidelines.
No approved comments yet.
How to read this: official status comes from each provider's own public status page. User reports are unverified visitor reports. Things that happen at the same time are coincidence, not causation. Cloudy_Day is independent and not an official status source for any company listed.