Fly · Operational
Observed by INTERNETMON
← All status pages
Vendor-reported status observed by INTERNETMON

Fly.io status

Fly · Atlassian Statuspage
Operational
Atlassian Statuspage reports All Systems Operational.
Platform and regions
Checked Poll cadence every 60 seconds Feed state fresh
Official signal: this is the provider's own report, collected and retained inside INTERNETMON. Compare it with independent regional monitoring when troubleshooting.

Active incidents

No active incidents were included in this vendor report.

Maintenance

No active or upcoming maintenance was included in this vendor report.

Component health

Reported
53
Retained
53
Affected retained
0
Projection scope: complete · 53 retained of 53 reported components across 5 source groups.
AMS - Amsterdam, Netherlands Group: Regional Availability Operational
Fly Machine .internal DNS Group: DNS Operational
Usage Metrics API Group: Billing Operational
Upstash for Redis Group: Extensions Operational
Customer Applications Operational
Management Plane - ORD Group: Managed Postgres Operational
Stripe API Connection Group: Billing Operational
Dashboard Operational
ARN - Stockholm, Sweden Group: Regional Availability Operational
Fly Machine External DNS Group: DNS Operational
Management Plane - IAD Group: Managed Postgres Operational
Machines API Operational
Management Plane - FRA Group: Managed Postgres Operational
*.flyio.net Nameservers Group: DNS Operational
Management Plane - GRU Group: Managed Postgres Operational
Persistent Storage (Volumes) Operational
BOM - Mumbai, India Group: Regional Availability Operational
Management Plane - LAX Group: Managed Postgres Operational
flydns.net Group: DNS Operational
Deployments Operational
Showing 20 of 53 retained components in the compact HTML summary. The JSON projection and interactive view contain the full bounded sample.

Recent observed status changes and checkpoints

These are sparse stored checkpoints—state changes plus hourly samples—not an uptime calculation or an exact incident duration.

Operational
HTTP 200 · 158.54 ms feed latency
Operational
HTTP 200 · 239.28 ms feed latency
Operational
HTTP 200 · 255.01 ms feed latency
Operational
HTTP 200 · 71.63 ms feed latency
Operational
HTTP 200 · 194.93 ms feed latency
Operational
HTTP 200 · 259.26 ms feed latency
Operational
HTTP 200 · 109.31 ms feed latency
Operational
HTTP 200 · 345.91 ms feed latency
Operational
HTTP 200 · 127.83 ms feed latency
Operational
HTTP 200 · 204.58 ms feed latency

Collection details

Provider adapter
Atlassian Statuspage
Feed response
HTTP 200
Feed latency
187.47 ms