Affected Components: Spinnable APP

Sep 29, 17:40:30 GMT+0
Identified - New Spinnable is coming with centralized billing and unlimited users.

Duration: 6 days, 14 hours and 8 minutes

Affected Components: Supabase → Database

Aug 31, 17:49:04 GMT+0
Investigating - While the first set of actions are taking effect, we are implementing a second set of likely mitigations to attempt to facilitate improvement in project creation..

Aug 31, 19:06:38 GMT+0
Resolved - Project creation has returned to baseline consistently..

Aug 31, 17:20:50 GMT+0
Investigating - We continue to work this issue. The steps we have taken are addressing the hypothesized cause of the issue. We are implementing further related mitigations..

Aug 31, 16:28:30 GMT+0
Investigating - Project creation is failing for new projects on the platform. We are investigating..

Aug 31, 16:53:46 GMT+0
Investigating - We have a working hypothesis on the cause of the issue, and are implementing steps to try to improve project creation performance..

Aug 31, 18:01:08 GMT+0
Identified - We are seeing the mitigation steps having the desired effect. Project creation is recovering..

Aug 31, 18:29:54 GMT+0
Monitoring - Project creation is reporting as recovered across the platform. We will monitor for stability in the near term..

Duration: 5 days, 5 hours and 5 minutes

Affected Components: Supabase → Database

Aug 3, 17:09:16 GMT+0
Identified - We have identified the cause of the upgrade delays and are working on a fix..

Aug 3, 16:19:52 GMT+0
Investigating - We are continuing to investigate project upgrade issues..

Aug 3, 19:47:58 GMT+0
Identified - We are developing a fix for the upgrade issues..

Aug 4, 15:30:47 GMT+0
Identified - The team has identified a likely fix and is consolidating the details in order to move to thorough testing. We will update again when the fix is applied..

Aug 5, 14:58:43 GMT+0
Monitoring - We have deployed a tested fix for the upgrade issue impacting some projects. The fix has been effective and we are monitoring for continued stability..

Aug 4, 23:38:20 GMT+0
Identified - We are continuing to test the fix to project upgrades. We will update again when the fix is applied..

Aug 3, 15:28:10 GMT+0
Investigating - We are investigating a potential issue that could result in a delay or failure in some users' project upgrades..

Aug 3, 22:46:03 GMT+0
Identified - We are continuing to fix project upgrade issues and are investigating further remediation. We will provide our next update within the next 14 hours..

Aug 5, 17:33:15 GMT+0
Resolved - Project upgrades have remained stable, we are resolving this incident..

Duration: 8 days, 15 hours and 9 minutes

Affected Components: Fly.io → Regional Availability → EU

Jul 31, 20:11:51 GMT+0
Resolved - This incident has been resolved..

Jul 31, 19:02:43 GMT+0
Monitoring - A fix has been implemented and we are monitoring the results..

Jul 31, 16:44:41 GMT+0
Investigating - Creating machines in CDG region may fail at this time with an "no capacity available in cdg" message. Existing apps continue to run..

Duration: 2 days, 10 hours and 22 minutes

Affected Components: Supabase → Database

Jul 31, 12:27:54 GMT+0
Investigating - We're investigating issues updating DNS records for newly created, unpaused, or updated databases..

Jul 31, 13:26:16 GMT+0
Resolved - The incident has been resolved..

Jul 31, 12:41:51 GMT+0
Identified - We have identified that the issue is with an upstream DNS provider, causing DNS creation delays for newly created, unpaused, or updated databases. Our team is actively monitoring the situation and will provide further updates as more information becomes available..

Jul 31, 12:55:52 GMT+0
Monitoring - The upstream DNS provider has implemented a fix and is monitoring the results. We are seeing signs of recovery; we will continue to monitor the situation and will provide further updates as more information becomes available..

Duration: 5 days, 1 hour and 49 minutes

Affected Components: Supabase → Database

Jul 27, 20:34:54 GMT+0
Investigating - We are investigating failures in provisioning DNS records for projects, there may be delays in creation of DNS records for new or unpaused projects..

