All Systems Operational

Updated a few seconds ago

Back to current status

Status History



September 2024

Slow page loads: Google Chrome

September 25, 2024 3:05PM UTC

Incident Status

Degraded Performance


Components

Admin Console Services, Analytics and Dashboard Services, Administrative API Services, Authentication API Services, Identity Store Services, Customer Login, Registration, and My Account Services, Email and SMS Notification Services, Website & Trial Signup Service


Locations

Ohio (us-east-2), Ireland (eu-west-1), Singapore (ap-southeast-1), Oregon (us-west-2), Sydney (ap-southeast-2), Frankfurt (eu-central-1), Montreal (ca-central-1), London (eu-west-2), Sao Paulo (sa-east-1), Cape Town (af-south-1), Hong Kong (ap-east-1), Bahrain (me-south-1), Seoul (ap-northeast-2)




September 24, 2024 1:47PM UTC
[Investigating] For customers that are using Google Analytics and Tag Manager - we're investigating an issue where Google is causing unusually long response times in page rendering for Google Chrome. We will provide more information shortly.

September 24, 2024 3:27PM UTC
[Identified] We have identified a hanging import issue caused by Google Chrome v129. A hotfix is being developed by Strivacity to circumvent the Google Chrome bug ahead of Google resolving the issue. Until our patch is released, we suggest disabling Google Tag Manager/Google Analytics in the Strivacity Admin Console if you have it enabled.

September 24, 2024 3:29PM UTC
[Monitoring] We have identified a hanging import issue caused by Google Chrome v129. A hotfix is being developed by Strivacity to circumvent the Google Chrome bug ahead of Google resolving the issue. Until our patch is released, we suggest disabling Google Tag Manager/Google Analytics in the Strivacity Admin Console if you have it enabled.

September 25, 2024 3:05PM UTC
[Resolved] Our hotfix has been released, resolving the issue.

June 2024

Spot Instance Interruptions

June 6, 2024 1:00PM UTC

Spot Instance Interruptions Partial Service Disruption

Incident Status

Partial Service Disruption


Components

Admin Console Services, Analytics and Dashboard Services, Administrative API Services, Authentication API Services, Identity Store Services, Customer Login, Registration, and My Account Services, Email and SMS Notification Services


Locations

Ohio (us-east-2)




June 6, 2024 12:00PM UTC
[Investigating] Strivacity uses spot instances for worker nodes. Strivacity’s AWS alert manager notified internal teams automatically at the beginning of the unexpected event and responsible teams have started investigating the issue. Due to the massive number of pod rescheduling events triggered by the spot instance terminations, the Kubernetes master nodes became overloaded. The Kubernetes master nodes are responsible for scheduling pods across available worker nodes in the cluster. An overloaded master can lead to delays or failures in pod scheduling. During that period some of the underlying services (eg. account storage) were not available causing inoperable logins.

June 6, 2024 1:00PM UTC
[Resolved] The system was self-healing, but it took longer to recover on its own with the original configuration. Strivacity increased the size (CPU and Memory) of the Kubernetes master nodes, to handle these rescheduling requests caused by AWS spot terminations, much faster, and more reliably to prevent similar issues in the future.

April 2024

AWS/US-EAST-2 disruption

April 20, 2024 1:45AM UTC

AWS/US-EAST-2 disruptionPartial Service Disruption

Incident Status

Partial Service Disruption


Components

Admin Console Services, Analytics and Dashboard Services, Administrative API Services, Authentication API Services, Identity Store Services, Customer Login, Registration, and My Account Services, Email and SMS Notification Services


Locations

Ohio (us-east-2)




April 19, 2024 11:48PM UTC
[Monitoring] AWS Region US-EAST-2 is experiencing a service disruption, which has had an impact on new instance launches and terminations: Apr 19 3:28 PM PDT Between 11:15 AM and 3:05 PM PDT, we experienced increased delays in EC2 instance and Status Check metrics, including DescribeInstances and DescribeInstanceStatus API results, in a single Availability Zone (use2-az1) in the US-EAST-2 Region. This issue affected the DescribeInstances, DescribeInstanceStatus APIs and new instance launches/terminations. We also experienced capacity errors during this period. Other AWS Services that invoke these APIs were also affected; some examples include creating new DataSync Tasks that copy data to/from the US-EAST-2 Region, Cluster creates within the Elastic Kubernetes Service, and EBS Volume attach and detach requests. The issue is resolved and the service is operating normally.

April 20, 2024 1:45AM UTC
[Resolved] Amazon has marked the incident resolved. Our services are fully operational.

June 2023

Potential delay in SMS delivery

June 8, 2023 5:23PM UTC

Incident Status

Operational


Components

Admin Console Services, Analytics and Dashboard Services, Administrative API Services, Authentication API Services, Identity Store Services, Customer Login, Registration, and My Account Services, Email and SMS Notification Services, Website & Trial Signup Service


Locations

Ohio (us-east-2), Ireland (eu-west-1), Singapore (ap-southeast-1), Oregon (us-west-2), Sydney (ap-southeast-2), Frankfurt (eu-central-1), Montreal (ca-central-1), London (eu-west-2), Sao Paulo (sa-east-1), Cape Town (af-south-1), Hong Kong (ap-east-1), Bahrain (me-south-1), Seoul (ap-northeast-2)




