Vendor record
AWS
Checked
Front door check counts and AWS’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.
Front door checks
We have no front door checks against AWS in the last 30 days. That does not show whether it was reachable.
Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every AWS product, region or your app worked.
How we count front door checksAWS says
Incident posts from AWS’s status page, with its titles, impact levels and times. They say what AWS chose to post, not what reached your app.
A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.
5
incidents AWS posted, last 90 days
Median recorded duration: 1d 2h. From 5 incidents with vendor-supplied starts and recorded closure times.
Most recent records · all dates
[RESOLVED] Elevated packet loss
MinorAWS’s postStarted, per AWS
Closed in our record(1d 2h)
[RESOLVED] Increased Error Rates
MinorAWS’s postStarted, per AWS
Closed in our record(1d 1h)
[RESOLVED] Increased API Error Rates
MinorAWS’s postStarted, per AWS
Closed in our record(1d 2h)
[RESOLVED] Increased Packet loss
MinorAWS’s postStarted, per AWS
Closed in our record(4d)
[RESOLVED] Elevated Packet Loss
MinorAWS’s postStarted, per AWS
Closed in our record(1d 1h)
4 older records
Inaccurate Estimated Billing Data
MinorAWS’s postStarted, per AWS
Closed in our record(2d 5h)
[RESOLVED] Internet Connectivity Issues
MinorAWS’s postStarted, per AWS
Closed in our record(1d)
Region Availability
MajorAWS’s postStarted, per AWS
Latest status AWS postedInvestigating. No resolution posted.
Region Availability
MajorAWS’s postStarted, per AWS
Latest status AWS postedInvestigating. No resolution posted.
Your code, your dependencies
See which of your code paths call AWS
Connect GitHub or GitLab to find where your public or private repository uses AWS. Review each match and your alert settings.
Free to start. No credit card.
Use this record on your site
Add AWS status to your page.
Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.
Frequently Asked Questions
Is AWS currently down?
AWS's latest recorded status is Partial Outage. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.
When did AWS last have an outage?
The most recent closed incident record began 12 days ago and spans 1d 2h. The vendor reported degraded performance. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.
Does CheckUpstream publish an uptime percentage for AWS?
No. CheckUpstream does not run front door checks against AWS. The incident history on this page is what AWS reported, not a measure of how often it was available.
How do I monitor AWS in production?
Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.
What does AWS do?
AWS, or Amazon Web Services, is a cloud computing platform that provides on-demand infrastructure and managed services for building, deploying, and operating software. It is used by developers, operations teams, and enterprises to run applications, store data, and manage networking and security. Its main product surfaces are web-based consoles, APIs, and command-line tools across a large catalog of cloud services.
How does CheckUpstream track AWS?
This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.