Spinnable Status - Incident history https://status.spinnable.ai Spinnable Tue, 29 Sep 2026 23:00:00 +0000 Launching Workspaces at Spinnable Type: Maintenance Affected Components: Spinnable APP Sep 29, 17:40:30 GMT+0 - Identified - New Spinnable is coming with centralized billing and unlimited users Type: Maintenance

Affected Components:

<p><small>Sep <var data-var='date'> 29</var>, <var data-var='time'>17:40:30</var> GMT+0</small><br><strong>Identified</strong> - New Spinnable is coming with centralized billing and unlimited users.</p> ]]> Tue, 29 Sep 2026 23:00:00 +0000 https://status.spinnable.ai/maintenance/cmumypgeh003j1mnx0ho2uc8d https://status.spinnable.ai/maintenance/cmumypgeh003j1mnx0ho2uc8d Project Creation Failures Type: Incident 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. Type: Incident

Duration: 6 days, 14 hours and 8 minutes

Affected Components:

<p><small>Aug <var data-var='date'> 31</var>, <var data-var='time'>17:49:04</var> GMT+0</small><br><strong>Investigating</strong> - 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..</p> <p><small>Aug <var data-var='date'> 31</var>, <var data-var='time'>19:06:38</var> GMT+0</small><br><strong>Resolved</strong> - Project creation has returned to baseline consistently..</p> <p><small>Aug <var data-var='date'> 31</var>, <var data-var='time'>17:20:50</var> GMT+0</small><br><strong>Investigating</strong> - 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..</p> <p><small>Aug <var data-var='date'> 31</var>, <var data-var='time'>16:28:30</var> GMT+0</small><br><strong>Investigating</strong> - Project creation is failing for new projects on the platform. We are investigating..</p> <p><small>Aug <var data-var='date'> 31</var>, <var data-var='time'>16:53:46</var> GMT+0</small><br><strong>Investigating</strong> - We have a working hypothesis on the cause of the issue, and are implementing steps to try to improve project creation performance..</p> <p><small>Aug <var data-var='date'> 31</var>, <var data-var='time'>18:01:08</var> GMT+0</small><br><strong>Identified</strong> - We are seeing the mitigation steps having the desired effect. Project creation is recovering..</p> <p><small>Aug <var data-var='date'> 31</var>, <var data-var='time'>18:29:54</var> GMT+0</small><br><strong>Monitoring</strong> - Project creation is reporting as recovered across the platform. We will monitor for stability in the near term..</p> ]]> Mon, 31 Aug 2026 16:28:30 +0000 https://status.spinnable.ai/incident/cmthge53j7xmb0kpwjjh4wbpm https://status.spinnable.ai/incident/cmthge53j7xmb0kpwjjh4wbpm Project Upgrade Delays Type: Incident 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. Type: Incident

Duration: 5 days, 5 hours and 5 minutes

Affected Components:

<p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>17:09:16</var> GMT+0</small><br><strong>Identified</strong> - We have identified the cause of the upgrade delays and are working on a fix..</p> <p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>16:19:52</var> GMT+0</small><br><strong>Investigating</strong> - We are continuing to investigate project upgrade issues..</p> <p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>19:47:58</var> GMT+0</small><br><strong>Identified</strong> - We are developing a fix for the upgrade issues..</p> <p><small>Aug <var data-var='date'> 4</var>, <var data-var='time'>15:30:47</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Aug <var data-var='date'> 5</var>, <var data-var='time'>14:58:43</var> GMT+0</small><br><strong>Monitoring</strong> - 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..</p> <p><small>Aug <var data-var='date'> 4</var>, <var data-var='time'>23:38:20</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to test the fix to project upgrades. We will update again when the fix is applied..</p> <p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>15:28:10</var> GMT+0</small><br><strong>Investigating</strong> - We are investigating a potential issue that could result in a delay or failure in some users' project upgrades..</p> <p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>22:46:03</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to fix project upgrade issues and are investigating further remediation. We will provide our next update within the next 14 hours..</p> <p><small>Aug <var data-var='date'> 5</var>, <var data-var='time'>17:33:15</var> GMT+0</small><br><strong>Resolved</strong> - Project upgrades have remained stable, we are resolving this incident..</p> ]]> Mon, 3 Aug 2026 15:28:10 +0000 https://status.spinnable.ai/incident/cmt0roo9t1k320rmg9a74h9yx https://status.spinnable.ai/incident/cmt0roo9t1k320rmg9a74h9yx Capacity issues in CDG Type: 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. Type: Incident