June 8, 2023 4:53PM UTC
[Monitoring] A service provider is addressing an issue involving potentially delayed delivery of SMS messages.

June 8, 2023 5:23PM UTC
[Resolved] The service provider has resolved the issue.

August 2022

Email Interruption

August 9, 2022 12:33PM UTC

Email InterruptionPartial Service Disruption

Incident Status

Partial Service Disruption


Components

Email and SMS Notification Services


Locations

Ohio (us-east-2)




August 9, 2022 12:15PM UTC
[Investigating] At 8:15 AM Eastern (EDT), we discovered that emails were not being sent through us-east-2. This impacted any emails sent through Strivacity including but not limited to Welcome emails, Password Reset emails, and/or Multi-Factor Authentication (MFA) emails. This only impacted instances in the us-east-2 region.

August 9, 2022 12:33PM UTC
[Resolved] The issue has been identified and resolved the issue at 8:33 AM Eastern (EDT).

July 2022

AWS/us-east-2 Disruption

July 28, 2022 8:38PM UTC

AWS/us-east-2 DisruptionPartial Service Disruption

Incident Status

Partial Service Disruption


Components

Admin Console Services, Analytics and Dashboard Services, Administrative API Services, Authentication API Services, Identity Store Services, Customer Login, Registration, and My Account Services, Email and SMS Notification Services


Locations

Ohio (us-east-2)




July 28, 2022 5:40PM UTC
[Identified] AWS Region US-EAST-2 is experiencing a service disruption: We can confirm that some instances within a single Availability Zone (USE2-AZ1) in the US-EAST-2 Region have experienced a loss of power. The loss of power is affecting part of a single data center within the affected Availability Zone. Power has been restored to the affected facility and at this stage the majority of the affected EC2 instances have recovered. We expect to recover the vast majority of EC2 instances within the next hour. For customers that need immediate recovery, we recommend failing away from the affected Availability Zone as other Availability Zones are not affected by this issue.

July 28, 2022 6:00PM UTC
[Monitoring] AWS Region US-EAST-2 is experiencing a service disruption, but underlying instances are coming back online: [10:49 AM PDT] We continue to see recovery of EC2 instances that were affected by the loss of power in a single Availability Zone in the US-EAST-2 Region. At this stage, the vast majority of affected EC2 instances and EBS volumes have returned to a healthy state and we continue to work on the remaining EC2 instances and EBS volumes. Elastic Load Balancing has shifted traffic away from the affected Availability Zone. Single-AZ RDS databases were also affected and will recover as the underlying EC2 instance recovers. Multi-AZ RDS databases would have mitigated impact by failing away from the affected Availability Zone. While the vast majority of Lambda functions continue operating normally, some functions are experiencing invocation failures and latencies, but we expect this to improve over the next 30 minutes. Power has been restored to all affected resources and remains stable. We expect the recovery of EC2 instances and EBS volumes to continue to improve over the next 45 minutes. For customers that need immediate recovery, we recommend failing away from the affected Availability Zone as other Availability Zones are not affected by this issue.

July 28, 2022 8:38PM UTC
[Resolved] [12:00 PM PDT] Starting at 9:57 AM PDT some EC2 instances and EBS volumes experienced a loss of power within a single Availability Zone in the US-EAST-2 Region. Power was restored at 10:19 AM PDT and EC2 instances and EBS volumes began to recover. By 10:23 AM PDT, the vast majority of EC2 instances and EBS volumes has fully recovered and by 11:37 AM PDT, all but a very small number of EC2 instances and EBS volumes had recovered. Elastic Load Balancing shifted traffic away from the affected Availability Zone, which has now been shifted back. RDS impact for single-AZ databases, which have also been recovered. Other services (tagged below) saw impact during the event, but most have fully recovered. Those that are still seeing impact, will provide updates via the Personal Health Dashboard as they work towards full recovery. The issue has been resolved and the service is operating normally.

December 2021

AWS Outage affecting connectivity issues

December 15, 2021 4:18PM UTC

Incident Status

Service Disruption


Components

Admin Console Services, Analytics and Dashboard Services, Administrative API Services, Authentication API Services, Identity Store Services, Email and SMS Notification Services


Locations

Oregon (us-west-2)




December 15, 2021 3:57PM UTC
[Investigating] An active AWS outage is having an impact on network connectivity to Fusion services

December 15, 2021 4:00PM UTC
[Investigating] Services are operational. Timeouts may be encountered. Services are running, but possibly inaccessible

December 15, 2021 4:07PM UTC
[Monitoring] AWS Internet Connectivity is being investigated in California and Oregon regions. We're seeing improved response times, and are actively monitoring the situation

December 15, 2021 4:12PM UTC
[Monitoring] Testing of email services has been successful

December 15, 2021 4:16PM UTC
[Monitoring] Performance is improving. AWS outage resolved in California region.

December 15, 2021 4:18PM UTC
[Resolved] AWS outage resolved in Oregon





Back to current status