Live checks, official provider updates, and incident history for AWS.
See the latest checks and provider updates, with separate results for Pakistan and other countries.
Some recent checks or provider updates suggest problems. A wider outage has not been confirmed.
Updates every 5 minutesChecks cover the measured service access; individual app features or accounts can behave differently.
The latest website check reached the service at 03-Oct-2026, 4:50 am PKT. This is one signal from the monitoring location.
The percentages above describe the networks measured, not every user. Regional results use checks from the relevant countries.
A responsive public website does not guarantee that every part of AWS is working. Login, notifications, payments, media, APIs, or regional routes can fail independently. We describe the evidence we have rather than turning a single successful check into a broad claim. When the latest stored status grows stale, the page shows that the status is not verified until new measurements arrive.
A status label is only a starting point. The exact symptom and the networks involved help explain what may be happening.
Cloud products span dashboards, APIs, regions, storage, DNS, and customer workloads. An incident in one component may leave others unaffected.
Record the affected product, region, response code, and start time. Compare a dashboard problem with API behavior rather than treating the provider as a single endpoint.
Check the provider's official status source and inspect your own application logs or origin infrastructure. Avoid attributing every downstream error to the cloud provider.
If the service fails on only one device, browser, or account, the cause may be local. If it fails across different connections and other people report the same symptom at the same time, a wider problem becomes more plausible. Keep troubleshooting steps reversible, particularly when a payment, booking, upload, or form submission could already be in progress.
Official status and independent public endpoint checks are combined where possible. Pakistan probe data can help show whether access differs by region or network.
Our worker tests safe public endpoints for DNS resolution, TCP connectivity, TLS negotiation, HTTPS response, and latency. RIPE Atlas can add Pakistani and international probe observations when configured; OONI may provide access context. Official status feeds are considered where the provider publishes one. These signals are weighted conservatively, and an unavailable provider contributes no positive evidence.
A public provider page responding does not prove that every region or customer workload is healthy.
For AWS, record the affected product, region, endpoint, error code, and start time. Compare any official component notice with your own application logs and recent changes. A cloud dashboard may fail while workloads continue, and an origin error may appear behind an otherwise healthy delivery network. Pakistan-based probes can help locate an access difference when configured, but one remote check cannot diagnose a customer's deployment. Treat the page's public measurements as a narrow signal, not a service-level guarantee.
Independent checks and official updates help confirm wider disruptions. For a problem with your own account, use the service’s official support channel.
Historical charts use stored checks. They start empty and grow as monitoring runs; no incidents or availability figures are fabricated.
Switch between 24-hour, 7-day, 30-day, and 90-day views.
Average public endpoint availability in this view: 100%. This measures configured endpoints, not every feature of the service.
No confirmed incidents have been recorded for AWS yet.
A public endpoint availability percentage measures only configured endpoints. It does not promise that every feature, region, account, or app function was available for the same percentage of time. Older raw checks are rolled into hourly aggregates and removed under the retention policy, while incident records remain available for context.
