Skip to content
UpButler
ProductAgentsStatus pagesDocsPricing
Sign inStart free

Is AWS us-east-1 (N. Virginia) down?

AWS us-east-1 (N. Virginia) is up

Right now

No. AWS us-east-1 (N. Virginia): no incidents reported.

Last checked (2026-10-10 07:16 UTC) from health.aws.amazon.com · every 300s

For agents

proceed

Proceed.

GET upbutler.com/status/aws/us-east-1/status.agent.json

MCP: upstream_status {"service":"aws","component":"us-east-1"}

The largest AWS region. Global control planes (IAM, Route 53, CloudFront configuration) depend on it, so its incidents reach other regions.

Part of Amazon Web Services status.

What Amazon Web Services says

Operational

Taken as is from Amazon Web Services's own AWS Health public events. Incident titles and component names below are theirs. Narrowed to what concerns AWS us-east-1 (N. Virginia).

Open health.aws.amazon.com

What UpButler measured

There is no keyless endpoint of Amazon Web Services that says anything useful, so UpButler does not probe it. To check your own Amazon Web Services account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.

AWS us-east-1 (N. Virginia): what Amazon Web Services lists

1 operational

  • us-east-1Operational

AWS us-east-1 (N. Virginia) incidents, last 90 days

  1. 2026-07-13: no record
  2. 2026-07-14: no record
  3. 2026-07-15: no record
  4. 2026-07-16: no record
  5. 2026-07-17: no record
  6. 2026-07-18: no record
  7. 2026-07-19: no record
  8. 2026-07-20: no record
  9. 2026-07-21: no record
  10. 2026-07-22: no record
  11. 2026-07-23: no record
  12. 2026-07-24: no record
  13. 2026-07-25: no record
  14. 2026-07-26: no record
  15. 2026-07-27: no record
  16. 2026-07-28: no record
  17. 2026-07-29: no record
  18. 2026-07-30: no record
  19. 2026-07-31: no record
  20. 2026-08-01: no record
  21. 2026-08-02: no record
  22. 2026-08-03: no record
  23. 2026-08-04: no record
  24. 2026-08-05: no record
  25. 2026-08-06: no record
  26. 2026-08-07: no record
  27. 2026-08-08: no record
  28. 2026-08-09: no record
  29. 2026-08-10: no record
  30. 2026-08-11: no record
  31. 2026-08-12: no record
  32. 2026-08-13: no record
  33. 2026-08-14: no record
  34. 2026-08-15: no record
  35. 2026-08-16: no record
  36. 2026-08-17: no record
  37. 2026-08-18: no record
  38. 2026-08-19: no record
  39. 2026-08-20: no record
  40. 2026-08-21: no record
  41. 2026-08-22: no record
  42. 2026-08-23: no record
  43. 2026-08-24: no record
  44. 2026-08-25: no record
  45. 2026-08-26: no record
  46. 2026-08-27: no record
  47. 2026-08-28: no record
  48. 2026-08-29: no record
  49. 2026-08-30: no record
  50. 2026-08-31: no record
  51. 2026-09-01: no record
  52. 2026-09-02: no record
  53. 2026-09-03: no record
  54. 2026-09-04: no record
  55. 2026-09-05: no record
  56. 2026-09-06: no record
  57. 2026-09-07: no record
  58. 2026-09-08: no record
  59. 2026-09-09: no record
  60. 2026-09-10: no record
  61. 2026-09-11: no record
  62. 2026-09-12: no record
  63. 2026-09-13: no record
  64. 2026-09-14: no record
  65. 2026-09-15: no record
  66. 2026-09-16: no record
  67. 2026-09-17: no record
  68. 2026-09-18: no record
  69. 2026-09-19: no record
  70. 2026-09-20: no record
  71. 2026-09-21: no record
  72. 2026-09-22: no record
  73. 2026-09-23: no record
  74. 2026-09-24: no record
  75. 2026-09-25: no record
  76. 2026-09-26: no record
  77. 2026-09-27: no record
  78. 2026-09-28: no record
  79. 2026-09-29: no record
  80. 2026-09-30: no record
  81. 2026-10-01: no record
  82. 2026-10-02: no record
  83. 2026-10-03: no record
  84. 2026-10-04: no record
  85. 2026-10-05: no record
  86. 2026-10-06: no record
  87. 2026-10-07: no record
  88. 2026-10-08: no record
  89. 2026-10-09: no record
  90. 2026-10-10: no incident reported
