Is AWS down right now?
AWS Health Dashboard currently reports partial outage for the selected AWS components.
Official incident history over the past 90 days. This is not a synthetic uptime claim.
View official history ↗- Scope
- Public AWS service events across regions, not account-specific health
- Source updated
- Checked by Qodex
This page reads AWS’s public service-health feed on the server. AWS recommends the signed-in Health Dashboard for events tied to your accounts and resources, so treat this as the public layer only.
Qodex does not operate AWS. Source: AWS Health Dashboard.
AWS is partial outage. Is your workflow?
An official status page answers whether the provider sees a broad service problem. It does not execute the request, repository, or browser journey your product depends on.
Region and service
Match the failing request to its exact service, region, edge location, and account-specific health view.
Credentials
Verify token expiry, scopes, role assumptions, and the identity used by the deployed environment.
Request and response
Capture the real endpoint, status code, headers, latency, and response body from the failing path.
Dependent flow
Replay the application journey that depends on the platform and assert the user-visible result.
Official components and incidents
Scope matters. The rows below come from AWS Health Dashboard and are filtered to AWS public service health. They are evidence from the provider, not synthetic Qodex probes.
- Service disruption: Increased Error RatesinvestigatingImpact: critical · Updated Apr 30, 2026, 7:25 AM UTC
- Impact: critical · Updated Apr 30, 2026, 7:07 AM UTC
Troubleshoot AWS without guessing
Start with the provider state, then move inward through your account, request, application, and final user journey.
| Signal | What to verify |
|---|---|
| Region and service | Match the failing request to its exact service, region, edge location, and account-specific health view. |
| Credentials | Verify token expiry, scopes, role assumptions, and the identity used by the deployed environment. |
| Request and response | Capture the real endpoint, status code, headers, latency, and response body from the failing path. |
| Dependent flow | Replay the application journey that depends on the platform and assert the user-visible result. |
AWS status FAQ
Is AWS down right now?
The status above is rendered from AWS Health Dashboard and scoped to Public AWS service events across regions, not account-specific health. If the official source is unavailable, Qodex reports the status as unavailable instead of guessing.
Why can AWS be operational while my integration is failing?
Provider dashboards report aggregate platform health. Your account, credentials, model access, region, request contract, SDK, repository, browser session, or downstream application flow can still fail independently.
Does Qodex monitor or operate AWS?
No. AWS is operated by its provider. Qodex renders the provider’s public status data here and helps engineering teams test the API and UI workflows that depend on it.
What should I test after the provider status is green?
Replay the real request and user journey with the same environment, credentials, payload, and assertions used in production. Check the response contract and the final user-visible result, not only connectivity.
Provider green is the start of diagnosis.
Qodex tests the API and UI path your team actually ships, then keeps the evidence with the failure.