Jul 27, 20:39:48 GMT+0
Identified - We have identified the cause of delays in DNS records creation and are actively working on a fix. We will continue to provide updates as things progress..

Jul 27, 20:53:39 GMT+0
Identified - We have identified and mitigated the issue that was blocking DNS updates. DNS record creation is succeeding, and latency has returned to normal levels. A subset of projects that encountered provisioning failures during the incident will require DNS records to be backfilled, and we are actively remediating these affected projects..

Jul 27, 22:23:08 GMT+0
Monitoring - All failed DNS creation has been backfilled, and customers should no longer see missing DNS records in their projects. DNS record creation and latency have returned to normal levels. We will continue to monitor before resolving this incident..

Jul 27, 22:36:44 GMT+0
Resolved - This incident is resolved. DNS creation for new projects has been fixed since 20:35 UTC. Backfill of missing DNS records has been completed at 22:20 UTC. Please contact Support if your project seems impacted by missing DNS records..

Duration: 19 days, 15 hours and 46 minutes

Affected Components: Supabase → Database

Jul 17, 19:20:33 GMT+0
Investigating - We are testing mitigation options to attempt to restore project action performance..

Jul 17, 17:49:58 GMT+0
Investigating - Certain project actions are failing. We are actively investigating to determine the regions impacted and source of the issue..

Jul 17, 18:16:46 GMT+0
Investigating - Project actions in us-east-1, us-east-2, sa-east-1, ca-central-1 are experiencing significant increases in error rates. We are exploring the best options for restoring performance..

Jul 17, 18:47:55 GMT+0
Investigating - We have determined that there are four main project actions impacted in the identified regions: Pause/unpause failures, Restore/PITR failures, PITR configuration failures and Backup problems. We are pursuing root cause and mitigation options in parallel..

Jul 17, 19:45:29 GMT+0
Identified - We have identified a problem with a specific job in us-east-1, we have mitigated the job and are observing the results..

Jul 17, 20:21:37 GMT+0
Monitoring - The mitigation has returned project activity to normal performance. Project actions that failed during the outage are being requeued to run. We will continue to monitor to ensure project functionality..

Jul 18, 01:41:45 GMT+0
Resolved - Project actions have been sustained at normal performance. This incident is resolved..

Duration: 50 minutes

Affected Components: WhatsApp, API, E2B sandboxes

Jul 2, 15:10:44 GMT+0
Identified - We're performing scheduled maintenance to improve the reliability and performance of our platform. During this window you may experience brief interruptions or slower response times. No action is needed on your end, and your data is safe..

Jul 2, 23:15:01 GMT+0
Identified - Maintenance is now in progress.

Jul 3, 00:04:43 GMT+0
Completed - Maintenance has completed successfully..

Duration: 11 days, 7 hours and 8 minutes

Affected Components: Supabase → Database

Jun 25, 15:32:53 GMT+0
Identified - We are aware that upgrades continue to be delayed. We are exploring other factors that are contributing to the slow upgrades..

Jun 25, 16:03:11 GMT+0
Identified - We are continuing to work through a variety of options for improving upgrade performance. This includes working with our upstream provider and adjusting operational parameters..

Jun 25, 16:27:00 GMT+0
Identified - We are implementing operational mitigations to try to improve upgrade performance..

Jun 25, 17:46:27 GMT+0
Identified - We are starting to notice improvements as a result of our mitigation efforts, and expect that project upgrades should start to become less delayed. We’ll continue monitoring and will update as we observe improvements across the fleet..

Jun 25, 18:08:06 GMT+0
Monitoring - We have implemented all necessary mitigations and the project upgrade rates have returned to normal across the fleet. We will continue to monitor these flows for any irregularities or recurring degradation. If you are still experiencing delayed or blocked upgrades on your Project, please contact Support..

Jun 25, 18:51:40 GMT+0
Resolved - Through our monitoring, we have determined that project upgrade behavior has returned to normal across the fleet. This incident is resolved..

