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: 19 days, 4 hours and 8 minutes

Affected Components: Supabase → Database

May 20, 22:48:13 GMT+0
Identified - We have identified the cause of the issue impacting read replica communication for projects. Our team is actively working on a fix and continuing to assess the impact to affected projects..

May 20, 23:41:26 GMT+0
Identified - Our team continues to work on implementing a fix for the issue. We are continuing to monitor the impact and will provide additional updates as progress is made..

May 21, 04:23:45 GMT+0
Monitoring - We have merged the fix and are monitoring for stability..

May 21, 04:44:27 GMT+0
Resolved - Communication between read replicas and their primaries for impacted projects has been restored. This incident is now resolved..

May 21, 01:12:31 GMT+0
Identified - Our team continues to work on implementing a fix for the issue. We will provide additional updates as progress is made..

May 20, 21:04:18 GMT+0
Investigating - Network restrictions are preventing read replicas from communicating with their primaries for a limited number of customer projects. We are actively investigating this issue..

May 20, 21:46:35 GMT+0
Investigating - We are reviewing the impact of this issue, which is limited to projects with read replicas and network restrictions. We continue to both investigate mitigation options for the issue and identify projects that may be impacted..

May 21, 03:49:41 GMT+0
Identified - We have developed a fix and it is currently being validated. We will provide more updates soon..

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: 3 days and 10 minutes

Affected Components: API

May 12, 12:15:00 GMT+0
Identified - We are planning for a scheduled maintenance during that time..

May 12, 12:15:01 GMT+0
Identified - Maintenance is now in progress.

May 15, 12:24:57 GMT+0
Completed - Maintenance has completed successfully..

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: 16 days and 53 minutes

Affected Components: Supabase → Database

Apr 27, 13:31:39 GMT+0
Identified - The team is continuing to work through affected projects; however, a project restart is also effective. This can be performed from the <a href="https://supabase.com/dashboard/project/_/settings/general">dashboard</a> for your own projects at any time..

Apr 27, 12:39:59 GMT+0
Identified - We are seeing an increase in projects unavailable in eu-west-3 following an upstream issue with EC2 instances in the region. The team is working on restoring access to these projects.

Apr 27, 13:38:29 GMT+0
Identified - We have identified this issue across multiple regions, not just eu-west-3 as originally suspected. We are expanding the scope of efforts to bring affected projects back online. Users can also resolve this, in most cases, on their own via a project restart. This can be performed from the <a href="https://supabase.com/dashboard/project/_/settings/general">dashboard</a> for your own projects at any time..

Apr 27, 15:00:01 GMT+0
Identified - The team is still working to bring these back online, and have a fix under way. Many users can also resolve this on their own via a project restart. This can be performed from the <a href="https://supabase.com/dashboard/project/_/settings/general">dashboard</a> for your own projects at any time. But for those who are still seeing issues after a restart, we will be pushing a fix soon..

Apr 27, 16:22:27 GMT+0
Identified - The team is continuing their mitigation efforts. We've fixed and restarted most of the affected projects. We're continuously looking for any others that are affected so we can be sure to get them all fixed..

Apr 27, 18:34:49 GMT+0
Monitoring - We believe all users affected by this particular issue have been resolved. The team is going to keep an eye on these error rates to ensure we catch any that didn't originally appear, or that no new issues arise. We appreciate your patience as we worked through this issue..

Apr 27, 19:04:52 GMT+0
Resolved - This incident has been resolved..

Duration: 27 days, 20 hours and 39 minutes

Affected Components: Supabase → Database

Apr 17, 13:31:21 GMT+0
Investigating - We are currently investigating reports of users experiencing login issues when using Supabase Auth. At this time, the impact appears to be limited to a subset of users, primarily in North and South America. The exact cause and scope are still being determined. Our team is actively working to identify the root of the issue and will provide updates as more information becomes available. We appreciate your patience while we investigate..

Apr 17, 14:30:00 GMT+0
Investigating - We continue to work with partners and investigate..

Apr 17, 13:51:42 GMT+0
Investigating - We are actively investigating this issue and working with relevant partner organizations. At this time, we do not believe this issue is specific to any particular network provider. A subset of users continue to be impacted in both South and North America..

Apr 17, 14:16:55 GMT+0
Investigating - We have further clarified the scope and impact of the issues currently affecting users. A subset of users across North and South America are experiencing DNS resolution failures and HTTP 530 errors. These symptoms indicate a networking-related issue impacting the availability of Supabase projects. We are actively working with both internal teams and external network providers to isolate the root cause and determine the most effective path to resolution. We will continue to provide updates as more information becomes available..

Apr 17, 14:53:01 GMT+0
Investigating - We continue to have active lines of investigation going with our upstream network provider partners, and are still working toward a resolution. This issue affects the network-level access to projects. The projects themselves and the data in them are safe and unaffected. Users are seeing two separate symptoms of these networking issues: 1. DNS Lookup failures for supabase project URLs 2. 530 responses to HTTP requests to supabase project API Endpoints.

Apr 17, 15:09:13 GMT+0
Identified - Our upstream networking provider has discovered an issue and has declared an incident on their side. They are currently working toward resolution. We are actively working with them and will provide updates on progress as more information is available..

