Prime Day 2026 by the Numbers: How AWS Handled 192 Million Requests a Second
DynamoDB peaked at 192M requests/sec on Prime Day 2026. Every AWS stat explained in plain English, plus a technical deep-dive for developers.
During Prime Day 2026 (23–26 June), Amazon DynamoDB peaked at 192 million requests per second and handled more than 59 trillion requests across the four days, according to AWS. AWS published the figures on 6 October in "All the numbers: Amazon Prime Day 2026 powered by AWS" by Channy Yun, and highlighted them again in its 13 October weekly roundup.
Big numbers like these are hard to picture. So this piece does two things. First, it translates each headline stat into everyday terms. Then it explains what each AWS service actually does during a sale this size.
What does "192 million requests a second" actually mean?
A "request" is a single ask to a database: what's the price of this item?, is it in stock?, add this to my cart. Every time you load a product page, dozens of these fire in the background.
Some back-of-envelope maths (our own calculations, using AWS's figures):
- 192 million a second is like every person on Earth (about 8.2 billion people) asking the database one question every 43 seconds, nonstop.
- 59 trillion requests over four days works out to an average of about 171 million a second (59 trillion ÷ 345,600 seconds).
- So the peak was only about 12% above the average. For a sale event, that's a surprisingly flat curve. Demand was intense the whole time, not just in a single spike.
- Compared with Prime Day 2025, when AWS reported a DynamoDB peak of 151 million a second, the 2026 peak is about 27% higher.
Editor's take (Lov Singh): The flat curve is the stat I find most interesting. Engineers usually fear one huge spike. A four-day plateau near peak is a different challenge: there's no quiet period to recover in, so the system has to stay healthy for 96 hours straight.
Prime Day 2026 AWS numbers, explained simply
All figures are from AWS's own post. The "In plain English" column is ours.
| AWS service | Prime Day 2026 figure | In plain English |
|---|---|---|
| DynamoDB | Peak 192M requests/sec; 59T+ requests over 4 days | The main "lookup" database for carts, prices and stock |
| ElastiCache | 2.1 trillion requests in one minute; 2.3 quadrillion daily at peak | A super-fast memory layer that answers repeat questions before they hit the database |
| SQS | 213M messages/sec peak | Queues of "to-do" notes passed between systems, like order placed → charge card → pack |
| Kinesis Data Streams | 988M records/sec peak | A live conveyor belt of events such as clicks and orders, for real-time processing |
| SNS | 5 trillion messages in a day | The broadcast system that tells many services "this happened" |
| Lambda | 2.3 trillion+ invocations per day | Small pieces of code that run on demand, then disappear |
| ECS on Fargate | 158.3M tasks per day on average (up 47.7% year on year) | Containers launched without managing servers |
| EBS | 24.8 trillion+ I/O operations; more than an exabyte moved daily | Hard drives attached to cloud servers |
| Aurora | 5,491 TB stored; 1,194 TB transferred | Amazon's relational (SQL) database for structured records |
| CloudFront | 2.1 trillion+ HTTP requests over the week (up 5%) | The delivery network serving images and pages close to you |
| EC2 / Graviton | Up to 49% of Amazon.com's EC2 compute | Amazon's own Arm-based chips doing half the work |
| CloudTrail | 3.6 trillion events in four days (up 44%) | An audit log of who did what |
| CloudWatch | 2.15 quadrillion metric observations per day | The dashboards and alarms engineers watch |
| GuardDuty | 14.08 trillion log events per hour (up 59%) | Security monitoring for suspicious activity |
| Fault Injection Service | 44,000+ experiments (over 6x 2025) | Deliberately breaking things before the sale to prove recovery works |
Two more ways to picture it:
- ElastiCache's 2.1 trillion requests in one minute is about 35 billion a second. That's roughly 180 times DynamoDB's peak. This is the point of a cache: most questions are answered from memory, so the database only sees what the cache can't answer.
- One exabyte a day on EBS is a million terabytes. If your laptop has a 1 TB drive, that's a million laptops' worth of data moved, every day.
How does AWS handle Prime Day traffic? A technical deep-dive
New to cloud basics? Read what AWS is first. This section assumes you know the basics.
DynamoDB: partitioned key-value storage at scale
DynamoDB splits data into partitions by key, so load is spread across many machines. The 192M/sec peak is spread across Amazon's many internal teams and tables, not one giant table. AWS says DynamoDB kept single-digit millisecond responses throughout. The lesson for builders: performance depends on good key design. A "hot" key, like one viral product, can concentrate traffic on one partition. That's why patterns such as write sharding and caching matter.
ElastiCache: protecting the database
At these volumes, a cache isn't optional. Product details, prices and session data are read far more often than they change. Serving those reads from memory keeps the database load sane and response times low.
SQS, SNS and Kinesis: decoupling
Placing an order sets off a chain: payment, inventory, fulfilment, emails, analytics. Instead of each system calling the next directly, they pass messages through SQS (queues), SNS (fan-out notifications) and Kinesis (streams). If one downstream system slows, messages wait in line instead of the whole checkout failing. 213 million SQS messages a second shows how much of Amazon works this way.
Aurora: where relational data still wins
Not everything fits a key-value model. Aurora holds structured data that benefits from SQL and transactions. Its 5,491 TB stored is a reminder that most large systems mix database types.
Graviton, Lambda and Fargate: compute that scales
Up to 49% of Amazon.com's EC2 compute ran on Graviton, AWS's own Arm chips, which AWS markets on price-performance and energy efficiency. Lambda and Fargate let teams scale code and containers without managing servers, and Fargate task volume grew 47.7% year on year.
Chaos engineering: 44,000 rehearsals
The quietest stat may be the most important. AWS ran more than 44,000 Fault Injection Service experiments before the event, over six times 2025's count. The idea is simple: break things on purpose, in a controlled way, so you know recovery works before millions of shoppers arrive.
What can developers learn from Prime Day 2026?
- Cache aggressively and measure your hit rate.
- Design keys for even load, and plan for hot items.
- Use queues between services so one slow system doesn't cascade.
- Rehearse failure before your own peak, not during it.
- Watch costs while you experiment. If you're trying DynamoDB, Lambda or SQS yourself, our AWS Free Tier 2026 guide explains how to avoid a surprise bill.
- Add AI carefully. Generative AI features built on Amazon Bedrock and Nova add new latency and cost to plan for.
These systems are run by AWS engineers. If that sounds like your kind of job, read our AWS hiring and interview loop guide.
Why Prime Day numbers matter for Amazon's earnings
Prime Day 2026 fell in June, inside Q2, while Prime Day 2025 was in July. That shift makes Amazon's Q3 2026 growth look lower on paper. We explain it, with a results scorecard, in our Amazon Q3 2026 earnings preview. AWS growth (37% in Q2) is the number to watch there.
What are developers saying?
We looked for in-depth community discussion of the 2026 numbers on r/aws and didn't find threads substantial enough to quote. The questions engineers usually raise about these posts are fair ones:
- Is 192M/sec one table or the sum across Amazon? (AWS's post gives the overall peak, not a per-table figure.)
- How much of the load does the cache absorb before DynamoDB?
- Is Graviton's 49% about cost, power, or both?
FAQ
When was Prime Day 2026?
23–26 June 2026, for Prime members, according to AWS.
How many requests did DynamoDB handle on Prime Day 2026?
More than 59 trillion over the four days, with a peak of 192 million requests per second.
How does that compare with Prime Day 2025?
AWS reported a DynamoDB peak of 151 million requests per second in 2025, so 2026 was about 27% higher.
What is DynamoDB?
A fully managed NoSQL key-value database from AWS, built for very high request rates with low latency.
What is AWS Graviton?
AWS's own Arm-based server processor. It powered up to 49% of the EC2 compute Amazon.com used on Prime Day 2026.
What is the AWS Fault Injection Service?
A tool for running controlled "chaos" experiments that simulate failures. Amazon ran more than 44,000 before Prime Day 2026.
Where did these numbers come from?
AWS's News Blog post "All the numbers: Amazon Prime Day 2026 powered by AWS" (6 October 2026) and the AWS Weekly Roundup of 13 October 2026.
Sources
- AWS News Blog: All the numbers: Amazon Prime Day 2026 powered by AWS
- AWS News Blog: AWS Weekly Roundup, 13 October 2026
- AWS News Blog: AWS services scale to new heights for Prime Day 2025
- Amazon: Q2 2026 earnings report
Featured image: AWS us-west-2 data centre campus, Morrow County, Oregon (aerial). Tedder / Wikimedia Commons (CC BY-SA 4.0). Source