Duration: 8 days, 15 hours and 9 minutes

Affected Components:

<p><small>Jul <var data-var='date'> 31</var>, <var data-var='time'>20:11:51</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Jul <var data-var='date'> 31</var>, <var data-var='time'>19:02:43</var> GMT+0</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results..</p> <p><small>Jul <var data-var='date'> 31</var>, <var data-var='time'>16:44:41</var> GMT+0</small><br><strong>Investigating</strong> - Creating machines in CDG region may fail at this time with an "no capacity available in cdg" message. Existing apps continue to run..</p> ]]> Fri, 31 Jul 2026 16:44:41 +0000 https://status.spinnable.ai/incident/cmt0s918n268h0rmgpc5yba0j https://status.spinnable.ai/incident/cmt0s918n268h0rmgpc5yba0j DNS creation delays Type: Incident 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. Type: Incident

Duration: 2 days, 10 hours and 22 minutes

Affected Components:

<p><small>Jul <var data-var='date'> 31</var>, <var data-var='time'>12:27:54</var> GMT+0</small><br><strong>Investigating</strong> - We're investigating issues updating DNS records for newly created, unpaused, or updated databases..</p> <p><small>Jul <var data-var='date'> 31</var>, <var data-var='time'>13:26:16</var> GMT+0</small><br><strong>Resolved</strong> - The incident has been resolved..</p> <p><small>Jul <var data-var='date'> 31</var>, <var data-var='time'>12:41:51</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Jul <var data-var='date'> 31</var>, <var data-var='time'>12:55:52</var> GMT+0</small><br><strong>Monitoring</strong> - 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..</p> ]]> Fri, 31 Jul 2026 12:27:53 +0000 https://status.spinnable.ai/incident/cmt0roocc1k3r0rmgd52korv9 https://status.spinnable.ai/incident/cmt0roocc1k3r0rmgd52korv9 Delays in creation of DNS records Type: Incident 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. Type: Incident

Duration: 5 days, 1 hour and 49 minutes

Affected Components:

<p><small>Jul <var data-var='date'> 27</var>, <var data-var='time'>20:34:54</var> GMT+0</small><br><strong>Investigating</strong> - We are investigating failures in provisioning DNS records for projects, there may be delays in creation of DNS records for new or unpaused projects..</p> <p><small>Jul <var data-var='date'> 27</var>, <var data-var='time'>20:39:48</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Jul <var data-var='date'> 27</var>, <var data-var='time'>20:53:39</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Jul <var data-var='date'> 27</var>, <var data-var='time'>22:23:08</var> GMT+0</small><br><strong>Monitoring</strong> - 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..</p> <p><small>Jul <var data-var='date'> 27</var>, <var data-var='time'>22:36:44</var> GMT+0</small><br><strong>Resolved</strong> - 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..</p> ]]> Mon, 27 Jul 2026 20:34:54 +0000 https://status.spinnable.ai/incident/cmt0rowa71l5o0rmgj1sn6tzy https://status.spinnable.ai/incident/cmt0rowa71l5o0rmgj1sn6tzy Project Actions Failing Across Multiple Regions Type: Incident 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. Type: Incident

Duration: 19 days, 15 hours and 46 minutes

Affected Components:

