AWS (DynamoDB, us-east-1) uptime
AWS (DynamoDB, us-east-1), checked by StatOSS every 5 minutes from Aarhus and Copenhagen in Denmark, Falkenstein in Germany, Ashburn in the USA, Singapore, and Sydney in Australia. Measured from outside, with every outage dated in UTC.
AWS (DynamoDB, us-east-1) is up.
Up for 6 d 3 h. Last checked 2026-10-06 11:36 UTC from Sydney, Australia: 200 in 709 ms.
Last 24 hours
Up for 6 d 3 h100% passed
288 checks, median 310 ms from Falkenstein, all passed
95% under 337 ms
Response time by region
Medians over this range, on one scale up to 1,000 ms. Europe's places are scaled to Falkenstein, its fastest shared place.
Last 90 days
Up for 6 d 3 h100% passed
1,764 checks, median 309 ms from Copenhagen, all passed
95% under 336 ms
Response time by region
Medians over this range, on one scale up to 1,000 ms. Europe's places are scaled to Copenhagen, its fastest shared place.
In the last 24 hours AWS (DynamoDB, us-east-1) passed 288 of 288 checks, 100%.
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.
| Last | Passed | Checks | Outages |
|---|---|---|---|
| 24 hours | 100% | 288 of 288 | 0 |
| 7 days | Not enough history yet: checks began on 30 Sep 2026 | ||
| 30 days | Not enough history yet: checks began on 30 Sep 2026 | ||
| 90 days | Not 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.
| From | Median | 95th percentile | Mean | Checks |
|---|---|---|---|---|
| Falkenstein, Germany | 322 ms | 344 ms | 322 ms | 192 |
| Ashburn, USA | 121 ms | 203 ms | 125 ms | 564 |
| Copenhagen, Denmark | 310 ms | 342 ms | 314 ms | 171 |
| Singapore | 880 ms | 1,047 ms | 892 ms | 560 |
| Sydney, Australia | 705 ms | 887 ms | 801 ms | 84 |
| Aarhus, Denmark | 344 ms | 378 ms | 346 ms | 193 |
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: Aarhus and Copenhagen in Denmark, Falkenstein in Germany, 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.