Incidents | CalStudio Incidents reported on status page for CalStudio https://status.calstudio.com/ en CalStudio recovered https://status.calstudio.com/ Sun, 10 Aug 2025 12:45:11 +0000 https://status.calstudio.com/#dd6417b252244406080d5a788489f3d165c455d9ad686c0db3c74caef6847908 CalStudio recovered CalStudio went down https://status.calstudio.com/ Sun, 10 Aug 2025 12:42:10 +0000 https://status.calstudio.com/#dd6417b252244406080d5a788489f3d165c455d9ad686c0db3c74caef6847908 CalStudio went down CalStudio recovered https://status.calstudio.com/ Fri, 08 Aug 2025 07:51:47 +0000 https://status.calstudio.com/#ef5c9b4462bb790ea47a6a72cc5c008f2be0af258d6161a4789ec0d59cd730d0 CalStudio recovered CalStudio went down https://status.calstudio.com/ Fri, 08 Aug 2025 07:48:48 +0000 https://status.calstudio.com/#ef5c9b4462bb790ea47a6a72cc5c008f2be0af258d6161a4789ec0d59cd730d0 CalStudio went down CalStudio recovered https://status.calstudio.com/ Fri, 08 Aug 2025 07:36:45 +0000 https://status.calstudio.com/#8594dea769082a6da36dcf8bad8a1a13700e2d92ebcf70d30efdba70e8a416cb CalStudio recovered CalStudio went down https://status.calstudio.com/ Fri, 08 Aug 2025 07:31:27 +0000 https://status.calstudio.com/#8594dea769082a6da36dcf8bad8a1a13700e2d92ebcf70d30efdba70e8a416cb CalStudio went down CalStudio recovered https://status.calstudio.com/ Fri, 08 Aug 2025 07:27:46 +0000 https://status.calstudio.com/#0359ab209c31ba2eca53cd546df3cfc1c4d90be67ceb8f00d63ef38ce95cdb51 CalStudio recovered CalStudio went down https://status.calstudio.com/ Fri, 08 Aug 2025 07:22:16 +0000 https://status.calstudio.com/#0359ab209c31ba2eca53cd546df3cfc1c4d90be67ceb8f00d63ef38ce95cdb51 CalStudio went down CalStudio recovered https://status.calstudio.com/ Mon, 28 Jul 2025 13:59:02 +0000 https://status.calstudio.com/#9447e4430c4b113efe0f6b2b20dffcc3c73296376e398dadac9d12d72331bce9 CalStudio recovered CalStudio went down https://status.calstudio.com/ Mon, 28 Jul 2025 13:56:02 +0000 https://status.calstudio.com/#9447e4430c4b113efe0f6b2b20dffcc3c73296376e398dadac9d12d72331bce9 CalStudio went down CalStudio subdomains recovered https://status.calstudio.com/ Sat, 19 Jul 2025 13:50:23 +0000 https://status.calstudio.com/#09476531041737d66a6ecca5ef7b821668022c43279a78ee998db552e681493f CalStudio subdomains recovered CalStudio subdomains went down https://status.calstudio.com/ Sat, 19 Jul 2025 12:50:20 +0000 https://status.calstudio.com/#09476531041737d66a6ecca5ef7b821668022c43279a78ee998db552e681493f CalStudio subdomains went down CalStudio subdomains recovered https://status.calstudio.com/ Fri, 18 Jul 2025 17:55:16 +0000 https://status.calstudio.com/#375aa6ecf2490e563667cf3c41f153aa92fb74c3d3ae63d51eec498f9c9d12de CalStudio subdomains recovered CalStudio subdomains went down https://status.calstudio.com/ Fri, 18 Jul 2025 17:49:20 +0000 https://status.calstudio.com/#375aa6ecf2490e563667cf3c41f153aa92fb74c3d3ae63d51eec498f9c9d12de CalStudio subdomains went down CalStudio recovered https://status.calstudio.com/ Thu, 17 Jul 2025 15:19:59 +0000 https://status.calstudio.com/#81952430da24c80232185ad0ea03b0761fa51b312b7a8f1f89d43342fc276be7 CalStudio recovered CalStudio went down https://status.calstudio.com/ Thu, 17 Jul 2025 15:14:55 +0000 https://status.calstudio.com/#81952430da24c80232185ad0ea03b0761fa51b312b7a8f1f89d43342fc276be7 CalStudio went down Security Incident – Unauthorized Stripe Activity (Resolved) https://status.calstudio.com/incident/714574 Wed, 16 Jul 2025 02:02:00 -0000 https://status.calstudio.com/incident/714574#d375caff7fee15e4536dbd76402f063528501c1391919b697daaa5fca0ecba96 Security Incident Resolved Security Incident – Unauthorized Stripe Activity (Resolved) https://status.calstudio.com/incident/714574 Wed, 16 Jul 2025 01:57:00 -0000 https://status.calstudio.com/incident/714574#d3ce84fd46375d8dd64356bc735262e3ddd2901aa6121c3f6ebf843553599e8f ## 🔒 Security Incident – API Key Leak via Contractor (Resolved) **Incident Date:** July 15, 2025 **Published:** August 28, 2025 --- ### Summary On **July 15, 2025**, we discovered a security incident involving a leaked Stripe API key. The key was unintentionally exposed due to a misconfigured environment used by a third-party contractor during a short-term engagement. The key was misused to attempt unauthorized charges via stored Stripe tokens. Importantly, **no payment card details, login credentials, chat data, or uploaded content were accessed or exposed**. We took immediate action to revoke access, audit the incident, and notify affected users. --- ### Impact - **3 customers** were affected - All unauthorized transactions were reversed - No service downtime or data loss occurred - No sensitive personal data was compromised --- ### Response & Communication - Affected users were notified **promptly after detection** - **Routine status updates** were provided to those impacted - Refunds and account protections were applied proactively --- ### Root Cause The incident was caused by a development `.env` file containing a Stripe secret key that was present in a cloned repository accessed by a contractor. Their local environment did not have proper isolation or secret management in place. --- ### Remediation Actions - Stripe keys immediately revoked and rotated - Contractor access terminated - Full audit of Git repositories and infrastructure conducted - Secrets moved to **AWS Secrets Manager** - Enforced scoped permissions, 2FA, and IP whitelisting - Stripe anomaly alerts and monitoring rules implemented --- ### Current Status ✅ The incident is fully resolved and closed. We’ve introduced stronger vetting and isolation policies for contractors, enforced stricter access management, and hardened our billing infrastructure. If you have any questions, please contact us at [support@calstudio.com](mailto:support@calstudio.com). Aditya Saxena Founder, [CalStudio.com](https://calstudio.com) Elevated System Resource Usage Detected https://status.calstudio.com/incident/557564 Tue, 06 May 2025 16:23:00 -0000 https://status.calstudio.com/incident/557564#2843193217d5f72bd90578ae911d12d6fb59db71a15e08bd34541b1adfa7deab Between 00:00 and 08:00 UTC on May 6th, we observed elevated system resource usage on our backend infrastructure. This resulted in slower response times for some requests. We have identified the root cause and implemented an optimization. System performance has since returned to normal. We continue to monitor the situation closely to ensure stability.