StatOSS

AWS (DynamoDB, us-east-1) uptime

AWS (DynamoDB, us-east-1), checked by StatOSS every 5 minutes from Helsinki in Finland, Falkenstein in Germany, Copenhagen in Denmark, Ashburn in the USA, Singapore and Sydney in Australia. Measured from outside, with every outage dated in UTC.

dynamodb.us-east-1.amazonaws.comEvery 5 minutes

AWS (DynamoDB, us-east-1) is up.

Up for 51 d 9 h. Last checked 2026-11-20 18:21 UTC from Falkenstein, Germany: 200 in 296 ms.

Last 24 hours

Up for 51 d 9 h100% passed

288 checks, median 295 ms from Copenhagen, all passed

95% under 307 ms

Response time by region
EuropeEurope295 ms
N. AmericaNorth America88 ms
AsiaAsia902 ms
OceaniaOceania718 ms

Medians over this range, on one scale up to 1,000 ms.

Last 90 days

Up for 51 d 9 h99.99% passed

14,799 checks, median 303 ms from Copenhagen, 1 timeout

95% under 346 ms

Response time by region
EuropeEurope303 ms
N. AmericaNorth America111 ms
AsiaAsia870 ms
OceaniaOceania723 ms

Medians over this range, on one scale up to 1,000 ms. Europe's places are scaled to Copenhagen, its fastest shared place.

Each bar of the first strip is one check, five minutes apart; each bar of the second is a day. Height is response time, red is a failed check, amber a timeout. Times are UTC, as of 2026-11-20 18:24 UTC.

In the last 30 days AWS (DynamoDB, us-east-1) passed 8,855 of 8,856 checks, 99.98%.

No outage since checks began on 30 Sep 2026.

Availability

The share of checks that passed, and the outages that began, in each window up to now.

LastPassedChecksOutages
24 hours100%288 of 2880
7 days99.95%2,007 of 2,0080
30 days99.98%8,855 of 8,8560
90 daysNot enough history yet: checks began on 30 Sep 2026

A year of checks is kept; the year's figure appears here once there is a year of them.

Response time by location

Over the last 7 days, from the checks that passed: the time from the start of the request to the answer's headers, with the DNS lookup, the connection and TLS included.

FromMedian95th percentileMeanChecks
Falkenstein, Germany314 ms339 ms315 ms44
Helsinki, Finland336 ms385 ms343 ms42
Ashburn, USA98 ms177 ms99 ms501
Copenhagen, Denmark296 ms305 ms296 ms420
Singapore880 ms1,060 ms887 ms504
Sydney, Australia709 ms886 ms717 ms503

Outages

None detected since checks began on 30 Sep 2026.

What is checked

Amazon Web Services. us-east-1, in Northern Virginia, is its oldest and largest region, and the default in many SDKs and tutorials.

StatOSS sends GET https://dynamodb.us-east-1.amazonaws.com/ and counts the check as passed on status 200 with the text healthy in the body within 10 seconds. The DynamoDB endpoint in us-east-1. A request without credentials answers 200 with the text `healthy: dynamodb.us-east-1.amazonaws.com`, and the check looks for the word healthy.

One service in one region. Other regions and other AWS services, S3 and EC2 among them, are not checked here.

AWS (DynamoDB, us-east-1) reports its own incidents at health.aws.amazon.com/health/status. The figures here are measured from outside and can differ from it in both directions.

How it is measured

  • One check every 5 minutes, from one location at a time in turn: Helsinki in Finland, Falkenstein in Germany, Copenhagen in Denmark, Ashburn in the USA, Singapore and Sydney in Australia.
  • A check fails when no answer comes within 10 seconds, when the connection or TLS fails, or when the answer is not status 200 with the text healthy in the body.
  • A failed check is repeated at once from a second location, and counts only when that location fails too, or cannot answer within 20 seconds.
  • Two failed checks in a row make an outage, dated from the second, and the first check that passes ends it. A failure shorter than 10 minutes may not make one, and times are good to about 5 minutes.
  • Availability is the share of checks that passed. There are no maintenance windows: every check counts.

It is the same check a StatOSS status page runs for its owner, with the same rules; the docs on checks have the details.