Incidents reported on status page for Spencer https://status.spencer.co/en https://d1lppblt9t2x15.cloudfront.net/logos/0c79fc6e1a761226b107ab7121611662.png https://status.spencer.co/en en https://status.spencer.co/en/incident/1008723 Sat, 08 Aug 2026 00:07:00 -0000 https://status.spencer.co/en/incident/1008723#639d571044d2adf8b04c6fef3806847e31198706e13fdf6c00dd293d020919ce On 8 August 2026, between approximately 02:07 and 02:09 CEST, some Spencer API requests returned errors. The disruption was caused by a restart of our managed Azure database while Azure applied a database engine update. The database recovered automatically and all services resumed normal operation. We are reviewing additional measures to reduce the impact of future database maintenance. https://status.spencer.co/en/incident/965845 Thu, 16 Jul 2026 11:18:00 -0000 https://status.spencer.co/en/incident/965845#5bf5fbf27a91b3bd5b705faf985ec1d994d591daab6070af808274cd2d1b4a46 Connectivity has been restored. This is the official explanation we received from AWS: > _Between 09:45 and 13:18 UTC+2, we experienced increased 5xx errors for CloudFront customers utilizing VPC Origins connectivity. Our engineers were automatically engaged and immediately began investigating the root cause. By 11:57 UTC+2, we identified the root cause of the issue as an internal constraint on the fleet that manages connections to private VPC origins. When this constraint was reached, the system responsible for distributing routing configuration to our network processors failed to load the updated configuration data correctly, affecting routing of VPC Origin connections. At 12:52 UTC+2, we took multiple mitigation actions that led to to full recovery at 13:18 UTC+2. Now that the issue has been mitigated, customers who temporarily changed their origin type can safely revert these changes. Customers utilizing other origin types were not affected by this issue. The issue has been resolved and the service is operating normally._ https://status.spencer.co/en/incident/965845 Thu, 16 Jul 2026 08:00:00 -0000 https://status.spencer.co/en/incident/965845#0cb51bb7b92a167ea786974eb0f6861749e30f95016a506521e66fbe43e10b56 The Commslab application is currently unavailable due to a service outage at Amazon Web Services, our hosting provider. > _Starting at 12:45 AM PDT, we are experiencing increased 5xx errors for CloudFront customers utilizing VPC Origins connectivity._ See https://health.aws.amazon.com/health/status for updates from AWS themselves. Please note that our Commslab API is unaffected, so end users of the app are not affected.