Jun 25, 14:20:31 GMT+0
Investigating - We are investigating potential upgrade issues in multiple regions. We are working to confirm impact and determine next steps..

Jun 25, 14:41:28 GMT+0
Investigating - Upgrades are taking longer than usual, but generally will complete if allowed to proceed. We are investigating the cause of the delays..

Jun 25, 15:01:28 GMT+0
Identified - The upgrade delays have been caused by resource capacity limits. We are taking actions to increase the appropriate resources..

Jun 25, 17:03:54 GMT+0
Identified - We are continuing our operational and investigative work to improve upgrade flow performance and mitigate further problems..

Duration: 1 day, 11 hours and 40 minutes

Affected Components: Composio → Composio Platform

Jun 26, 16:40:26 GMT+0
Resolved - This incident has been resolved..

Jun 25, 05:00:00 GMT+0
Investigating - We've identified some transient issues with some toolkits like Outlook, Gmail, Google Calendar and some others. We are investigating a root cause and working closely with our providers to address it as quickly as possible..

Jun 26, 11:03:14 GMT+0
Identified - _We've traced the issue to one of our integration providers (Composio). A fix is actively being implemented, and we're adding a second provider to build in redundancy so integrations no longer depend on a single source. This is our top priority — next update coming shortly._.

Jun 26, 13:13:09 GMT+0
Monitoring - We implemented a general fix and are currently monitoring the result. All tools should be back to normal. Please report any issues you find. We are sorry for the disruption .

Duration: 3 days, 3 hours and 41 minutes

Jun 23, 15:16:57 GMT+0
Investigating - We are investigating errors in creating and unpausing projects in the eu-west-1 region..

Jun 23, 15:26:40 GMT+0
Identified - We have identified the issue is related to keys and are preparing a mitigation..

Jun 23, 15:43:13 GMT+0
Identified - Multiple mitigations have been deployed and project create performance is improving..

Jun 23, 15:46:38 GMT+0
Identified - During this incident, postgres upgrade functionality has also been affected. The key updates are being deployed and other mitigations continue to take effect..

Jun 23, 16:01:57 GMT+0
Monitoring - Key updates and other mitigations have been fully deployed and project creation and unpause functionality is returning to normal. We will continue to monitor this region for stability for the next 30 minutes..

Jun 23, 16:32:38 GMT+0
Resolved - Project create and unpause operations have returned to normal and remained stable for the past 30 minutes..

Duration: 1 day, 9 hours and 56 minutes

Affected Components: API

May 24, 11:13:43 GMT+0
Investigating - We are currently investigating an incident with an upstream provider of tools for workers..

May 24, 22:32:40 GMT+0
Monitoring - We implemented a fix and are currently monitoring the result. We will email users individually to explain the actions taken and the disruption they saw with some of their connected accounts..

May 25, 21:09:43 GMT+0
Resolved - This incident has been resolved. All tools should be working correctly after reconnection. We will notify users by email in the coming day with more details about the causes and measures taken..