Apr 17, 15:41:58 GMT+0
Identified - Our upstream networking partner is continuing their investigation. We will continue to post regular updates as we have more information..

Apr 17, 16:31:05 GMT+0
Identified - Our upstream networking provider has identified a fix and is currently implementing a fix. We are seeing preliminary improvements to error rates for users in North America, but are still following this issue closely with our provider..

Apr 17, 17:44:07 GMT+0
Identified - Upstream provider mitigations are still under way, and we are seeing improvements incrementally as routing regions have the mitigations applied. We are still seeing particular impact in South America, but some users in North America may still be affected as well. We anticipate continued incremental improvements and will update as we get more information..

Apr 17, 18:34:06 GMT+0
Identified - Our upstream provider has rolled the fix out to most regions. While we are seeing improvement, we are still seeing increased error rates in Mexico and Brazil and are continuing to work with them until this is fully resolved..

Apr 17, 20:35:10 GMT+0
Identified - Some users continue to experience errors. We are raising the issue with our provider..

Apr 17, 21:31:59 GMT+0
Identified - We recognize that some of our users, especially in parts of North and South America, are continuing to experience DNS and 5XX errors when trying to connect to their projects. We have escalated this issue with our network provider and will work with them continuously until the problems are resolved..

Apr 17, 19:33:24 GMT+0
Identified - The fix that our upstream provider implemented has taken effect. Service has significantly improved across all previously impacted regions. There are still residual elevated error rates in a handful of regions and we will continue to work with our provider to eliminate them..

Apr 17, 20:10:25 GMT+0
Monitoring - Our upstream provider has reported their incident resolved. We will continue to monitor for any errors our customers may be experiencing for another 30 minutes..

Apr 17, 23:08:02 GMT+0
Identified - We've seen a marked improvement in error rates across all regions in the last few minutes. We are still waiting on confirmation from our provider on status, but we believe things to be improved at the moment. We'll keep working on this until we have for sure reached a resolution..

Apr 18, 00:37:57 GMT+0
Monitoring - We've received confirmation from our networking provider that there is recovery across all regions. We are able to corroborate this with our own metrics collections. We will continue to monitor for a bit, but we believe this to be resolved at this time. We apologize for the trouble, and we appreciate your patience..

Apr 18, 02:01:40 GMT+0
Resolved - All metrics have been nominal and stable for several hours now, and our upstream provider has resolved their incident..

Apr 17, 13:02:16 GMT+0
Investigating - We are currently investigating reports of users experiencing login issues when using Supabase Auth. At this time, the impact appears to be limited to a subset of users, primarily in South America. The exact cause and scope are still being determined. Our team is actively working to identify the root of the issue and will provide updates as more information becomes available. We appreciate your patience while we investigate..

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: 10 days, 20 hours and 28 minutes

Affected Components: Supabase → Database

Mar 3, 02:10:36 GMT+0
Investigating - We're experiencing an increased number of errors in database operations in us-east-2 region. We'll post more details as we investigate..

Mar 3, 02:41:06 GMT+0
Identified - We’ve identified that this affects only a subset of projects in us-east-2.  We are taking remediation actions for the affected projects. If you’re affected, you can also fix it manually by restarting your project by visiting this page in the dashboard and click on Restart Project: https://supabase.com/dashboard/project/_/settings/general.

Mar 3, 03:14:07 GMT+0
Identified - We are currently continuing with remediation actions for affected projects. If you’re affected, you can also fix it manually by restarting your project by visiting this page in the dashboard and click on Restart Project: https://supabase.com/dashboard/project/_/settings/general.

Mar 3, 04:08:01 GMT+0
Monitoring - We've fixed majority of the affected projects. They are very few projects that need extra steps to resolve. We are working on them at the moment..

Mar 3, 06:31:05 GMT+0
Resolved - Root cause has been confirmed to be addressed. Handful of projects still require manual intervention however. We will be reaching out to their respective owners..

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..

Duration: 5 hours and 39 minutes

Affected Components: API, WhatsApp

Nov 18, 12:00:00 GMT+0
Identified - A global Cloudflare issue is affecting multiple systems worldwide. We'll monitor this and update accordingly .

Nov 18, 17:39:21 GMT+0
Resolved - .

Duration: 8 minutes

Affected Components: API, WhatsApp

Nov 14, 19:16:42 GMT+0
Investigating - A fix is expected within the hour..

Nov 14, 19:24:16 GMT+0
Resolved - We've identified and solved the issue involving a database migration..

Duration: 31 minutes

Affected Components: API

Nov 10, 09:50:02 GMT+0
Investigating - This is a test and can be ignored.

Nov 10, 10:21:15 GMT+0
Resolved - This incident has been resolved..

Duration: 2 hours and 53 minutes

Affected Components: API

Oct 20, 09:00:00 GMT+0
Resolved - This incident has been resolved..

Oct 20, 08:31:00 GMT+0
Identified - We are continuing to work on a fix for this incident..

Oct 20, 07:31:00 GMT+0
Identified - We've been affected by an outage of AWS services..