Vendor record
AWS S3
Checked
Front door check counts and AWS S3’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.
Front door checks
We send a request to a documented AWS S3 endpoint and count the checks that got the answer it is documented to give.
Front door reachable in 2,879 of 2,879 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.
- Endpoint checked
- s3.ap-southeast-2.amazonaws.com
- Scope
- s3ap-southeast-2
- First check in this window
- Latest clear answer
Front door reachable in 2,879 of 2,879 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.
- Endpoint checked
- s3.eu-west-1.amazonaws.com
- Scope
- s3eu-west-1
- First check in this window
- Latest clear answer
Front door reachable in 2,879 of 2,879 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.
- Endpoint checked
- s3.us-east-1.amazonaws.com
- Scope
- s3us-east-1
- First check in this window
- Latest clear answer
Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every AWS S3 product, region or your app worked.
How we count front door checksShorter disruptions
Our checks are 15 minutes apart, so they miss disruptions shorter than that. Datadog runs a separate outage tracker that may show disruptions our checks cannot see.
Independent outage detection for AWS S3: Datadog’s Updog(opens in a new tab)CheckUpstream is not affiliated with Datadog.
AWS S3 says
Incident posts from AWS S3’s status page, with its titles, impact levels and times. They say what AWS S3 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.
AWS does not publish a component catalog for this feed. This page includes an incident only when AWS names this product in the event. A quiet record does not mean the product was available.
0
incidents AWS S3 posted, last 90 days
Most recent records · all dates
No incidents recorded
AWS S3 has posted nothing we recorded. That is an empty history, not evidence of uninterrupted service.
Your code, your dependencies
See which of your code paths call AWS S3
Connect GitHub or GitLab to find where your public or private repository uses AWS S3. Review each match and your alert settings.
Free to start. No credit card.
Use this record on your site
Add AWS S3 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 S3 currently down?
AWS S3's latest recorded status is Operational. 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 S3 last have an outage?
We have no closed incident record for AWS S3 in the past 12 months. Missing records do not establish that the service had no incidents.
Does CheckUpstream publish an uptime percentage for AWS S3?
No. CheckUpstream checks AWS S3’s front door every 15 minutes and publishes how many checks reached it over the last 30 days, with the endpoint checked. Checks 15 minutes apart cannot see disruptions shorter than that. A percentage would claim more than the checks can show.
How do I monitor AWS S3 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.
How does CheckUpstream track AWS S3?
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.