Incidents reported on status page for CalStudio https://status.calstudio.com/ en https://status.calstudio.com/ Mon, 06 Jul 2026 15:53:58 +0000 https://status.calstudio.com/#9341084269766bbbf90141e113c7ef205fb6cb6b9f34be47754908c8291fbdb8 CalStudio recovered https://status.calstudio.com/ Mon, 06 Jul 2026 15:46:07 +0000 https://status.calstudio.com/#9341084269766bbbf90141e113c7ef205fb6cb6b9f34be47754908c8291fbdb8 CalStudio went down https://status.calstudio.com/ Mon, 06 Jul 2026 15:42:01 +0000 https://status.calstudio.com/#433ca337682a71a9b0a6dd504f9edad88deb6120b9e0e7aee362072d9398acc5 CalStudio recovered https://status.calstudio.com/ Mon, 06 Jul 2026 15:39:42 +0000 https://status.calstudio.com/#433ca337682a71a9b0a6dd504f9edad88deb6120b9e0e7aee362072d9398acc5 CalStudio went down https://status.calstudio.com/ Sat, 27 Jun 2026 10:56:58 +0000 https://status.calstudio.com/#8139582471a85df610358f4587a3f7415a29eb8b31cb8e195a23f75c232c8434 CalStudio recovered https://status.calstudio.com/ Sat, 27 Jun 2026 10:53:43 +0000 https://status.calstudio.com/#8139582471a85df610358f4587a3f7415a29eb8b31cb8e195a23f75c232c8434 CalStudio went down https://status.calstudio.com/ Fri, 13 Feb 2026 00:36:37 +0000 https://status.calstudio.com/#27c9cef082935c56337a18c39eee8af4cbd8a54c02a927d7046d0dc2ad97a12a CalStudio Custom Domains went down https://status.calstudio.com/incident/714574 Wed, 16 Jul 2025 02:02:00 -0000 https://status.calstudio.com/incident/714574#d375caff7fee15e4536dbd76402f063528501c1391919b697daaa5fca0ecba96 Security Incident 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) 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.