<p><small>Jul <var data-var='date'> 17</var>, <var data-var='time'>19:20:33</var> GMT+0</small><br><strong>Investigating</strong> - We are testing mitigation options to attempt to restore project action performance..</p> <p><small>Jul <var data-var='date'> 17</var>, <var data-var='time'>17:49:58</var> GMT+0</small><br><strong>Investigating</strong> - Certain project actions are failing. We are actively investigating to determine the regions impacted and source of the issue..</p> <p><small>Jul <var data-var='date'> 17</var>, <var data-var='time'>18:16:46</var> GMT+0</small><br><strong>Investigating</strong> - 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..</p> <p><small>Jul <var data-var='date'> 17</var>, <var data-var='time'>18:47:55</var> GMT+0</small><br><strong>Investigating</strong> - 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..</p> <p><small>Jul <var data-var='date'> 17</var>, <var data-var='time'>19:45:29</var> GMT+0</small><br><strong>Identified</strong> - We have identified a problem with a specific job in us-east-1, we have mitigated the job and are observing the results..</p> <p><small>Jul <var data-var='date'> 17</var>, <var data-var='time'>20:21:37</var> GMT+0</small><br><strong>Monitoring</strong> - 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..</p> <p><small>Jul <var data-var='date'> 18</var>, <var data-var='time'>01:41:45</var> GMT+0</small><br><strong>Resolved</strong> - Project actions have been sustained at normal performance. This incident is resolved..</p> ]]> Fri, 17 Jul 2026 17:49:58 +0000 https://status.spinnable.ai/incident/cmt0rowab1l610rmgncns2idw https://status.spinnable.ai/incident/cmt0rowab1l610rmgncns2idw Scheduled maintenance Type: Maintenance 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. Type: Maintenance

Duration: 50 minutes

Affected Components: , ,

<p><small>Jul <var data-var='date'> 2</var>, <var data-var='time'>15:10:44</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Jul <var data-var='date'> 2</var>, <var data-var='time'>23:15:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Jul <var data-var='date'> 3</var>, <var data-var='time'>00:04:43</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> ]]> Thu, 2 Jul 2026 23:15:00 +0000 https://status.spinnable.ai/maintenance/cmr3n6164001q0rqbikyckn82 https://status.spinnable.ai/maintenance/cmr3n6164001q0rqbikyckn82 Upgrade Failures Type: Incident 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. Type: Incident

Duration: 11 days, 7 hours and 8 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 25</var>, <var data-var='time'>15:32:53</var> GMT+0</small><br><strong>Identified</strong> - We are aware that upgrades continue to be delayed. We are exploring other factors that are contributing to the slow upgrades..</p> <p><small>Jun <var data-var='date'> 25</var>, <var data-var='time'>16:03:11</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Jun <var data-var='date'> 25</var>, <var data-var='time'>16:27:00</var> GMT+0</small><br><strong>Identified</strong> - We are implementing operational mitigations to try to improve upgrade performance..</p> <p><small>Jun <var data-var='date'> 25</var>, <var data-var='time'>17:46:27</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Jun <var data-var='date'> 25</var>, <var data-var='time'>18:08:06</var> GMT+0</small><br><strong>Monitoring</strong> - 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..</p> <p><small>Jun <var data-var='date'> 25</var>, <var data-var='time'>18:51:40</var> GMT+0</small><br><strong>Resolved</strong> - Through our monitoring, we have determined that project upgrade behavior has returned to normal across the fleet. This incident is resolved..</p> <p><small>Jun <var data-var='date'> 25</var>, <var data-var='time'>14:20:31</var> GMT+0</small><br><strong>Investigating</strong> - We are investigating potential upgrade issues in multiple regions. We are working to confirm impact and determine next steps..</p> <p><small>Jun <var data-var='date'> 25</var>, <var data-var='time'>14:41:28</var> GMT+0</small><br><strong>Investigating</strong> - Upgrades are taking longer than usual, but generally will complete if allowed to proceed. We are investigating the cause of the delays..</p> <p><small>Jun <var data-var='date'> 25</var>, <var data-var='time'>15:01:28</var> GMT+0</small><br><strong>Identified</strong> - The upgrade delays have been caused by resource capacity limits. We are taking actions to increase the appropriate resources..</p> <p><small>Jun <var data-var='date'> 25</var>, <var data-var='time'>17:03:54</var> GMT+0</small><br><strong>Identified</strong> - We are continuing our operational and investigative work to improve upgrade flow performance and mitigate further problems..</p> ]]> Thu, 25 Jun 2026 14:20:31 +0000 https://status.spinnable.ai/incident/cmt0rp4zv1m2a0rmgr5w2r11u https://status.spinnable.ai/incident/cmt0rp4zv1m2a0rmgr5w2r11u Issues with some toolkits Type: Incident 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 Type: Incident

