On October 20th, 2025, at 12:05 AM PT, Firstup platform infrastructure monitoring tools fired multiple alerts of failed system health checks. Firstup engineers immediately acknowledged the alerts and started investigating. At 12:17 AM PT, the investigations revealed that both Studio and Employee Experience on the Firstup US platform were not accessible because of an Amazon Web Services (AWS) service disruption in the N. Virginia (us-east-1) region. A platform incident was declared at 12:34 AM PT, and subsequently published on our Status Page at 12:44 AM PT.
Sev-1
All customers on the Firstup US platform attempting to access Studio or the Employee Experience were in scope of this incident.
Customers on the Firstup US platform primarily observed an error message while trying to log into or navigate within Studio or the Employee Experience. Some microservices on the Firstup US platform continued to exhibit degraded performance once access to Studio and Employee Experience was restored. These microservices included:
· Insights Reports
· Image/video uploading and processing
· User Sync
The root cause for this incident was determined to be an Amazon Web Services (AWS) service disruption in the N. Virginia (us-east-1) region. A summary of the incident on the AWS platform can be found here.
As AWS continued to work on the service disruption on their platform, access to Studio and Employee Experience on the Firstup US platform was restored by 2:37 AM PT, although some latency was still observed while navigating within these products. Some microservices on the Firstup US platform continued to experience intermittent degraded performance throughout the AWS incident, until it was fully resolved at 2:09 PM PT.
In an effort to make the Firstup platform more resilient to an incident on a dependent third-party vendor such as AWS, we have adjusted our systems’ Health-checks and Liveliness probes to better react to pod slow startups which were observed to cause crash loops during the incident.