2026-07-130 of 1 days with an incidenttoday

Each bar is a day, coloured by the worst incident Amazon Web Services reported for AWS us-east-1 (N. Virginia). It is their incident record, not a measurement of uptime.

No finished incidents on record yet since 2026-10-10. UpButler keeps what Amazon Web Services publishes for 90 days from the day it starts tracking a service.

Get alerted when AWS us-east-1 (N. Virginia) goes down

No account. One email when Amazon Web Services reports an incident that affects AWS us-east-1 (N. Virginia), one when it is over. You confirm the address first, and every email has a one-click unsubscribe.

Or follow the RSS feed. On UpButler? Add Amazon Web Services as a dependency to route it to Slack, Teams or a webhook.

Status badge

Show AWS us-east-1 (N. Virginia)'s current status in a README or an internal wiki. It updates by itself.

AWS us-east-1 (N. Virginia) status badge

[![AWS us-east-1 (N. Virginia) status](https://upbutler.com/status/aws/badge.svg?component=us-east-1)](https://upbutler.com/status/aws/us-east-1)

Tell your outage from Amazon Web Services's

Declare that your project depends on AWS us-east-1 (N. Virginia). When one of your monitors fails while Amazon Web Services has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.

npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.

Start freeHow it works
upbutler.yaml
# upbutler.yaml
dependencies:
  - service: aws
    components: ["us-east-1"]
Ask before you retry
curl -s https://upbutler.com/status/aws/us-east-1/status.agent.json
status.agent.json (live)
{
  "schema": "upbutler.upstream-status/v1",
  "service": "aws",
  "component": {
    "slug": "us-east-1",
    "name": "AWS us-east-1 (N. Virginia)"
  },
  "verdict": "proceed",
  "status": "operational",
  "reason": "AWS us-east-1 (N. Virginia): no incidents reported",
  "retryAfterSec": null,
  "incident": null,
  "probe": null
}

Questions

Is AWS us-east-1 (N. Virginia) down right now?
No. As of 2026-10-10 07:16 UTC, AWS us-east-1 (N. Virginia) is up. This page reads the status again every 5 minutes.
Where does this status come from?
From Amazon Web Services's own AWS Health public events at https://health.aws.amazon.com/health/status. UpButler reads it once for everyone (not once per visitor) every 5 minutes with conditional requests, and shows it unchanged: incident titles and component names are Amazon Web Services's words. Their page covers more than this page shows; it is narrowed to the parts that concern AWS us-east-1 (N. Virginia).
Can I get an alert when AWS us-east-1 (N. Virginia) goes down?
Yes, without an account: enter your email on this page, confirm the link we send, and you get one email when Amazon Web Services reports an incident that affects AWS us-east-1 (N. Virginia) and one when it is over. There is also an RSS feed at https://upbutler.com/status/aws/feed.rss. Teams on UpButler can route the same alert to Slack, Teams or a webhook.
How can my agent or app check AWS us-east-1 (N. Virginia) status?
Fetch https://upbutler.com/status/aws/us-east-1/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"aws","component":"us-east-1"}, on https://upbutler.com/mcp/public.
How do I know whether an outage is mine or Amazon Web Services's?
Add "aws" to the dependencies of your UpButler workspace. When one of your monitors fails while Amazon Web Services has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

Also check

UpButler is not affiliated with Amazon Web Services. Status and incident text belong to Amazon Web Services and are read from their public status source; the probe result is UpButler's own measurement.