Duration: 1 day, 11 hours and 40 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 26</var>, <var data-var='time'>16:40:26</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Jun <var data-var='date'> 25</var>, <var data-var='time'>05:00:00</var> GMT+0</small><br><strong>Investigating</strong> - 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..</p> <p><small>Jun <var data-var='date'> 26</var>, <var data-var='time'>11:03:14</var> GMT+0</small><br><strong>Identified</strong> - _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._.</p> <p><small>Jun <var data-var='date'> 26</var>, <var data-var='time'>13:13:09</var> GMT+0</small><br><strong>Monitoring</strong> - 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 .</p> ]]> Thu, 25 Jun 2026 05:00:00 +0000 https://status.spinnable.ai/incident/cmqtiy4g600iq2ipbhmzc95mu https://status.spinnable.ai/incident/cmqtiy4g600iq2ipbhmzc95mu Project create and unpause errors in eu-west-1 Type: Incident 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. Type: Incident

Duration: 3 days, 3 hours and 41 minutes

<p><small>Jun <var data-var='date'> 23</var>, <var data-var='time'>15:16:57</var> GMT+0</small><br><strong>Investigating</strong> - We are investigating errors in creating and unpausing projects in the eu-west-1 region..</p> <p><small>Jun <var data-var='date'> 23</var>, <var data-var='time'>15:26:40</var> GMT+0</small><br><strong>Identified</strong> - We have identified the issue is related to keys and are preparing a mitigation..</p> <p><small>Jun <var data-var='date'> 23</var>, <var data-var='time'>15:43:13</var> GMT+0</small><br><strong>Identified</strong> - Multiple mitigations have been deployed and project create performance is improving..</p> <p><small>Jun <var data-var='date'> 23</var>, <var data-var='time'>15:46:38</var> GMT+0</small><br><strong>Identified</strong> - During this incident, postgres upgrade functionality has also been affected. The key updates are being deployed and other mitigations continue to take effect..</p> <p><small>Jun <var data-var='date'> 23</var>, <var data-var='time'>16:01:57</var> GMT+0</small><br><strong>Monitoring</strong> - 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..</p> <p><small>Jun <var data-var='date'> 23</var>, <var data-var='time'>16:32:38</var> GMT+0</small><br><strong>Resolved</strong> - Project create and unpause operations have returned to normal and remained stable for the past 30 minutes..</p> ]]> Tue, 23 Jun 2026 15:16:57 +0000 https://status.spinnable.ai/incident/cmt0rp4z81m1z0rmg0lopj63i https://status.spinnable.ai/incident/cmt0rp4z81m1z0rmg0lopj63i Issues with worker tools from upstream provider Type: Incident 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) Type: Incident

Duration: 1 day, 9 hours and 56 minutes

Affected Components:

<p><small>May <var data-var='date'> 24</var>, <var data-var='time'>11:13:43</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating an incident with an upstream provider of tools for workers..</p> <p><small>May <var data-var='date'> 24</var>, <var data-var='time'>22:32:40</var> GMT+0</small><br><strong>Monitoring</strong> - 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..</p> <p><small>May <var data-var='date'> 25</var>, <var data-var='time'>21:09:43</var> GMT+0</small><br><strong>Resolved</strong> - 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..</p> <p><small>May <var data-var='date'> 26</var>, <var data-var='time'>21:00:00</var> GMT+0</small><br><strong>Postmortem</strong> - ### 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).</p> ]]> Sun, 24 May 2026 11:13:43 +0000 https://status.spinnable.ai/incident/cmpjoj12i009vnmnvxf3mjwxv https://status.spinnable.ai/incident/cmpjoj12i009vnmnvxf3mjwxv WhatsApp Service Disrupted Type: Incident 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 Type: Incident

Duration: 5 days, 18 hours and 31 minutes

Affected Components:

