Fly.io

Object storage

Connection times from Fly.io to Amazon S3 and Tigris.

Live measurements

Source

ORD

Chicago, Illinois (US)

S3 reachable

33 / 34

Nearest S3

24 ms

S3 · us-east-2

AWS reports issues affecting 2 monitored S3 regions

AWS Health ↗

AWS-reported incidents are marked below.

me-central-1 · UAE Region Availability ↗ me-south-1 · Bahrain Region Availability ↗

All Systems Operational

Tigris object read

HTTPS GET, including DNS, TLS, and object delivery. S3 measures TCP connection time only.

13 ms

0.0% loss

Tigris status ↗

S3 regional endpoints

Region TCP connection Loss
af-south-1 284 ms 0.0%
ap-east-1 244 ms 0.0%
ap-east-2 183 ms 0.0%
ap-northeast-1 192 ms 0.0%
ap-northeast-2 182 ms 0.0%
ap-northeast-3 175 ms 0.0%
ap-south-1 258 ms 0.0%
ap-south-2 290 ms 0.0%
ap-southeast-1 276 ms 0.0%
ap-southeast-2 187 ms 0.0%
ap-southeast-3 252 ms 0.0%
ap-southeast-4 262 ms 0.0%
ap-southeast-5 217 ms 0.0%
ap-southeast-6 215 ms 0.0%
ap-southeast-7 268 ms 0.0%
ca-central-1 95 ms 0.0%
ca-west-1 94 ms 0.0%
eu-central-1 140 ms 0.0%
eu-central-2 128 ms 0.0%
eu-north-1 183 ms 0.0%
eu-south-1 169 ms 0.0%
eu-south-2 174 ms 0.0%
eu-west-1 164 ms 0.0%
eu-west-2 133 ms 0.0%
eu-west-3 192 ms 0.0%
il-central-1 191 ms 0.0%
me-central-1 AWS incident 268 ms 0.0%
me-south-1 AWS incident — 100.0%
mx-central-1 135 ms 0.0%
sa-east-1 196 ms 0.0%
us-east-1 28 ms 0.0%
us-east-2 24 ms 0.0%
us-west-1 74 ms 0.0%
us-west-2 104 ms 0.0%