Fly.io

Storage paths

Compare live connection time from Fly compute to every commercial Amazon S3 region and a real object read from Tigris.

Historical rollup · last 1h

Median connection time · 17% coverage · 10 deploy/topology samples excluded

Source

ORD

Chicago, Illinois (US)

S3 reachable

0 / 34

TCP connections

Nearest S3

—

Waiting for data

Provider-reported status

AWS reports issues affecting 2 monitored S3 regions

AWS Health ↗

RTT still shows the observed connection failure, but marks affected endpoints so an AWS outage is not mistaken for a Fly network issue.

me-central-1 · UAE Increased Error Rates ↗ me-south-1 · Bahrain Increased Error Rates ↗

Tigris global object · All Systems Operational

A real cached object read

Unlike the S3 TCP probes below, this includes DNS, TLS, HTTP, and object delivery from RTT’s public canary bucket.

—

100.0% loss

Amazon Web Services

S3 regional endpoints

Region Connection Loss
af-south-1 — 100.0%
ap-east-1 — 100.0%
ap-east-2 — 100.0%
ap-northeast-1 — 100.0%
ap-northeast-2 — 100.0%
ap-northeast-3 — 100.0%
ap-south-1 — 100.0%
ap-south-2 — 100.0%
ap-southeast-1 — 100.0%
ap-southeast-2 — 100.0%
ap-southeast-3 — 100.0%
ap-southeast-4 — 100.0%
ap-southeast-5 — 100.0%
ap-southeast-6 — 100.0%
ap-southeast-7 — 100.0%
ca-central-1 — 100.0%
ca-west-1 — 100.0%
eu-central-1 — 100.0%
eu-central-2 — 100.0%
eu-north-1 — 100.0%
eu-south-1 — 100.0%
eu-south-2 — 100.0%
eu-west-1 — 100.0%
eu-west-2 — 100.0%
eu-west-3 — 100.0%
il-central-1 — 100.0%
me-central-1 AWS incident — 100.0%
me-south-1 AWS incident — 100.0%
mx-central-1 — 100.0%
sa-east-1 — 100.0%
us-east-1 — 100.0%
us-east-2 — 100.0%
us-west-1 — 100.0%
us-west-2 — 100.0%