<p><small>May <var data-var='date'> 22</var>, <var data-var='time'>16:51:19</var> GMT+0</small><br><strong>Monitoring</strong> - We have deployed a fix and will progressively roll-out WhatsApp back to all users by Monday. .</p> <p><small>May <var data-var='date'> 21</var>, <var data-var='time'>06:43:37</var> GMT+0</small><br><strong>Monitoring</strong> - We have given all workers a new WhatsApp number. You will be contacted by the workers through the new number.</p> <p><small>May <var data-var='date'> 21</var>, <var data-var='time'>07:17:35</var> GMT+0</small><br><strong>Identified</strong> - We are now in the process of setting up new numbers for your AI workers.</p> <p><small>May <var data-var='date'> 20</var>, <var data-var='time'>19:42:54</var> GMT+0</small><br><strong>Investigating</strong> - 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..</p> <p><small>May <var data-var='date'> 25</var>, <var data-var='time'>21:33:44</var> GMT+0</small><br><strong>Monitoring</strong> - We started rolling out a solution. Service should be fully restored in two days..</p> <p><small>May <var data-var='date'> 26</var>, <var data-var='time'>14:13:49</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved, all users will have WhatsApp access by the end of the day.</p> ]]> Wed, 20 May 2026 19:42:54 +0000 https://status.spinnable.ai/incident/cmpegyfpz0128qnweii4ysoyx https://status.spinnable.ai/incident/cmpegyfpz0128qnweii4ysoyx Issues with upstream toolkit provider Type: Incident 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. Type: Incident

Duration: 29 minutes

Affected Components:

<p><small>Apr <var data-var='date'> 29</var>, <var data-var='time'>14:50:00</var> GMT+0</small><br><strong>Identified</strong> - 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.</p> <p><small>Apr <var data-var='date'> 29</var>, <var data-var='time'>15:18:58</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Wed, 29 Apr 2026 14:50:00 +0000 https://status.spinnable.ai/incident/cmok6skv5004iz4sewa0ml435 https://status.spinnable.ai/incident/cmok6skv5004iz4sewa0ml435 We're investigating an issue with tool connections Type: Incident 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. Type: Incident

Duration: 38 minutes

Affected Components:

<p><small>Apr <var data-var='date'> 28</var>, <var data-var='time'>15:18:18</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Apr <var data-var='date'> 28</var>, <var data-var='time'>15:56:40</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Tue, 28 Apr 2026 15:18:18 +0000 https://status.spinnable.ai/incident/cmoirtec506b83lrvxp6v376r https://status.spinnable.ai/incident/cmoirtec506b83lrvxp6v376r Unavailability of Google suite tools Type: Incident 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. Type: Incident

Duration: 3 hours and 12 minutes

Affected Components:

<p><small>Apr <var data-var='date'> 14</var>, <var data-var='time'>07:00:51</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Apr <var data-var='date'> 14</var>, <var data-var='time'>10:12:33</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Apr <var data-var='date'> 14</var>, <var data-var='time'>10:12:44</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Tue, 14 Apr 2026 07:00:51 +0000 https://status.spinnable.ai/incident/cmny9vrt7014vc8nxorhzjl6b https://status.spinnable.ai/incident/cmny9vrt7014vc8nxorhzjl6b Issues with Gmail and Google Calendar Type: Incident 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. Type: Incident

Duration: 1 hour and 17 minutes

Affected Components:

<p><small>Apr <var data-var='date'> 13</var>, <var data-var='time'>10:55:22</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Apr <var data-var='date'> 13</var>, <var data-var='time'>11:02:02</var> GMT+0</small><br><strong>Identified</strong> - Workers using Gmail and Google Calendar are currently not available. We are continuing to work on a fix for this incident..</p> <p><small>Apr <var data-var='date'> 13</var>, <var data-var='time'>12:12:20</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Mon, 13 Apr 2026 10:55:22 +0000 https://status.spinnable.ai/incident/cmnx2thd3006hgyw95qdsj9y0 https://status.spinnable.ai/incident/cmnx2thd3006hgyw95qdsj9y0 Authentication Issues Type: Incident 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. Type: Incident

Duration: 32 minutes

Affected Components:

