Fly.io

Storage paths

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

Live measurements

Source

ORD

Chicago, Illinois (US)

S3 reachable

33 / 34

TCP connections

Nearest S3

37 ms

S3 · us-east-1

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.

5 ms

0.0% loss

Amazon Web Services

S3 regional endpoints

Region Connection Loss
af-south-1 267 ms 0.0%
ap-east-1 234 ms 0.0%
ap-east-2 224 ms 0.0%
ap-northeast-1 183 ms 0.0%
ap-northeast-2 292 ms 0.0%
ap-northeast-3 243 ms 0.0%
ap-south-1 287 ms 0.0%
ap-south-2 345 ms 0.0%
ap-southeast-1 302 ms 0.0%
ap-southeast-2 215 ms 0.0%
ap-southeast-3 311 ms 0.0%
ap-southeast-4 250 ms 0.0%
ap-southeast-5 278 ms 0.0%
ap-southeast-6 232 ms 0.0%
ap-southeast-7 259 ms 0.0%
ca-central-1 88 ms 0.0%
ca-west-1 87 ms 0.0%
eu-central-1 194 ms 0.0%
eu-central-2 187 ms 0.0%
eu-north-1 158 ms 0.0%
eu-south-1 210 ms 0.0%
eu-south-2 147 ms 0.0%
eu-west-1 121 ms 0.0%
eu-west-2 130 ms 0.0%
eu-west-3 157 ms 0.0%
il-central-1 204 ms 0.0%
me-central-1 AWS incident 244 ms 0.0%
me-south-1 AWS incident — 100.0%
mx-central-1 96 ms 0.0%
sa-east-1 202 ms 0.0%
us-east-1 37 ms 0.0%
us-east-2 73 ms 0.0%
us-west-1 176 ms 0.0%
us-west-2 90 ms 0.0%