Incidents reported on status page for Spare Cores https://status.sparecores.com/ https://d1lppblt9t2x15.cloudfront.net/logos/37102ea6628d4ffd0a3f94dfe076a8ae.png https://status.sparecores.com/ en https://status.sparecores.com/ Wed, 18 Mar 2026 14:15:23 +0000 https://status.sparecores.com/#51d6348bf4161f7b733f31ede5eff57014c31ebaed5f39b407df78875843c4d3 API recovered https://status.sparecores.com/ Wed, 18 Mar 2026 14:09:26 +0000 https://status.sparecores.com/#51d6348bf4161f7b733f31ede5eff57014c31ebaed5f39b407df78875843c4d3 API went down https://status.sparecores.com/ Mon, 16 Mar 2026 19:36:27 +0000 https://status.sparecores.com/#7adfca6f1407b559901457917b4001f76ef14957890a3045f6422ac56dddbde0 API recovered https://status.sparecores.com/ Mon, 16 Mar 2026 19:30:32 +0000 https://status.sparecores.com/#7adfca6f1407b559901457917b4001f76ef14957890a3045f6422ac56dddbde0 API went down https://status.sparecores.com/ Thu, 12 Mar 2026 09:18:26 +0000 https://status.sparecores.com/#5f1a7a068c1508155dcc502871e844492b09df8aff42f67f9cb44739c8f1daaa API recovered https://status.sparecores.com/ Thu, 12 Mar 2026 09:09:29 +0000 https://status.sparecores.com/#5f1a7a068c1508155dcc502871e844492b09df8aff42f67f9cb44739c8f1daaa API went down https://status.sparecores.com/ Mon, 09 Mar 2026 11:00:31 +0000 https://status.sparecores.com/#6f3b16370d67e61353975266632bb3166e2a206961ec93ec8aca3ca23179cc92 API recovered https://status.sparecores.com/ Mon, 09 Mar 2026 10:54:27 +0000 https://status.sparecores.com/#6f3b16370d67e61353975266632bb3166e2a206961ec93ec8aca3ca23179cc92 API went down https://status.sparecores.com/ Sun, 08 Mar 2026 02:30:20 +0000 https://status.sparecores.com/#9053ae15837b04239cb0ff132ad950b36efde163ad10cf75e27464bde6d52158 API recovered https://status.sparecores.com/ Sun, 08 Mar 2026 02:24:33 +0000 https://status.sparecores.com/#9053ae15837b04239cb0ff132ad950b36efde163ad10cf75e27464bde6d52158 API went down https://status.sparecores.com/ Wed, 04 Mar 2026 14:21:23 +0000 https://status.sparecores.com/#b6f192db693169f2e5ee33079881b8f580488c42f5ed9f2b2ccdf6ccd084e106 API recovered https://status.sparecores.com/ Wed, 04 Mar 2026 14:12:28 +0000 https://status.sparecores.com/#b6f192db693169f2e5ee33079881b8f580488c42f5ed9f2b2ccdf6ccd084e106 API went down https://status.sparecores.com/ Wed, 04 Mar 2026 10:57:38 +0000 https://status.sparecores.com/#2f6f08f4734f8885195b186b1afc21bf2a9d6403be5f194e228fdf5922aac535 API recovered https://status.sparecores.com/ Wed, 04 Mar 2026 10:51:28 +0000 https://status.sparecores.com/#2f6f08f4734f8885195b186b1afc21bf2a9d6403be5f194e228fdf5922aac535 API went down https://status.sparecores.com/ Tue, 03 Mar 2026 01:55:45 +0000 https://status.sparecores.com/#9a5193d649574b01b617d51c632fcfa80e40522bbe213828253337a302dec1f5 Crawler recovered https://status.sparecores.com/ Tue, 03 Mar 2026 01:24:08 +0000 https://status.sparecores.com/#9a5193d649574b01b617d51c632fcfa80e40522bbe213828253337a302dec1f5 Crawler went down https://status.sparecores.com/ Mon, 02 Mar 2026 16:28:21 +0000 https://status.sparecores.com/#d9f3eb5776b34a02a86f745486551ff3f5c383124c1b59d87f3227cf902df907 Hosting recovered https://status.sparecores.com/ Mon, 02 Mar 2026 16:22:24 +0000 https://status.sparecores.com/#d9f3eb5776b34a02a86f745486551ff3f5c383124c1b59d87f3227cf902df907 Hosting went down https://status.sparecores.com/incident/820144 Fri, 06 Feb 2026 21:42:00 -0000 https://status.sparecores.com/incident/820144#77fc9c1833cb4431b13d75c1e87590eeb9204d903c576d0bbb364342b4c1e4b0 Final fix deployed, and the Crawler is running at https://github.com/SpareCores/sc-data-dumps/actions/runs/21766478971/job/62803492787 https://status.sparecores.com/incident/820144 Fri, 06 Feb 2026 20:43:00 -0000 https://status.sparecores.com/incident/820144#694e1806f6369a7335554e58174e3d095dc31c29d271d47b1fe1acc13d713e61 The proposed fix did not fully resolve the situation, so we continue investigating the situation. https://status.sparecores.com/incident/820144 Fri, 06 Feb 2026 15:39:00 -0000 https://status.sparecores.com/incident/820144#0a38f30fabaefc46552bd2bad37570d9274ffd47ee8d767152cbd2e11a1d46f2 A fix for the removed Azure client is currently being tested, upstream bugreport opened. https://status.sparecores.com/incident/820144 Fri, 06 Feb 2026 15:21:00 -0000 https://status.sparecores.com/incident/820144#5d3397d724c099d2bea9a0c8a81f5081d3f2105ebdd7480d6a6f413535caab3a We have identified the issue: the Azure Python SDK has been updated and the `SubscriptionClient` we use to list the available regions has been removed from the azure-mgmt-resource package. We are investigating what exactly happened and how to overcome the issue -- preferably without pinning the package to an older version. https://status.sparecores.com/incident/820144 Fri, 06 Feb 2026 10:38:00 -0000 https://status.sparecores.com/incident/820144#8e0f92e7006ff27085b152da9d6c1199870e26d1f46dabdd559d7e1ed4741839 The Crawler's hourly and more frequent runs have been failing for 2 hours, potentially resulting in outdated data. https://status.sparecores.com/incident/810477 Fri, 23 Jan 2026 16:30:00 -0000 https://status.sparecores.com/incident/810477#99ac1695703be0b3b9582e16c9ed5ac0d09a0a6c359980db0b7af956c1b903d5 Migration complete, data is flowing to the new repo 🎉 S3 location was not affected. https://status.sparecores.com/incident/810477 Fri, 23 Jan 2026 16:03:00 -0000 https://status.sparecores.com/incident/810477#b1219b249f3e1a230c955e23987949492213c9bcefd9f6d01b366eac434421d0 We are migrating the scheduled Crawler runs from the sc-data repository to a new location (sc-data-dumps), which shouldn't take more than an hour -- I'll report back. In the meantime, S3 dumps should be up-to-date, but changelog might be missed for a few runs along with the heartbeat signals sent to our statuspage. https://status.sparecores.com/incident/436319 Sat, 28 Sep 2024 20:45:00 -0000 https://status.sparecores.com/incident/436319#c7f93ea6456f494585970306662028cec21447ebe326b69ebde4f011014a2b97 The sparecores.com domain was removed from Amplify, and added to the directly managed Cloudfront distribution, CNAME update in progress. https://status.sparecores.com/incident/436319 Sat, 28 Sep 2024 20:39:00 -0000 https://status.sparecores.com/incident/436319#6373f43eea5e1751a31b76995fc78859497d8e53e9054b9f0dc976fbc92e77fc We decided to move our hosting (Angular SSR) from serverless Edge Lambda provided by AWS Amplify to traditional Express hosting behind a CDN, and the migration required to take off Amplify before the CNAME records change due a technical limitation at AWS. https://status.sparecores.com/incident/424671 Thu, 05 Sep 2024 13:11:00 -0000 https://status.sparecores.com/incident/424671#1668480f595e728ac24f14fb80675cfd7c56459054b0b1b7fd3bff12ec028124 The static and SSR components of our homepage have been migrated away from Netlify, and the service is back to normal. https://status.sparecores.com/incident/424671 Thu, 05 Sep 2024 13:03:00 -0000 https://status.sparecores.com/incident/424671#a3988ad596530808f80bb8acdfd44de18d9ff2a9ab5542932e3d349646de5842 We are investigating migration to another hosting provider. https://status.sparecores.com/incident/424671 Thu, 05 Sep 2024 12:55:00 -0000 https://status.sparecores.com/incident/424671#53023454cf9950adf7ec86501469e3fd57cca637e2b481e73ed3ca0671846e50 Netlify misunderstood a support ticket that we had opened regarding SSR edge function usage, and they took down the site without notice, as they handled our support ticket as "a report for problematic website hosted on our service". https://status.sparecores.com/incident/416964 Wed, 21 Aug 2024 09:39:00 -0000 https://status.sparecores.com/incident/416964#d9369d9235114339fc1dd255c67ba1014080ee43e2f996ce9355cd44c0897548 We have upgraded the cluster to use larger instances to support the increased memory requirements of the Keeper. https://status.sparecores.com/incident/416964 Wed, 21 Aug 2024 07:21:00 -0000 https://status.sparecores.com/incident/416964#7dba8c0e97b62bf940b8fbd9d7ea2a36a4c483e0ed99f8e7c7058bf60c89206c We have identified the root cause (more memory required for Duck DB compared to SQLite), and currently testing a fix offline. https://status.sparecores.com/incident/416964 Wed, 21 Aug 2024 04:35:00 -0000 https://status.sparecores.com/incident/416964#d9f1faf4248b55e41fbe8873679f959489008f0a9c6bf7a720440381252179d4 Due to a recent update (switching from using SQLite to Duck DB), the production Keeper API endpoint is struggling with the relatively small containerized environment.