Last checked from AWS Direct Connect official status page 4 min. 24 sec. ago
AWS Direct Connect Status
Cloud computing services for reliable, scalable, and inexpensive solutions.
Not working for you?
Is AWS Direct Connect down?
Minor AWS Direct Connect outage
Increased Error Rates
Not working for you?
StatusGator reports that Amazon Web Services is currently experiencing a partial outage. There have been 39 user-submitted reports of outages in the past 24 hours. There are confirmed issues with Bahrain - Amazon Detective, UAE - AWS AppSync, and Bahrain - AWS Ground Station and 271 other components, but all other components are operational. Increased Error Rates
AWS Direct Connect service health graph
Shows recent status reports over time, including possible and confirmed outages.
Shows recent status reports over time, including possible and confirmed outages.
This chart represents AWS Direct Connect service health over the last 24 hours, with data points collected every 15 minutes based on issue reports, page visits, and signal strength. Sign up for free to see more AWS Direct Connect status data.
24 hrs ending
●
Service up
●
Possible outage
●
Likely outage
AWS Direct Connect outage reports
Lists recent AWS Direct Connect incidents, including duration, acknowledgement status, and severity.
Lists recent AWS Direct Connect incidents, including duration, acknowledgement status, and severity.
2,195 outage reports in the last 24 hours
Recent community and social reports
Harjumaa, Estonia
"All models went missing from kiro"
• about 2 hours ago
São Paulo, Brazil
"Secrets manager is failing to list secrets in the AWS web console - host secretsmanager.us-east-1.amazonaws.com is not reachable."
• about 5 hours ago
Quebec, Canada
"Calling Bedrock API Error: The operation timed out."
• about 7 hours ago
Maryland, United States
"Timeout calling bedrock"
• about 8 hours ago
Capital Region, Denmark
Other
• about 10 hours ago
Budapest, Hungary
"Kiro is having trouble responding right now: 0: Failed to send the request: An unknown error occurred: InternalServerException 1: An unknown error occurred: InternalServerException 2: unhandled error (InternalServerException) 3: service error 4: unhandled error (InternalServerExcepti"
• about 10 hours ago
Budapest, Hungary
"Kiro is having trouble responding right now: 0: Failed to send the request: An unknown error occurred: InternalServerException 1: An unknown error occurred: InternalServerException 2: unhandled error (InternalServerException) 3: service error 4: unhandled error (InternalServerExcepti"
• about 10 hours ago
England, United Kingdom
Error message
• about 10 hours ago
United Kingdom
Error message
• about 11 hours ago
England, United Kingdom
Error message
• about 12 hours ago
Budapest, Hungary
"Kiro are you with me? Kiro is having trouble responding right now: 0: Failed to send the request: An unknown error occurred: InternalServerException 1: An unknown error occurred: InternalServerException 2: unhandled error (InternalServerException) 3: service error 4: unhandled error"
• about 13 hours ago
Belgrade, Serbia
"I always get this after I submitted a prompt: Kiro is having trouble responding right now: ... 5: Error { code: "InternalServerException", message: "Encountered an unexpected error when processing the request, please try again.", aws_request_id: "123..."}"
• about 14 hours ago
Tamil Nadu, India
"CloudWatch console doesn't show the list of log groups"
• about 19 hours ago
Madhya Pradesh, India
" Server Not Found Zen can’t connect to the server at kiro.dev. Did you mean to go to www.kiro.dev? What can you do about it? Try connecting on a different device. Check your modem or router. Disconnect and reconnect to Wi-Fi. Learn more… "
• about 21 hours ago
New York, United States
"Bedrock 503s for sonnet 5"
• 1 day ago
Budapest, Hungary
"503 Bedrock is unable to process your request"
• 1 day ago
Ontario, Canada
Other
• 1 day ago
California, United States
"503 Bedrock errors.."
• 1 day ago
Washington, United States
"API Error: 503 Failed to call LLM service: invoking wrapper: ServiceUnavailableException: Bedrock in unable to process your request. - thru Claude "
• 1 day ago
Illinois, United States
"503 "
• 1 day ago
Top reported outages
Error message
Service down
Connectivity issue
App not loading
Other
Server not responding
Sign in problem
Slow performance
Unable to download
Having a different problem?
Get notified about AWS Direct Connect outages
Stay updated with instant alerts for AWS Direct Connect outages by signing up now!
AWS Direct Connect outage map
Displays regions where users have recently reported issues. Map markers are based on user-submitted reports.
Displays regions where users have recently reported issues. Map markers are based on user-submitted reports.
Amazon Web Services outage map
AWS Direct Connect incidents history
Lists recent AWS Direct Connect incidents, including duration, acknowledgement status, and severity.
View more history
Lists recent AWS Direct Connect incidents, including duration, acknowledgement status, and severity.
| Incident Name | Duration | Started | Acknowledged | Severity |
|---|---|---|---|---|
|
Increased Error Rates
|
8d 3h 26m | Yes |
Warn
|
|
|
Increased Error Rates
|
119d 22h 42m | Yes |
Warn
|
|
|
CloudFront and Route53 service disruption
|
1h 4m | Yes, 13m delay |
Warn
|
|
|
Kiro service experiencing unexpected errors and outages
|
1h 6m | No |
Warn
|
|
|
Increased Error Rates and Latencies
|
121d 14h 13m | Yes |
Warn
|
|
|
Outage in N. Virginia, us-east-1
|
50m | Yes, 39m delay |
Warn
|
|
|
EC2 access and AWS console experiencing connectivity issues
|
3h 42m | No |
Warn
|
|
|
Problems signing in to the AWS Console.
|
50m | No |
Warn
|
|
|
Connectivity Issues
|
3h 30m | Yes |
Warn
|
Incident name
Increased Error Rates
Duration
8d 3h 26m
Start
Acknowledged
Yes
Severity
Warn
Incident name
Increased Error Rates
Duration
119d 22h 42m
Start
Acknowledged
Yes
Severity
Warn
Incident name
CloudFront and Route53 service disruption
Duration
1h 4m
Start
Acknowledged
Yes, 13m delay
Severity
Warn
Incident name
Kiro service experiencing unexpected errors and outages
Duration
1h 6m
Start
Acknowledged
No
Severity
Warn
Incident name
Increased Error Rates and Latencies
Duration
121d 14h 13m
Start
Acknowledged
Yes
Severity
Warn
Incident name
Outage in N. Virginia, us-east-1
Duration
50m
Start
Acknowledged
Yes, 39m delay
Severity
Warn
Incident name
EC2 access and AWS console experiencing connectivity issues
Duration
3h 42m
Start
Acknowledged
No
Severity
Warn
Incident name
Problems signing in to the AWS Console.
Duration
50m
Start
Acknowledged
No
Severity
Warn
Incident name
Connectivity Issues
Duration
3h 30m
Start
Acknowledged
Yes
Severity
Warn
AWS Direct Connect status history
Shows daily AWS Direct Connect status over the past 60 days, including uptime, warnings, and outage events.
Shows daily AWS Direct Connect status over the past 60 days, including uptime, warnings, and outage events.
July 01, 2026
Warning for 10 Hours and 8 Minutes
Warning for 10 Hours and 8 Minutes
July 02, 2026
Warning for 1 Day
Warning for 1 Day
July 03, 2026
Warning for 1 Day
Warning for 1 Day
July 04, 2026
Warning for 1 Day
Warning for 1 Day
July 05, 2026
Warning for 1 Day
Warning for 1 Day
July 06, 2026
Warning for 1 Day
Warning for 1 Day
July 07, 2026
Warning for 1 Day
Warning for 1 Day
July 08, 2026
Warning for 1 Day
Warning for 1 Day
July 09, 2026
Warning for 1 Day
Warning for 1 Day
July 10, 2026
Warning for 23 Hours and 40 Minutes
Warning for 23 Hours and 40 Minutes
60 days ago
Today
Up
Down
Warn
Maint
AWS Direct Connect status page accuracy
Learn more
Amazon Web Services status page accuracy rating
This rating evaluates how quickly Amazon Web Services acknowledges incidents, the consistency of updates, and whether reported issues align with actual service disruptions experienced by users.
A – Excellent
| Rating grade | Average delay |
|---|---|
|
A
Excellent
|
< 15 min |
|
B
Good
|
15 - 30 min |
|
C
Fair
|
30 - 120 min |
|
D
Poor
|
2 - 4 hrs |
|
F
Failing
|
>= 4 hrs |
Get notified about AWS Direct Connect outages
Stay updated with instant alerts for AWS Direct Connect outages by signing up now!
Looking for Downdetector AWS Direct Connect alerts?
| Features | StatusGator | Downdetector |
|---|---|---|
| Both official and crowdsourced updates for AWS Direct Connect outages. |
|
|
| More than 9,500 services monitored. |
|
|
| Proactive alerts on AWS Direct Connect status changes sent to your Slack, Microsoft Teams, and more. |
|
|
| Monitoring of both AWS Direct Connect and your own apps. |
|
|
| Granular monitoring of AWS Direct Connect components. |
|
|
Both official and crowdsourced updates for AWS Direct Connect outages.
StatusGator
Downdetector
More than 9,500 services monitored.
StatusGator
Downdetector
Proactive alerts on AWS Direct Connect status changes sent to your Slack, Microsoft Teams, and more.
StatusGator
Downdetector
Monitoring of both AWS Direct Connect and your own apps.
StatusGator
Downdetector
Granular monitoring of AWS Direct Connect components.
StatusGator
Downdetector
About our AWS Direct Connect status page integration
AWS Direct Connect (Cloud computing services for reliable, scalable, and inexpensive solutions) is a a Cloud Infrastructure solution that StatusGator has been monitoring since March 2015. Over the past over 11 years, we have collected data on on more than 2,184 outages that affected AWS Direct Connect users. When AWS Direct Connect publishes downtime on their status page, they do so across 5,839 components and 36 groups using 3 different statuses: up, warn, and down which we use to provide granular uptime metrics and notifications.
If you're wondering, "Is AWS Direct Connect down?", or need to know its current status, we've got you covered. Our platform tracks every reported outage, performance issue, and maintenance window to ensure you're informed. Whether AWS Direct Connect is experiencing a problem now or has recently resolved one, our detailed history keeps you updated.
More than 5,500 StatusGator users monitor AWS Direct Connect to get notified when it's down or has an outage. This makes it one of the most popular Cloud Infrastructure services monitored on our platform. We've sent more than 834,800 notifications to our users about AWS Direct Connect incidents, providing transparency and peace of mind. You can get alerts by signing up for a free StatusGator account.
-
Early Warning Signals
If we detect a potential AWS Direct Connect outage or other issue before it was reported on the official status page we will send an Early Warning Signal notification to StatusGator subscribers. We can often detect issues before they are officially acknowledged by the provider, giving you a head start on resolving any potential problems.
-
Down Notifications
If AWS Direct Connect is having system outages or experiencing other critical issues, red down notifications appear on the status page. In most cases, it means that core functions are not working properly, or there is some other serious customer-impacting event underway.
-
Warning Notifications
Warn notifications are used when AWS Direct Connect is undergoing a non-critical issue like minor service issues, performance degradation, non-core bugs, capacity issues, or problems affecting a small number of users.
-
Maintenance Notifications
AWS Direct Connect does not post separate notifications for planned maintenance work so we are unable to send notifications when maintenance windows begin. If you need AWS Direct Connect maintenance notifications, please email us.
-
Status Messages
When AWS Direct Connect posts issues on their status page, we collect the main headline message and include that brief information or overview in notifications to StatusGator subscribers.
-
Status Details
When AWS Direct Connect has outages or other service-impacting events on their status page, we pull down the detailed informational updates and include them in notifications. These messages often include the current details about how the problem is being mitigated, or when the next update will occur.
-
Component Status Filtering
Because AWS Direct Connect has several components, each with their individual statuses, StatusGator can differentiate the status of each component in our notifications to you whenever a particular component is down. This means, you can filter your status page notifications based on the services, regions, or components you utilize. This is an essential feature for complex services with many components or services spread out across many regions.