<p><small>Apr <var data-var='date'> 7</var>, <var data-var='time'>13:38:18</var> GMT+0</small><br><strong>Investigating</strong> - We are experiencing timeouts with our authentication provider. Investigating.</p> <p><small>Apr <var data-var='date'> 7</var>, <var data-var='time'>13:43:40</var> GMT+0</small><br><strong>Monitoring</strong> - The issue has been fixed. We are currently monitoring..</p> <p><small>Apr <var data-var='date'> 7</var>, <var data-var='time'>14:10:11</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Tue, 7 Apr 2026 13:38:18 +0000 https://status.spinnable.ai/incident/cmnonzwve03lhdtjvgkwm2phn https://status.spinnable.ai/incident/cmnonzwve03lhdtjvgkwm2phn Browser Use Unavailable Type: Incident 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. Type: Incident

Duration: 1 hour and 58 minutes

Affected Components:

<p><small>Apr <var data-var='date'> 2</var>, <var data-var='time'>16:00:00</var> GMT+0</small><br><strong>Identified</strong> - We've identified an issue with our browser use provider. We are monitoring the situation.</p> <p><small>Apr <var data-var='date'> 2</var>, <var data-var='time'>17:57:51</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Thu, 2 Apr 2026 16:00:00 +0000 https://status.spinnable.ai/incident/cmnho8bzf07788yl9qs0ej8ti https://status.spinnable.ai/incident/cmnho8bzf07788yl9qs0ej8ti Increased latency & errors Type: Incident 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 Type: Incident

Duration: 7 hours and 14 minutes

Affected Components:

<p><small>Apr <var data-var='date'> 1</var>, <var data-var='time'>14:13:38</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Apr <var data-var='date'> 1</var>, <var data-var='time'>07:00:00</var> GMT+0</small><br><strong>Investigating</strong> - 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..</p> <p><small>Apr <var data-var='date'> 1</var>, <var data-var='time'>10:54:24</var> GMT+0</small><br><strong>Identified</strong> - Our upstream model providers are experiencing degraded performance. We are improving the robustness and monitoring.</p> ]]> Wed, 1 Apr 2026 07:00:00 +0000 https://status.spinnable.ai/incident/cmnfwrjie0933v4ysthsgcvdy https://status.spinnable.ai/incident/cmnfwrjie0933v4ysthsgcvdy Potential issues when executing skills Type: Incident 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. Type: Incident

Duration: 1 hour

Affected Components:

<p><small>Mar <var data-var='date'> 16</var>, <var data-var='time'>09:37:00</var> GMT+0</small><br><strong>Investigating</strong> - We identified an issue where workers might fail to execute skills that require running code. We're working on a fix..</p> <p><small>Mar <var data-var='date'> 16</var>, <var data-var='time'>10:12:00</var> GMT+0</small><br><strong>Identified</strong> - We are still working on a fix..</p> <p><small>Mar <var data-var='date'> 16</var>, <var data-var='time'>10:36:55</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved and the fix will be live in a few moments..</p> ]]> Mon, 16 Mar 2026 09:37:00 +0000 https://status.spinnable.ai/incident/cmmt0w9xz03e5135pojjbx8g5 https://status.spinnable.ai/incident/cmmt0w9xz03e5135pojjbx8g5 Issues with our DB provider Type: Incident 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. Type: Incident

Duration: 15 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 10</var>, <var data-var='time'>09:07:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Mar <var data-var='date'> 10</var>, <var data-var='time'>09:13:52</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>Mar <var data-var='date'> 10</var>, <var data-var='time'>09:18:35</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Mar <var data-var='date'> 10</var>, <var data-var='time'>09:22:17</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Tue, 10 Mar 2026 09:07:00 +0000 https://status.spinnable.ai/incident/cmmkdz6wo08rzk5jdwqldwzly https://status.spinnable.ai/incident/cmmkdz6wo08rzk5jdwqldwzly Issues with WhatsApp messages Type: Incident 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. Type: Incident

