# AWS Outage – Possible Service Disruptions A For your information post **URL:** \ **Category:** Integrator.io\ **Created:** [October 20, 2025, 8:17am UTC](https://connective.celigo.com/t/aws-outage-possible-service-disruptions-a-for-your-information-post/5725 "2025-10-20T08:17:18Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![nuriensing](https://sea1.discourse-cdn.com/flex001/user_avatar/connective.celigo.com/nuriensing/32/6918_2.png) [@nuriensing](https://connective.celigo.com/u/nuriensing)\ **Post date:** [October 20, 2025, 8:17am UTC](https://connective.celigo.com/t/aws-outage-possible-service-disruptions-a-for-your-information-post/5725/1 "2025-10-20T08:17:18Z")
A FYI: If you are experiencing any AWS errors it might be due to AWS: [https://health.aws.amazon.com/health/status](https://health.aws.amazon.com/health/status) **Increased Error Rates and Latencies** **Oct 20 12:51 AM PDT** We can confirm increased error rates and latencies for multiple AWS Services in the US-EAST-1 Region. This issue may also be affecting Case Creation through the AWS Support Center or the Support API. We are actively engaged and working to both mitigate the issue and understand root cause. We will provide an update in 45 minutes, or sooner if we have additional information to share. **Oct 20 12:11 AM PDT** We are investigating increased error rates and latencies for multiple AWS services in the US-EAST-1 Region. We will provide another update in the next 30-45 minutes. ---
**Author:** ![tylerlamparter](https://sea1.discourse-cdn.com/flex001/user_avatar/connective.celigo.com/tylerlamparter/32/9204_2.png) [@tylerlamparter](https://connective.celigo.com/u/tylerlamparter)\ **Post date:** [October 20, 2025, 3:56pm UTC](https://connective.celigo.com/t/aws-outage-possible-service-disruptions-a-for-your-information-post/5725/2 "2025-10-20T15:56:13Z")
This was in fact the issue this early morning. We also were unable to update the status page due to Atlassian also using AWS and we use the Atlassian status page service. It seems things are mostly back to normal, but provisioning of new worker resources is still taking a bit longer. ---
**Author:** ![nuriensing](https://sea1.discourse-cdn.com/flex001/user_avatar/connective.celigo.com/nuriensing/32/6918_2.png) [@nuriensing](https://connective.celigo.com/u/nuriensing)\ **Post date:** [October 21, 2025, 7:25am UTC](https://connective.celigo.com/t/aws-outage-possible-service-disruptions-a-for-your-information-post/5725/3 "2025-10-21T07:25:45Z")
AWS services are back online. I’ve shared more details on what happened and why so many tools went down in my latest blog post: [https://teknuro.com/major-aws-outage-why-your-favorite-tools-arent-working/](https://teknuro.com/major-aws-outage-why-your-favorite-tools-arent-working/) ---
**Author:** ![Kenneth\_Welling](https://avatars.discourse-cdn.com/v4/letter/k/a4c791/32.png) [@Kenneth\_Welling](https://connective.celigo.com/u/Kenneth_Welling)\ **Post date:** [October 21, 2025, 5:39pm UTC](https://connective.celigo.com/t/aws-outage-possible-service-disruptions-a-for-your-information-post/5725/4 "2025-10-21T17:39:48Z")
Did you need to do anything to get your flows working again? My last flow ran at 1:38PDT yesterday. I have refreshed the metadata on the connectors, but that hasn’t changed it. ---
**Author:** ![nuriensing](https://sea1.discourse-cdn.com/flex001/user_avatar/connective.celigo.com/nuriensing/32/6918_2.png) [@nuriensing](https://connective.celigo.com/u/nuriensing)\ **Post date:** [October 22, 2025, 8:26am UTC](https://connective.celigo.com/t/aws-outage-possible-service-disruptions-a-for-your-information-post/5725/5 "2025-10-22T08:26:04Z")
Do you have it scheduled, it should work automatically. Flows that are stuck in queue maybe cancel and rerun. ---
**Author:** ![Kenneth\_Welling](https://avatars.discourse-cdn.com/v4/letter/k/a4c791/32.png) [@Kenneth\_Welling](https://connective.celigo.com/u/Kenneth_Welling)\ **Post date:** [October 22, 2025, 2:41pm UTC](https://connective.celigo.com/t/aws-outage-possible-service-disruptions-a-for-your-information-post/5725/6 "2025-10-22T14:41:21Z")
I think that my Saleforce connector did not recover after the outage. Refreshing the credentials did not help. I got an error when I tried to replace it. Ultimately I had to create a new Salesforce connector, and then manually change each of my flows to use it.