May 26, 21:00:00 GMT+0
Postmortem - ### Composio security incident — May 21, 2026 On May 21, 2026, **Composio** — one of the integration providers Spinnable uses to connect to third-party services — experienced a security incident. Composio's own analysis indicates the affected scope was small (around 0.3% of customer connections globally, concentrated in GitHub, which Spinnable does not route through Composio). ### Impact on Spinnable We have **no indication that any Spinnable accounts have been impacted**. The connections that route through Composio (Gmail, Outlook, Asana, and similar) are stored on Composio's infrastructure, not ours — so our exposure tracked theirs. Integrations Spinnable provides through other MCPs or directly are not part of this incident. We reviewed our access logs for activity from the attacker's known IP addresses across the incident window and found **no evidence of unauthorized access to Spinnable systems**. ### What we did Out of an abundance of caution, every affected connection in our project has been invalidated — either through Composio's own bulk-revocation effort, by per-connection revocation we ran through their API, or through direct credential rotation (X / Twitter) where Composio's revocation pathway was failing. Affected users were notified directly by email. ### Timeline (UTC) | When | Event | | ------------------- | ---------------------------------------------------------------------------------------------------------- | | May 21, 08:05–16:15 | Composio incident window | | May 23 | Composio published their public disclosure and began bulk revocation | | May 24 | Spinnable forensic snapshot, per-connection revocation for our project, X (Twitter) client-secret rotation | | May 26 | Post-mortem published; status page updated | | May 27 | Spinnable emailed the affected users directly | ### What we've improved * Enabled 2FA on Spinnable's Composio dashboard account * Configured IP allowlisting on the Composio API key (a feature Composio rolled out as part of their incident response) * Reorganised our public status-page components to separate Spinnable services from subprocessors, so the same kind of upstream incident attributes correctly in future * Committed the response tooling (snapshot → resolve users → revoke → comms) to the Spinnable repo for faster future runs ### Looking forward For toolkits where token leakage would be high-impact, we're evaluating moving to **bring-your-own OAuth credentials**, which would give Spinnable a direct kill switch independent of subprocessor cooperation. We'll share updates as that work progresses. ### Reference Composio's full public disclosure: <https://composio.dev/blog/composio-may-2026-security-incident> Questions or concerns: [security@spinnable.ai](mailto:security@spinnable.ai).

Duration: 5 days, 18 hours and 31 minutes

Affected Components: WhatsApp

May 22, 16:51:19 GMT+0
Monitoring - We have deployed a fix and will progressively roll-out WhatsApp back to all users by Monday. .

May 21, 06:43:37 GMT+0
Monitoring - We have given all workers a new WhatsApp number. You will be contacted by the workers through the new number.

May 21, 07:17:35 GMT+0
Identified - We are now in the process of setting up new numbers for your AI workers.

May 20, 19:42:54 GMT+0
Investigating - The Spinnable WhatsApp platform number is currently down. You cannot communicate through WhatsApp unless they have a dedicated phone number. All other communication methods are working (Interface, Email, Tools). We are investigating to bring it back up as soon as possible..

May 25, 21:33:44 GMT+0
Monitoring - We started rolling out a solution. Service should be fully restored in two days..

May 26, 14:13:49 GMT+0
Resolved - This incident has been resolved, all users will have WhatsApp access by the end of the day.

Duration: 29 minutes

Affected Components: API

Apr 29, 14:50:00 GMT+0
Identified - Our upstream toolkit provider is experiencing unavailability and timeouts. If may notice your workers taking very long to start answering or failing to use certain tools. We are actively monitoring this issue.

Apr 29, 15:18:58 GMT+0
Resolved - This incident has been resolved..

Duration: 38 minutes

Affected Components: API

Apr 28, 15:18:18 GMT+0
Investigating - We are currently investigating this incident..

Apr 28, 15:56:40 GMT+0
Resolved - This incident has been resolved..

Duration: 3 hours and 12 minutes

Affected Components: API

Apr 14, 07:00:51 GMT+0
Investigating - We are currently investigating this incident..

Apr 14, 10:12:33 GMT+0
Monitoring - We implemented a fix and are currently monitoring the result..

Apr 14, 10:12:44 GMT+0
Resolved - This incident has been resolved..

Duration: 1 hour and 17 minutes

Affected Components: API

Apr 13, 10:55:22 GMT+0
Investigating - We are currently investigating this incident..

Apr 13, 11:02:02 GMT+0
Identified - Workers using Gmail and Google Calendar are currently not available. We are continuing to work on a fix for this incident..

Apr 13, 12:12:20 GMT+0
Resolved - This incident has been resolved..

Duration: 32 minutes

Affected Components: API

Apr 7, 13:38:18 GMT+0
Investigating - We are experiencing timeouts with our authentication provider. Investigating.

Apr 7, 13:43:40 GMT+0
Monitoring - The issue has been fixed. We are currently monitoring..

Apr 7, 14:10:11 GMT+0
Resolved - This incident has been resolved..

