Dynamic Labs had 25 outages in the last 2 years totaling 1h 32m of downtime — averaging 1 incident per month.
There were 25 Dynamic Labs outages since February 8, 2025 totaling 1h 32m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are investigating an issue with the API and Dashboard.
Dashboard and API services have recovered and we are monitoring.
This incident has been resolved.
We found the root issue and we are reverting a recent change
We implemented a fix and are currently monitoring the result.
Type: Incident Duration: 41 minutes Affected Components: API, SDK Oct 6, 13:40:00 GMT+0 - Resolved - This incident has been resolved. Oct 6, 12:59:00 GMT+0 - Investigating - Related to:
Type: Incident Duration: 13 hours Affected Components: 3rd Party Services Oct 9, 02:04:41 GMT+0 - Postmortem - We are adding more redundancy and alerting on this type of outages Oct 3, 17:00:00 GMT+0 - Resolved - This incident has been resolved. Oct 3, 04:00:00 GMT+0 - Identified - 3rd party provider returned stalled svm data on token holdings
Type: Incident Duration: 1 hour Affected Components: 3rd Party Services, API Sep 17, 11:45:00 GMT+0 - Investigating - We are currently investigating this incident with a downstream provider. Sep 17, 12:45:00 GMT+0 - Resolved - We are continuing to work on a fix for this incident.
Type: Incident Duration: 1 hour and 57 minutes Affected Components: 3rd Party Services, API, SDK Sep 6, 14:40:00 GMT+0 - Investigating - We are currently investigating this incident. Sep 6, 15:55:45 GMT+0 - Identified - We are continuing to work on a fix for this incident. Sep 6, 16:37:00 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 9 minutes Affected Components: API, SDK Aug 28, 15:41:00 GMT+0 - Investigating - Degraded performance across Dynamic API affecting authentication, embedded wallets, etc. Aug 28, 15:50:00 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 1 hour and 36 minutes Affected Components: API, SDK Aug 11, 23:45:00 GMT+0 - Resolved - This incident has been resolved. Aug 11, 22:09:00 GMT+0 - Investigating - We are currently investigating this incident.
We have identified the root cause of the issue and a fix is actively being worked on. We will share another update once the fix has been deployed. Thank you for your patience.
This incident has been resolved.
Type: Incident Affected Components: SDK, API Apr 28, 23:28:26 GMT+0 - Identified - We have identified the root cause of the issue and a fix is actively being worked on. We will share another update once the fix has been deployed. Thank you for your patience.
Type: Incident Duration: 1 day and 11 hours Affected Components: API Apr 4, 03:38:00 GMT+0 - Monitoring - We've identified and resolved an issue with our webhook delivery. Some events may be delayed. A fix has been deployed and we will continue to monitor. Apr 5, 14:38:00 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 15 hours and 43 minutes Affected Components: SDK, API Dec 9, 07:46:22 GMT+0 - Resolved - This incident has been resolved. Dec 8, 16:03:16 GMT+0 - Investigating - We’re aware of an issue affecting email deliverability and our team is actively working to resolve it. Dec 8, 16:20:05 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result.
Type: Incident Duration: 7 hours and 28 minutes Nov 18, 12:00:00 GMT+0 - Identified - Signup, login, wallets and the admin dashboard are affected. Nov 18, 14:00:00 GMT+0 - Identified - Signup and Login are operational for most customers, we are still facing some issues with embedded wallets and the admin dashboard. Nov 18, 14:53:56 GMT+0 - Monitoring - All Dynamic services have been restored, but we are actively monitoring. Nov 18, 19:28:00 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 1 hour and 30 minutes Affected Components: SDK, API Nov 16, 16:30:00 GMT+0 - Resolved - This incident has been resolved. Nov 16, 15:00:00 GMT+0 - Investigating - We are currently investigating this incident. Nov 16, 15:57:00 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result.
Type: Incident Duration: 5 hours and 19 minutes Affected Components: API Oct 31, 17:58:00 GMT+0 - Monitoring - We switched to our backup provider; a few custom email domains on that provider are still not active. We expect these domains to be resolved soon. Oct 31, 17:41:00 GMT+0 - Investigating - We had an email outage from one of our providers Oct 31, 23:00:00 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 3 hours and 6 minutes Affected Components: Website, SDK, API, 3rd Party Services, Dashboard Oct 20, 19:53:30 GMT+0 - Investigating - We are currently investigating this incident. Oct 20, 20:38:12 GMT+0 - Identified - Due to netowrk issues on the AWS clusters we have are suffering from a partial outage Oct 20, 20:45:33 GMT+0 - Monitoring - Due to AWS networking issues, service is partially unavailable, we are working on full restoration. Please see the Status page for more updates. Oct 20, 22:33:17 GMT+0 - Monitoring - AWS anticipate full service restoration by 4:50 PM PDT, we are still working to find alternative remediations in the meantime Oct 20, 22:46:02 GMT+0 - Monitoring - We've implemented a fix and are seeing full service restoration, we'll continue to monitor and update Oct 20, 23:00:00 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 1 hour and 58 minutes Affected Components: API, 3rd Party Services, Dashboard Oct 20, 07:30:00 GMT+0 - Investigating - The known impact is on email service (we switched providers), embedded wallets, and web-hook delivery Oct 20, 07:54:34 GMT+0 - Monitoring - The outage is impacting v3 wallets that don't have an active session Oct 20, 09:27:51 GMT+0 - Resolved - This incident has been resolved.
Type: Incident Duration: 56 minutes Affected Components: API Oct 16, 13:11:00 GMT+0 - Resolved - This incident has been resolved. Oct 16, 12:15:00 GMT+0 - Identified - We are working to resolve the issue with the provider
Type: Incident Duration: 20 minutes Affected Components: API Sep 10, 15:20:00 GMT+0 - Resolved - This incident has been resolved. Sep 10, 15:15:00 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Sep 10, 15:00:00 GMT+0 - Investigating - We are currently investigating this incident.
Type: Incident Duration: 53 minutes Affected Components: 3rd Party Services Jul 18, 15:50:00 GMT+0 - Resolved - This incident has been resolved. Jul 18, 14:57:00 GMT+0 - Identified - We are continuing to work on a fix for this incident.
Type: Incident Duration: 1 day, 1 hour and 13 minutes Affected Components: 3rd Party Services Jun 12, 19:22:04 GMT+0 - Resolved - This incident has been resolved. Jun 11, 18:09:00 GMT+0 - Identified -
Type: Incident Duration: 21 minutes Affected Components: API, SDK Mar 13, 19:31:00 GMT+0 - Resolved - This incident has been resolved. Mar 13, 19:10:00 GMT+0 - Investigating - We are currently investigating this incident.
Type: Incident Duration: 1 hour and 11 minutes Affected Components: API Mar 7, 17:44:00 GMT+0 - Resolved - This incident has been resolved. Mar 7, 17:44:00 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Mar 7, 16:33:00 GMT+0 - Investigating - We are currently investigating this incident.
Type: Incident Duration: 1 hour and 25 minutes Affected Components: API, SDK Feb 18, 19:31:57 GMT+0 - Resolved - This incident has been resolved. Feb 18, 19:31:57 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Feb 18, 18:07:00 GMT+0 - Investigating - We are currently investigating this incident.
Type: Incident Duration: 57 minutes Affected Components: SDK Feb 8, 19:10:00 GMT+0 - Resolved - Coinbase has disclosed a security vulnerability in their Coinbase Wallet SDK affecting their versions >4.0 to <4.3.0. To address this, we've updated the Dynamic SDK to use the patched 4.3.0 version of Coinbase's Wallet SDK. I would appreciate if the team can update to Dynamic SDK v3.9.11+ or v4.5.2+ which moves to their 4.3.0 SDK and addresses the issue. You can read more details here: