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, 29 Apr 2026 05:50:10 +0000 https://status.sparecores.com/#4752f61ad5469bd5d62123a5d782c3a9a4ebe117b26fe38da094611089af9f69 Database updates recovered https://status.sparecores.com/ Wed, 29 Apr 2026 02:08:25 +0000 https://status.sparecores.com/#4752f61ad5469bd5d62123a5d782c3a9a4ebe117b26fe38da094611089af9f69 Database updates went down https://status.sparecores.com/ Mon, 27 Apr 2026 19:58:21 +0000 https://status.sparecores.com/#f3b704316c9cf3d6738c13f1c84528b2ef3f214a829627a1d752494c58a9e57c Database updates recovered https://status.sparecores.com/ Mon, 27 Apr 2026 18:42:19 +0000 https://status.sparecores.com/#f3b704316c9cf3d6738c13f1c84528b2ef3f214a829627a1d752494c58a9e57c Database updates went down https://status.sparecores.com/ Mon, 27 Apr 2026 11:54:36 +0000 https://status.sparecores.com/#83d3a9464ec5c09ffbf573c0002121590287c9ceaa1f1646c8e1b8eb6ffd8aca Database updates recovered https://status.sparecores.com/ Mon, 27 Apr 2026 11:13:10 +0000 https://status.sparecores.com/#83d3a9464ec5c09ffbf573c0002121590287c9ceaa1f1646c8e1b8eb6ffd8aca Database updates went down https://status.sparecores.com/ Mon, 27 Apr 2026 07:09:56 +0000 https://status.sparecores.com/#491ba820ef88f48ea3a98858c26ce489892fdfeb32dbae8aeb9dd6eeed734405 Database updates recovered https://status.sparecores.com/ Mon, 27 Apr 2026 06:12:37 +0000 https://status.sparecores.com/#491ba820ef88f48ea3a98858c26ce489892fdfeb32dbae8aeb9dd6eeed734405 Database updates went down https://status.sparecores.com/ Mon, 20 Apr 2026 12:04:22 +0000 https://status.sparecores.com/#cf56a1c1e99e1f0c9f901b114d9b829b13ddbda669c6b30a3c0d1a5c2bd0a0b1 Database updates recovered https://status.sparecores.com/ Mon, 20 Apr 2026 10:57:09 +0000 https://status.sparecores.com/#cf56a1c1e99e1f0c9f901b114d9b829b13ddbda669c6b30a3c0d1a5c2bd0a0b1 Database updates went down https://status.sparecores.com/ Wed, 15 Apr 2026 15:41:35 +0000 https://status.sparecores.com/#6f461af37327e9609117858f34dcfa31cb6148bde263eae62b96cf2d3d961afa Database updates recovered https://status.sparecores.com/ Wed, 15 Apr 2026 13:42:12 +0000 https://status.sparecores.com/#6f461af37327e9609117858f34dcfa31cb6148bde263eae62b96cf2d3d961afa Database updates went down https://status.sparecores.com/ Tue, 14 Apr 2026 23:10:54 +0000 https://status.sparecores.com/#af0e51b5913cdc52a6036cd6eed71d9861740ab9548347063236113bac48b397 Database updates recovered https://status.sparecores.com/ Tue, 14 Apr 2026 22:37:51 +0000 https://status.sparecores.com/#af0e51b5913cdc52a6036cd6eed71d9861740ab9548347063236113bac48b397 Database updates went down https://status.sparecores.com/ Mon, 13 Apr 2026 03:38:34 +0000 https://status.sparecores.com/#822e759f4f58e85ce8d93dbbdda29e183923dd9cb4891e534a0063064406a6c3 Database updates recovered https://status.sparecores.com/ Mon, 13 Apr 2026 03:06:56 +0000 https://status.sparecores.com/#822e759f4f58e85ce8d93dbbdda29e183923dd9cb4891e534a0063064406a6c3 Database updates went down https://status.sparecores.com/ Sun, 12 Apr 2026 16:30:58 +0000 https://status.sparecores.com/#c1bdb30b5c9c32f136c11a83c4514da956b83596ab94ff0c89c24cceade3b196 Database updates recovered https://status.sparecores.com/ Sun, 12 Apr 2026 15:41:09 +0000 https://status.sparecores.com/#c1bdb30b5c9c32f136c11a83c4514da956b83596ab94ff0c89c24cceade3b196 Database updates went down https://status.sparecores.com/ Sun, 12 Apr 2026 03:14:02 +0000 https://status.sparecores.com/#9cdff2b1eafc09c5466dacab80837c1078a4be88aff6f487f9197e14b6f264ca Database updates recovered https://status.sparecores.com/ Sun, 12 Apr 2026 02:36:05 +0000 https://status.sparecores.com/#9cdff2b1eafc09c5466dacab80837c1078a4be88aff6f487f9197e14b6f264ca Database updates went down https://status.sparecores.com/ Fri, 10 Apr 2026 23:09:42 +0000 https://status.sparecores.com/#e2485f72e972091fbc6cceae4f5f6940b1a3cd84a490368b15aee15543d5de4e Database updates recovered https://status.sparecores.com/ Fri, 10 Apr 2026 22:27:50 +0000 https://status.sparecores.com/#e2485f72e972091fbc6cceae4f5f6940b1a3cd84a490368b15aee15543d5de4e Database updates went down https://status.sparecores.com/ Thu, 09 Apr 2026 04:55:04 +0000 https://status.sparecores.com/#d8678788254b506e07d87e58d3ba38044f597d0cf9a49dc0bb692829acecb532 Database updates recovered https://status.sparecores.com/ Thu, 09 Apr 2026 04:13:32 +0000 https://status.sparecores.com/#d8678788254b506e07d87e58d3ba38044f597d0cf9a49dc0bb692829acecb532 Database updates went down https://status.sparecores.com/ Wed, 08 Apr 2026 16:40:29 +0000 https://status.sparecores.com/#d89cab4a7344db8e28200e5a73711f869829f5c16becb12b533fc0a3b524784d Database updates recovered https://status.sparecores.com/ Wed, 08 Apr 2026 14:27:51 +0000 https://status.sparecores.com/#d89cab4a7344db8e28200e5a73711f869829f5c16becb12b533fc0a3b524784d Database updates went down https://status.sparecores.com/ Mon, 06 Apr 2026 03:44:16 +0000 https://status.sparecores.com/#391bc21930ad3c187e2ca90abe5c37a6f0bf4012083a8a8cd231443149aaa988 Database updates recovered https://status.sparecores.com/ Mon, 06 Apr 2026 03:12:44 +0000 https://status.sparecores.com/#391bc21930ad3c187e2ca90abe5c37a6f0bf4012083a8a8cd231443149aaa988 Database updates went down https://status.sparecores.com/ Sun, 05 Apr 2026 18:53:52 +0000 https://status.sparecores.com/#c9caf1044fec0c0878fdb389871ef999083ae29dd51192ebebdb92231ae71792 Database updates recovered https://status.sparecores.com/ Sun, 05 Apr 2026 16:56:21 +0000 https://status.sparecores.com/#c9caf1044fec0c0878fdb389871ef999083ae29dd51192ebebdb92231ae71792 Database updates went down https://status.sparecores.com/ Sun, 05 Apr 2026 09:48:42 +0000 https://status.sparecores.com/#2aac59adf65650ba4b9440fdd90be37572f73e64fadf7e07e908d4dd7695d9d6 Database updates recovered https://status.sparecores.com/ Sun, 05 Apr 2026 09:41:28 +0000 https://status.sparecores.com/#2aac59adf65650ba4b9440fdd90be37572f73e64fadf7e07e908d4dd7695d9d6 Database updates went down https://status.sparecores.com/incident/862381 Wed, 01 Apr 2026 07:58:00 -0000 https://status.sparecores.com/incident/862381#a7110f0ed9fa647a6143816133e255af0ea21e7a9f4b91af8cbdb1e1df85dffa The `me-south-1` AWS region became unreachable and failed the related ETL pipeline. We have applied a fix to mark a region as inactive in such case and not block the rest of the ETL process. https://status.sparecores.com/incident/862381 Wed, 01 Apr 2026 04:31:00 -0000 https://status.sparecores.com/incident/862381#605795abe22480e29f0c5e2db0f6d12f395e2a1a276853e2f9b04adfc27767e1 Recent ETL jobs have been failing. https://status.sparecores.com/incident/862376 Wed, 25 Mar 2026 10:32:00 -0000 https://status.sparecores.com/incident/862376#1c592779b777f69682927f64ca332acd5453038248b04a4787c3862a0571c00f ETL pipeline is back to normal, and we are working on mitigating the risk of similar failures in the future. https://status.sparecores.com/incident/862376 Wed, 25 Mar 2026 07:18:00 -0000 https://status.sparecores.com/incident/862376#ef309b372755bbf2996be6fecf3aa41836f78989c4819e62154d45d331d7c979 A new cloud region was discovered at a cloud vendor with undocumented fields, which resulted in failing our ETL processes. We are rolling out a fix in the next hour or so. https://status.sparecores.com/incident/862376 Wed, 25 Mar 2026 03:12:00 -0000 https://status.sparecores.com/incident/862376#039400979a01df847aff22a4b387385c9e52e83869c094202d5435e04ed37b39 Recent ETL jobs have been failing. https://status.sparecores.com/incident/855819 Mon, 23 Mar 2026 23:38:00 -0000 https://status.sparecores.com/incident/855819#334cf904f6ef7727a8fe581257ca7ee98e208694477d22db82f648cac6dbe7b2 There was a dependency resolution error in our Infrastructure-as-Code implementation that resulted in temporarily TLS negotiations in some requests. All these errors are now resolved and the site is back to normal. https://status.sparecores.com/incident/855819 Mon, 23 Mar 2026 22:58:00 -0000 https://status.sparecores.com/incident/855819#529873874f3ea064a4f13eb5547e1841b45207db58fa6f82006fd191fa3b0e03 The load balancer in front of our web servers is being migrated, resulting in brief downtime. We will report back once the migration is ready. 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.