Duration: 2 days, 8 hours and 10 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 6</var>, <var data-var='time'>08:33:46</var> GMT+0</small><br><strong>Identified</strong> - We are still working on solving our connection with WhatsApp. Apologies for the disruption..</p> <p><small>Mar <var data-var='date'> 5</var>, <var data-var='time'>19:27:50</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Mar <var data-var='date'> 5</var>, <var data-var='time'>21:05:44</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>Mar <var data-var='date'> 6</var>, <var data-var='time'>20:00:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Thu, 5 Mar 2026 19:27:50 +0000 https://status.spinnable.ai/incident/cmmduyaz816uvdfl688c7uqz1 https://status.spinnable.ai/incident/cmmduyaz816uvdfl688c7uqz1 Issue with scheduled tasks Type: Incident 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. Type: Incident

Duration: 7 hours and 53 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 3</var>, <var data-var='time'>06:30:00</var> GMT+0</small><br><strong>Identified</strong> - Workers might have missed their scheduled tasks in the past hours..</p> <p><small>Mar <var data-var='date'> 3</var>, <var data-var='time'>11:18:17</var> GMT+0</small><br><strong>Monitoring</strong> - 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..</p> <p><small>Mar <var data-var='date'> 3</var>, <var data-var='time'>14:23:15</var> GMT+0</small><br><strong>Resolved</strong> - We'll keep monitoring..</p> ]]> Tue, 3 Mar 2026 06:30:00 +0000 https://status.spinnable.ai/incident/cmmajuqo50ba7tjjsw7nr2xry https://status.spinnable.ai/incident/cmmajuqo50ba7tjjsw7nr2xry Issues with messages with attachments Type: Incident 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. Type: Incident

Duration: 1 day, 2 hours and 30 minutes

Affected Components:

<p><small>Jan <var data-var='date'> 23</var>, <var data-var='time'>07:30:47</var> GMT+0</small><br><strong>Resolved</strong> - We deployed one more fix and are now resolving this. Apologies again for the long disruption of the service..</p> <p><small>Jan <var data-var='date'> 22</var>, <var data-var='time'>05:00:53</var> GMT+0</small><br><strong>Investigating</strong> - 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..</p> <p><small>Jan <var data-var='date'> 22</var>, <var data-var='time'>11:02:52</var> GMT+0</small><br><strong>Identified</strong> - PDF files are also affected. We are continuing to investigate this incident..</p> <p><small>Jan <var data-var='date'> 23</var>, <var data-var='time'>03:17:47</var> GMT+0</small><br><strong>Investigating</strong> - We are still investigating this issue. Apologies for the long duration..</p> <p><small>Jan <var data-var='date'> 23</var>, <var data-var='time'>05:41:02</var> GMT+0</small><br><strong>Monitoring</strong> - 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..</p> ]]> Thu, 22 Jan 2026 05:00:53 +0000 https://status.spinnable.ai/incident/cmkp1urm40473mmgr2zmqyjoh https://status.spinnable.ai/incident/cmkp1urm40473mmgr2zmqyjoh Issues with Hiring Flow Type: Incident 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. Type: Incident

Duration: 4 hours and 18 minutes

Affected Components:

<p><small>Dec <var data-var='date'> 17</var>, <var data-var='time'>09:30:21</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating an issue with the hiring process. Let us know if you have issues hiring workers.</p> <p><small>Dec <var data-var='date'> 17</var>, <var data-var='time'>11:42:19</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Dec <var data-var='date'> 17</var>, <var data-var='time'>13:48:10</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Wed, 17 Dec 2025 09:30:21 +0000 https://status.spinnable.ai/incident/cmj9vsp1100d1m3x59g8zpvli https://status.spinnable.ai/incident/cmj9vsp1100d1m3x59g8zpvli Third-party provider outage Type: Incident 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. Type: Incident

Duration: 1 hour and 38 minutes

Affected Components: ,

<p><small>Nov <var data-var='date'> 24</var>, <var data-var='time'>09:40:00</var> GMT+0</small><br><strong>Identified</strong> - Our database provider is facing issues, which affects our users' ability to log in and use our app..</p> <p><small>Nov <var data-var='date'> 24</var>, <var data-var='time'>11:17:57</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Mon, 24 Nov 2025 09:40:00 +0000 https://status.spinnable.ai/incident/cmicz7xii08r7twjrh3udwf19 https://status.spinnable.ai/incident/cmicz7xii08r7twjrh3udwf19