Duration: 1 hour and 58 minutes

Affected Components: API

Apr 2, 16:00:00 GMT+0
Identified - We've identified an issue with our browser use provider. We are monitoring the situation.

Apr 2, 17:57:51 GMT+0
Resolved - This incident has been resolved..

Duration: 7 hours and 14 minutes

Affected Components: API

Apr 1, 14:13:38 GMT+0
Resolved - This incident has been resolved..

Apr 1, 07:00:00 GMT+0
Investigating - We are experiencing increased latency with the upstream providers. This is directly affecting the latency of Spinnable workers that can take several minutes to complete tasks sometimes error out..

Apr 1, 10:54:24 GMT+0
Identified - Our upstream model providers are experiencing degraded performance. We are improving the robustness and monitoring.

Duration: 1 hour

Affected Components: API

Mar 16, 09:37:00 GMT+0
Investigating - We identified an issue where workers might fail to execute skills that require running code. We're working on a fix..

Mar 16, 10:12:00 GMT+0
Identified - We are still working on a fix..

Mar 16, 10:36:55 GMT+0
Resolved - This incident has been resolved and the fix will be live in a few moments..

Duration: 15 minutes

Affected Components: API

Mar 10, 09:07:00 GMT+0
Investigating - We are currently investigating this incident..

Mar 10, 09:13:52 GMT+0
Identified - We are continuing to work on a fix for this incident..

Mar 10, 09:18:35 GMT+0
Monitoring - We implemented a fix and are currently monitoring the result..

Mar 10, 09:22:17 GMT+0
Resolved - This incident has been resolved..

Duration: 2 days, 8 hours and 10 minutes

Affected Components: WhatsApp

Mar 6, 08:33:46 GMT+0
Identified - We are still working on solving our connection with WhatsApp. Apologies for the disruption..

Mar 5, 19:27:50 GMT+0
Investigating - We are currently investigating this incident..

Mar 5, 21:05:44 GMT+0
Identified - We are continuing to work on a fix for this incident..

Mar 6, 20:00:00 GMT+0
Resolved - This incident has been resolved..

Duration: 7 hours and 53 minutes

Affected Components: API

Mar 3, 06:30:00 GMT+0
Identified - Workers might have missed their scheduled tasks in the past hours..

Mar 3, 11:18:17 GMT+0
Monitoring - We already applied a fix and will be monitoring the system until tomorrow. Please reach out if you face any further issues. We apologize for the inconvenience..

Mar 3, 14:23:15 GMT+0
Resolved - We'll keep monitoring..

Duration: 1 day, 2 hours and 30 minutes

Affected Components: API

Jan 23, 07:30:47 GMT+0
Resolved - We deployed one more fix and are now resolving this. Apologies again for the long disruption of the service..

Jan 22, 05:00:53 GMT+0
Investigating - When an image is attached to a message, workers are sometimes unable to see the message, and fail silently. We are currently investigating this issue..

Jan 22, 11:02:52 GMT+0
Identified - PDF files are also affected. We are continuing to investigate this incident..

Jan 23, 03:17:47 GMT+0
Investigating - We are still investigating this issue. Apologies for the long duration..

Jan 23, 05:41:02 GMT+0
Monitoring - We've deployed a fix and will be monitoring. Let us know if you still face any errors or silent fails with messages that contain attachments..

Duration: 4 hours and 18 minutes

Affected Components: API

Dec 17, 09:30:21 GMT+0
Investigating - We are currently investigating an issue with the hiring process. Let us know if you have issues hiring workers.

Dec 17, 11:42:19 GMT+0
Monitoring - We implemented a fix and are currently monitoring the result..

Dec 17, 13:48:10 GMT+0
Resolved - This incident has been resolved..

Duration: 1 hour and 38 minutes

Affected Components: API, WhatsApp

Nov 24, 09:40:00 GMT+0
Identified - Our database provider is facing issues, which affects our users' ability to log in and use our app..

Nov 24, 11:17:57 GMT+0
Resolved - This incident has been resolved..