Fly.io

Object storage

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

Last 3h

Median connection time · 92% coverage · 165 deploy/topology samples excluded

Source

ORD

Chicago, Illinois (US)

S3 reachable

0 / 34

Nearest S3

—

Waiting for data

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.

—

100.0% loss

Tigris status ↗

S3 regional endpoints

Region TCP 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%