Status updates | Spare Cores Incidents and maintenance reported on status page for Spare Cores https://status.sparecores.com/ https://d1lppblt9t2x15.cloudfront.net/logos/37102ea6628d4ffd0a3f94dfe076a8ae.png Status updates | Spare Cores https://status.sparecores.com/ en API and homepage unreachable https://status.sparecores.com/incident/1083756 Wed, 07 Oct 2026 06:01:00 -0000 https://status.sparecores.com/incident/1083756#2ef6c6ed233e3f44a97996c87c5c607d2a548e8b6506005b4946d2c96fdd0d6c Incident Certificate renewed and all affected services are back to normal operations. API and homepage unreachable https://status.sparecores.com/incident/1083756 Wed, 07 Oct 2026 05:35:00 -0000 https://status.sparecores.com/incident/1083756#3149f8f722b6d786a3465cd4f8c0198bc51b176d3b1ffe541f04e87fd634b6d0 Incident We were notified of the outage and identified the root cause: our shared ALB certificate expired and couldn't be automatically renewed. We are working on the related fix and will report back in 30 minutes. API and homepage unreachable https://status.sparecores.com/incident/1083756 Wed, 07 Oct 2026 03:22:00 -0000 https://status.sparecores.com/incident/1083756#d08b4b4154f6bd45d3ee977c431f2c6f432d474cfe02c57668326954c5784f6e Incident Our Navigator API and website are unreachable for most customers as per our automated monitoring system. Broken website https://status.sparecores.com/incident/1072521 Wed, 23 Sep 2026 23:42:00 -0000 https://status.sparecores.com/incident/1072521#7e2d6f11c45c45a197fff81c3d6473ec36884e6f5ca59c3793a035a3700f1550 Incident The fix is deployed, and everything is back to normal. Broken website https://status.sparecores.com/incident/1072521 Wed, 23 Sep 2026 23:27:00 -0000 https://status.sparecores.com/incident/1072521#e68186aad94679774bcb8a374194867586092b3ccb732ac641cc346daa7b083f Incident We have identified the issue, which was introduced in the process of sanitizing JS and CSS files from sourcemap references. Fix is on the way. Broken website https://status.sparecores.com/incident/1072521 Wed, 23 Sep 2026 23:14:00 -0000 https://status.sparecores.com/incident/1072521#b58fa737aa4dba57ea55cf7778e394789e8855db527dff79ab6fb028fb68ef11 Incident The sparecores.com website has a broken JS file resulting in failing interactivity. Delayed data ingest https://status.sparecores.com/incident/998658 Thu, 06 Aug 2026 23:44:00 -0000 https://status.sparecores.com/incident/998658#97570682b0d1306d1335dfc9467906ae2a33a0ee32c28a71c069b4555798cfeb Incident Data ingest is back to normal since GitHub Action outage is resolved. Delayed data ingest https://status.sparecores.com/incident/998658 Thu, 06 Aug 2026 22:55:00 -0000 https://status.sparecores.com/incident/998658#723742c97496dbba47ad2742b3a1e625db9fd33b148174d1935d422c6e00aa40 Incident GitHub Actions is getting back online, and our crawler jobs also started to run, so data delays should be fixed within the hour. Delayed data ingest https://status.sparecores.com/incident/998658 Thu, 06 Aug 2026 16:50:00 -0000 https://status.sparecores.com/incident/998658#96bfec8775b958bdd09f8bc4b2c5aa1d6651b0acfc9cae12af25aa39a1194542 Incident GitHub Actions have been experiencing a major outage affecting our public data ingests: <https://www.githubstatus.com/incidents/qcvjkzcs7j74> Delayed data ingest https://status.sparecores.com/incident/862381 Wed, 01 Apr 2026 07:58:00 -0000 https://status.sparecores.com/incident/862381#a7110f0ed9fa647a6143816133e255af0ea21e7a9f4b91af8cbdb1e1df85dffa Incident 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. Delayed data ingest https://status.sparecores.com/incident/862381 Wed, 01 Apr 2026 04:31:00 -0000 https://status.sparecores.com/incident/862381#605795abe22480e29f0c5e2db0f6d12f395e2a1a276853e2f9b04adfc27767e1 Incident Recent ETL jobs have been failing. Delayed data ingest https://status.sparecores.com/incident/862376 Wed, 25 Mar 2026 10:32:00 -0000 https://status.sparecores.com/incident/862376#1c592779b777f69682927f64ca332acd5453038248b04a4787c3862a0571c00f Incident ETL pipeline is back to normal, and we are working on mitigating the risk of similar failures in the future. Delayed data ingest https://status.sparecores.com/incident/862376 Wed, 25 Mar 2026 07:18:00 -0000 https://status.sparecores.com/incident/862376#ef309b372755bbf2996be6fecf3aa41836f78989c4819e62154d45d331d7c979 Incident 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. Delayed data ingest https://status.sparecores.com/incident/862376 Wed, 25 Mar 2026 03:12:00 -0000 https://status.sparecores.com/incident/862376#039400979a01df847aff22a4b387385c9e52e83869c094202d5435e04ed37b39 Incident Recent ETL jobs have been failing. Website unreachable https://status.sparecores.com/incident/855819 Mon, 23 Mar 2026 23:38:00 -0000 https://status.sparecores.com/incident/855819#334cf904f6ef7727a8fe581257ca7ee98e208694477d22db82f648cac6dbe7b2 Incident 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. Website unreachable https://status.sparecores.com/incident/855819 Mon, 23 Mar 2026 22:58:00 -0000 https://status.sparecores.com/incident/855819#529873874f3ea064a4f13eb5547e1841b45207db58fa6f82006fd191fa3b0e03 Incident 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. Delayed data ingest https://status.sparecores.com/incident/820144 Fri, 06 Feb 2026 21:42:00 -0000 https://status.sparecores.com/incident/820144#77fc9c1833cb4431b13d75c1e87590eeb9204d903c576d0bbb364342b4c1e4b0 Incident Final fix deployed, and the Crawler is running at https://github.com/SpareCores/sc-data-dumps/actions/runs/21766478971/job/62803492787 Delayed data ingest https://status.sparecores.com/incident/820144 Fri, 06 Feb 2026 20:43:00 -0000 https://status.sparecores.com/incident/820144#694e1806f6369a7335554e58174e3d095dc31c29d271d47b1fe1acc13d713e61 Incident The proposed fix did not fully resolve the situation, so we continue investigating the situation. Delayed data ingest https://status.sparecores.com/incident/820144 Fri, 06 Feb 2026 15:39:00 -0000 https://status.sparecores.com/incident/820144#0a38f30fabaefc46552bd2bad37570d9274ffd47ee8d767152cbd2e11a1d46f2 Incident A fix for the removed Azure client is currently being tested, upstream bugreport opened. Delayed data ingest https://status.sparecores.com/incident/820144 Fri, 06 Feb 2026 15:21:00 -0000 https://status.sparecores.com/incident/820144#5d3397d724c099d2bea9a0c8a81f5081d3f2105ebdd7480d6a6f413535caab3a Incident 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. Delayed data ingest https://status.sparecores.com/incident/820144 Fri, 06 Feb 2026 10:38:00 -0000 https://status.sparecores.com/incident/820144#8e0f92e7006ff27085b152da9d6c1199870e26d1f46dabdd559d7e1ed4741839 Incident The Crawler's hourly and more frequent runs have been failing for 2 hours, potentially resulting in outdated data. sc-data migration https://status.sparecores.com/incident/810477 Fri, 23 Jan 2026 16:30:00 -0000 https://status.sparecores.com/incident/810477#99ac1695703be0b3b9582e16c9ed5ac0d09a0a6c359980db0b7af956c1b903d5 Incident Migration complete, data is flowing to the new repo 🎉 S3 location was not affected. sc-data migration https://status.sparecores.com/incident/810477 Fri, 23 Jan 2026 16:03:00 -0000 https://status.sparecores.com/incident/810477#b1219b249f3e1a230c955e23987949492213c9bcefd9f6d01b366eac434421d0 Incident 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. Cloudfront migration https://status.sparecores.com/incident/436319 Sat, 28 Sep 2024 20:45:00 -0000 https://status.sparecores.com/incident/436319#c7f93ea6456f494585970306662028cec21447ebe326b69ebde4f011014a2b97 Incident The sparecores.com domain was removed from Amplify, and added to the directly managed Cloudfront distribution, CNAME update in progress. Cloudfront migration https://status.sparecores.com/incident/436319 Sat, 28 Sep 2024 20:39:00 -0000 https://status.sparecores.com/incident/436319#6373f43eea5e1751a31b76995fc78859497d8e53e9054b9f0dc976fbc92e77fc Incident 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. Homepage unavailable https://status.sparecores.com/incident/424671 Thu, 05 Sep 2024 13:11:00 -0000 https://status.sparecores.com/incident/424671#1668480f595e728ac24f14fb80675cfd7c56459054b0b1b7fd3bff12ec028124 Incident The static and SSR components of our homepage have been migrated away from Netlify, and the service is back to normal. Homepage unavailable https://status.sparecores.com/incident/424671 Thu, 05 Sep 2024 13:03:00 -0000 https://status.sparecores.com/incident/424671#a3988ad596530808f80bb8acdfd44de18d9ff2a9ab5542932e3d349646de5842 Incident We are investigating migration to another hosting provider. Homepage unavailable https://status.sparecores.com/incident/424671 Thu, 05 Sep 2024 12:55:00 -0000 https://status.sparecores.com/incident/424671#53023454cf9950adf7ec86501469e3fd57cca637e2b481e73ed3ca0671846e50 Incident 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". Degraded API https://status.sparecores.com/incident/416964 Wed, 21 Aug 2024 09:39:00 -0000 https://status.sparecores.com/incident/416964#d9369d9235114339fc1dd255c67ba1014080ee43e2f996ce9355cd44c0897548 Incident We have upgraded the cluster to use larger instances to support the increased memory requirements of the Keeper. Degraded API https://status.sparecores.com/incident/416964 Wed, 21 Aug 2024 07:21:00 -0000 https://status.sparecores.com/incident/416964#7dba8c0e97b62bf940b8fbd9d7ea2a36a4c483e0ed99f8e7c7058bf60c89206c Incident We have identified the root cause (more memory required for Duck DB compared to SQLite), and currently testing a fix offline. Degraded API https://status.sparecores.com/incident/416964 Wed, 21 Aug 2024 04:35:00 -0000 https://status.sparecores.com/incident/416964#d9f1faf4248b55e41fbe8873679f959489008f0a9c6bf7a720440381252179d4 Incident 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.