Dubber Outage History

Started Sep 11, 2026, 06:24 AM UTC· resolved Sep 15, 2026, 07:23 AM UTC

1. investigating Sep 11, 2026, 06:24 AM UTC

   A small number of customers are experiencing an intermittent issue with calls not being recorded on Microsoft Teams in the Dubber UK1 region. Dubber is working to determine the root cause and a fix for the problem.

2. investigating Sep 11, 2026, 01:40 PM UTC

   A small number of customers are experiencing an intermittent issue with calls not being recorded on Microsoft Teams in the Dubber UK1 region. Dubber is continuing to work to determine the root cause and a fix for the problem.

3. investigating Sep 14, 2026, 01:44 AM UTC

   For most customers the issue has been resolved with a smaller subset still experiencing intermittent issues. We are continuing to investigate this in conjunction with Microsoft.

4. resolved Sep 15, 2026, 07:23 AM UTC

   Dubber and Microsoft have concluded their investigation and found no issues with Dubber’s recording service. Customers who continue to experience this issue should raise a support ticket directly with Microsoft.

Read the full incident report →

Started Jun 30, 2026, 10:19 AM UTC· resolved Jun 30, 2026, 02:06 PM UTC

1. investigating Jun 30, 2026, 10:19 AM UTC

   We are currently investigating an issue affecting the Dubber Pause and Resume functionality within the Microsoft Teams app. At this time: - Call recording services remain fully operational - Recording bots are not impacted - Only the Pause/Resume controls within the Teams app are affected Users may experience unexpected behaviour when accessing the pause or app via the Teams interface. For our customers using the pause & resume app for on-demand recording, as a temporary workaround, you can enable the 'Auto start recording' tenant setting via our provisioning app - teams.emea.dubber.net (Please note it can take 1 hour for the changes to apply) Our teams are actively working to identify the root cause and restore full functionality as quickly as possible. Further updates will be provided as more information becomes available.

2. investigating Jun 30, 2026, 11:07 AM UTC

   We are continuing to investigate this issue.

3. investigating Jun 30, 2026, 01:26 PM UTC

   The issue has been escalated to Microsoft Support. We will keep you informed and share updates as soon as more information becomes available

4. identified Jun 30, 2026, 01:52 PM UTC

   The issue has been identified, and configuration updates are in progress to restore the pause/resume functionality.

5. resolved Jun 30, 2026, 02:06 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 26, 2026, 08:37 AM UTC· resolved Jul 03, 2026, 07:46 AM UTC

1. investigating Jun 26, 2026, 08:37 AM UTC

   Dubber are currently investigating an incident impacting customer payment services.

2. identified Jun 26, 2026, 09:13 AM UTC

   We have identified an issue in Dubber Site 1 and are currently working to restore service. We will provide another update in the next 20 minutes.

3. identified Jun 26, 2026, 09:35 AM UTC

   We are continuing to restore service. We will provide another update in the next 20 minutes.

4. identified Jun 26, 2026, 09:59 AM UTC

   Service has now been partially restored. Our teams are continuing to work toward full service restoration. We will share another update within the next 20 minutes.

5. identified Jun 26, 2026, 10:25 AM UTC

   Service has now been partially restored. Our teams are continuing to work toward full service restoration. We will share another update within the next 20 minutes

6. identified Jun 26, 2026, 10:46 AM UTC

   Service has now been partially restored. Our teams are continuing to work toward full service restoration. We will share another update within the next 20 minutes

7. identified Jun 26, 2026, 11:16 AM UTC

   The majority of the service has now been restored. Our teams are continuing to work toward full service restoration. We will share another update within the next 20 minutes

8. identified Jun 26, 2026, 12:21 PM UTC

   The majority of the service has now been restored. Our teams are continuing to work toward full service restoration. We will share another update within the next 30 minutes

9. identified Jun 26, 2026, 12:51 PM UTC

   The majority of the service has now been restored. Our teams are continuing to work toward full service restoration. We will share another update within the next 30 minutes.

10. monitoring Jun 26, 2026, 01:16 PM UTC

    The application side of the service has now been fully restored, and any impact to new telephone calls has been mitigated. However, some issues may still affect calls that were in progress prior to 14:00. We will provide a further update in 30 minutes.

11. monitoring Jun 26, 2026, 01:59 PM UTC

    We can see that the majority of calls in Site 1 have now completed, with the remaining traffic successfully routing through Site 2. We will continue to monitor the situation and provide a further update in 30 minutes.

12. monitoring Jun 26, 2026, 02:24 PM UTC

    The impact has now been fully mitigated across both the application and telephony services. Call handling and payment processing are operating normally, with transactions completing successfully. We have stabilised the service by routing traffic through our secondary (Site 2) data centre. This will remain our active operating environment throughout the weekend while we carry out a thorough assessment of Site 1 and determine the necessary remedial actions. We will continue to closely monitor performance and provide further updates as required.

13. monitoring Jun 27, 2026, 09:36 AM UTC

    We have been closely monitoring the service following yesterday’s restoration, and it remains stable, with calls and payments being processed at expected levels. We will continue to monitor the service and provide updates as needed.

14. monitoring Jun 29, 2026, 08:44 AM UTC

    We have continued to closely monitor the platform throughout the weekend, and all services have remained stable. Call handling and payment processing have been completing successfully without any issues. Traffic is currently being handled by Site 2, which is our primary data centre and continues to operate as normal with no impact to performance or reliability. We are preparing for repairs to Site 1. This is expected to be completed by the middle of this week. We will continue to monitor the service closely and provide further updates as required. The next status update will be tomorrow morning.

15. monitoring Jun 30, 2026, 08:55 AM UTC

    We are continuing to monitor the platform closely, and all services continue to remain stable. Traffic continues to be handled by Site 2, operating as normal with no impact to performance or reliability. We are proceeding with work to complete repairs to Site 1, this is expected to be completed by the end of this week. We will continue to monitor the service closely and provide further updates as required. The next status update will be tomorrow morning.

16. monitoring Jul 01, 2026, 10:27 AM UTC

    We are continuing to monitor the platform closely, and all services continue to remain stable. Traffic continues to be handled by Site 2, operating as normal with no impact to performance or reliability. We are proceeding with work to complete repairs to Site 1, this is expected to be completed by the end of this week. We will continue to monitor the service closely and provide further updates as required. The next status update will be tomorrow morning.

17. monitoring Jul 02, 2026, 03:05 PM UTC

    Repairs to Site 1 have now been completed. As part of the restoration process, we will be bringing the Site 1 SBCs back into service this evening. This will restore service capability within Site 1 and return platform resilience to normal business-as-usual operation. The activity is scheduled to take place between 20:00 and 22:00. We do not anticipate any customer impact during this activity; however, we will continue to monitor the platform closely throughout the change. Further updates will be provided as required. The next scheduled update will be issued tomorrow.

18. resolved Jul 03, 2026, 07:46 AM UTC

    The planned activity to return the Site 1 SBCs to service was completed successfully within the scheduled maintenance window. Site 1 is now actively handling call traffic again, restoring full service capability at the site and returning platform resilience to normal business-as-usual operation. No customer impact was observed during the change, and we will continue to monitor the platform closely as part of our post-restoration checks. We would like to thank customers for their patience and cooperation throughout this incident. In addition, we will be following up directly with affected customers regarding any customer-specific actions, observations, or additional requirements arising from this event. This incident is now considered resolved. Further communications will be provided directly where customer-specific follow-up is required.

Read the full incident report →

Started Jun 23, 2026, 12:40 PM UTC· resolved Jun 23, 2026, 02:17 PM UTC

1. monitoring Jun 23, 2026, 12:40 PM UTC

   Between approximately 12:45 and 13:15, we observed a brief issue impacting our Site 1 data center, related to our data centre supplier. This may have caused a short interruption to calls passing through that site. Services have since recovered. Site 2 remained unaffected. We are continuing to monitor.

2. resolved Jun 23, 2026, 02:17 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 26, 2026, 05:53 PM UTC· resolved May 26, 2026, 06:45 PM UTC

1. investigating May 26, 2026, 05:53 PM UTC

   Dubber is currently investigating an issue logging into the US and Canadian Dubber Portal. We will investigate this and resolve as quickly as possible.

2. investigating May 26, 2026, 05:53 PM UTC

   We are continuing to investigate this issue.

3. investigating May 26, 2026, 06:27 PM UTC

   Dubber is continuing to investigate the login issues for US and Canadian Dubber portals.

4. resolved May 26, 2026, 06:45 PM UTC

   This was just a limited issue and has been fully resolved. US and CA portals can be accessed with no issues.

Read the full incident report →

Started May 12, 2026, 02:53 PM UTC· resolved May 12, 2026, 03:30 PM UTC

1. investigating May 12, 2026, 02:53 PM UTC

   We are currently investigating reports of errors being returned from the US API. Recording & portal availability is not impacted.

2. identified May 12, 2026, 03:13 PM UTC

   We have identified an issue and are working on a resolution.

3. resolved May 12, 2026, 03:30 PM UTC

   The issue has now been resolved, and we will continue to monitor.

Read the full incident report →

Started Feb 25, 2026, 12:17 AM UTC· resolved Feb 25, 2026, 11:43 AM UTC

1. investigating Feb 25, 2026, 12:17 AM UTC

   We are currently investigating an issue affecting Dubber's Microsoft Teams Pause & Resume App. The issue is not impacting the desktop client however the browser version is unavailable. Call recording is NOT impacted by this incident, only the Pause & Resume app.

2. resolved Feb 25, 2026, 11:43 AM UTC

   A fix has been deployed to all regions, the browser version of the Pause and Resume App is now functioning as expected.

Read the full incident report →

Started Nov 18, 2025, 02:21 PM UTC· resolved Nov 18, 2025, 05:44 PM UTC

1. monitoring Nov 18, 2025, 02:21 PM UTC

   Dubber are aware of a Cloudflare incident which is impacting access to the Dubber portal. Cloudflare are aware of the issues and are working to resolve the problems. Dubber will periodically provide updates on the Cloudflare issues which can also be seen here: https://www.cloudflarestatus.com/

2. resolved Nov 18, 2025, 05:44 PM UTC

   Dubber has continued to monitor our portal interfaces and we are seeing no issues accessing Dubber portals and we are satisfied that Cloudflare has resolved the issue and this issue is being closed.

Read the full incident report →

Started Nov 17, 2025, 01:12 AM UTC· resolved Dec 01, 2025, 08:20 AM UTC

1. identified Nov 17, 2025, 01:12 AM UTC

   We are aware of an issue where Dubber recording bots are appearing as participants in Microsoft Teams meetings. Our investigation confirms this behaviour is not caused by Dubber. We have reported the issue to Microsoft, who are currently investigating the cause. Recording and playback functionality remain fully operational and are not impacted.

2. resolved Dec 01, 2025, 08:20 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 20, 2025, 09:54 AM UTC· resolved Oct 21, 2025, 07:19 AM UTC

1. monitoring Oct 20, 2025, 09:54 AM UTC

   Dubber are aware of an ongoing AWS incident, see https://health.aws.amazon.com/health/status for details. This may be impacting Dubber services in the US-East region, and we therefore recommend that partners in this region with redundancy in place failover to another region. Dubber are continuing to monitor the situation closely.

2. monitoring Oct 20, 2025, 02:30 PM UTC

   Dubber are continuing to monitor the ongoing AWS incident.

3. resolved Oct 21, 2025, 07:19 AM UTC

   AWS have confirmed their incident to be resolved.

Read the full incident report →

Started Aug 11, 2025, 08:36 PM UTC· resolved Aug 12, 2025, 12:30 AM UTC

1. investigating Aug 11, 2025, 08:36 PM UTC

   Dubber is investigating an issue with recording playback for the US East Coast BroadWorks accounts. Will investigate and provide updates as they are obtained. We are aware of this problem and are working to identify and resolve this problem.

2. investigating Aug 11, 2025, 09:03 PM UTC

   Dubber is continuing to investigate the issues regarding call playback for BroadWorks customers in the US East.

3. investigating Aug 11, 2025, 09:14 PM UTC

   We continue to review and troubleshoot. We are aware that Playback AND recording download are currently impacted.

4. investigating Aug 11, 2025, 09:45 PM UTC

   As we continue working this issue we understand the impact is being felt in the US Dubber portal generally and not limited in scope to BroadWorks accounts. We are aware of the issues downloading and playing recordings back. We are identifying the root cause and taking actions to correct this issue. Please continue to monitor the status page for updates on this issue.

5. identified Aug 11, 2025, 10:46 PM UTC

   Dubber has identified the issue causing the delayed processing of recording files and has taken corrective actions to clear this backlog which has already reduced by 33%. Dubber is continuing to review ways to expedite the clearing of the backlog.

6. resolved Aug 12, 2025, 12:30 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 04, 2025, 07:23 PM UTC· resolved Aug 04, 2025, 10:54 PM UTC

1. investigating Aug 04, 2025, 07:23 PM UTC

   Dubber is investigating an issue with our technology partner relating to an API outage. We are following updates from our partner and will provide more details as they are given.

2. identified Aug 04, 2025, 08:00 PM UTC

   Dubber's customer facing API services are currently being impacted by an outage on our partner's platform. Dubber is monitoring the situation and will provide updates and guidance as we receive them.

3. identified Aug 04, 2025, 08:13 PM UTC

   The issue we are experiencing at the moment is an interruption with our API gateway causing issues accessing Dubber platform via api.dubber.net. Recording is not impacted and recording playback is fine via the Dubber portal itself. Recordings are not impact We will continue to work with our partner and will provide updates as we receive them.

4. identified Aug 04, 2025, 08:21 PM UTC

   Our API Partner has identified their issue and is implementing a fix, we will closely monitor their progress and provide updates.

5. monitoring Aug 04, 2025, 09:33 PM UTC

   Our partner has implemented a fix and is seeing recovery in some regions. They are continuing to work to mitigate the API issues for all impacted regions. Dubber confirms we can see items recovering and backlogs processing. We will continue to monitor for updates.

6. resolved Aug 04, 2025, 10:54 PM UTC

   Our API partner has resolved their issue and have resumed normal service. Dubber systems are processing through a backlog of items but we also confirm that everything is operational with this partner from our perspective. This issue is resolved and Dubber will continue to monitor our partner's performance. Recordings were not impacted in any way. API functions have returned to normal.

Read the full incident report →

Started Jul 25, 2025, 07:41 AM UTC· resolved Jul 25, 2025, 08:54 AM UTC

1. investigating Jul 25, 2025, 07:41 AM UTC

   Dubber are aware of a problem that may be impacting the ability to process calls and payments. We are investigating as a matter of urgency and will provide regular updates.

2. identified Jul 25, 2025, 08:11 AM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring Jul 25, 2025, 08:27 AM UTC

   A fix has been implemented and the issue looks to be resolved. We will be closely monitoring for at least the next 30 minutes and will provide further updates in due course.

4. resolved Jul 25, 2025, 08:54 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 16, 2025, 09:16 PM UTC· resolved Jul 17, 2025, 06:16 AM UTC

1. investigating Jul 16, 2025, 09:16 PM UTC

   We are investigating reports that recordings have stopped updating in the US Dubber portal. We will provide more detail when this has been identified.

2. investigating Jul 16, 2025, 09:48 PM UTC

   Dubber is continuing to work to identify the issues impacting the US Dubber portal accounts. We will identify and remedy the issues as swiftly as possible

3. monitoring Jul 16, 2025, 10:04 PM UTC

   We found the problem and have taken corrective action. We can see call recordings resuming in the US and we will continue to monitor the nodes to verify this issue has been rectified.

4. resolved Jul 17, 2025, 06:16 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 08, 2025, 02:46 PM UTC· resolved Jul 08, 2025, 05:14 PM UTC

1. investigating Jul 08, 2025, 02:46 PM UTC

   We are aware that some customers in the US Region are experiencing delaying in call recordings being available in the Dubber portal. We are investigating this incident and will provide further details as we have them.

2. investigating Jul 08, 2025, 03:13 PM UTC

   We are continuing to investigate this incident. We will provide further updates when we have them.

3. identified Jul 08, 2025, 04:02 PM UTC

   The issue has been identified and Dubber is working towards a resolution. We can confirm that all call records have been captured, there have been no loss of call recordings.

4. identified Jul 08, 2025, 05:14 PM UTC

   We are continuing to work on a fix for this issue.

5. resolved Jul 08, 2025, 05:14 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 01, 2025, 05:48 PM UTC· resolved Jul 01, 2025, 06:44 PM UTC

1. investigating Jul 01, 2025, 05:48 PM UTC

   We are currently investigating an issue accessing the Insights dashboard in the US Dubber portal. We are aware of this and will be identifying and correcting the issue. Will update. This appears to be limited to the US Region only.

2. resolved Jul 01, 2025, 06:44 PM UTC

   We had a minor issue that limited access to our Insights dashboard in the US region briefly and this has been corrected and is now back in full operation.

Read the full incident report →

Started Jun 25, 2025, 01:09 PM UTC· resolved Jul 04, 2025, 02:54 PM UTC

1. investigating Jun 25, 2025, 01:09 PM UTC

   We are aware that some customers are experiencing issues with playing calls back in the in the Dubber portal. We are working to resolve the incident as soon as possible and will provide regular updates.

2. investigating Jun 25, 2025, 02:23 PM UTC

   We are aware that some customers are experiencing issues with playing calls back in the in the Dubber portal. We are working to resolve the incident as soon as possible and will provide regular updates.

3. investigating Jun 25, 2025, 03:28 PM UTC

   We are aware that some customers are experiencing issues with playing calls back in the in the Dubber portal. We are working to resolve the incident as soon as possible and will provide regular updates.

4. identified Jun 25, 2025, 05:35 PM UTC

   The issue has been identified and Dubber is working to correct the problems, we will continue to work on this to return to normal operation. We will continue to provide updates as they are available.

5. identified Jun 25, 2025, 07:35 PM UTC

   Work continues on this playback issue, our team is working to fully resolve this problem and to return to normal service as soon as possible.

6. identified Jun 26, 2025, 05:43 AM UTC

   Dubber is continuing remediation work on this incident. We will continue to provide updates on this status page.

7. identified Jun 26, 2025, 02:37 PM UTC

   Dubber is continuing remediation work on this incident. We will continue to provide updates on this status page.

8. monitoring Jun 26, 2025, 04:47 PM UTC

   Dubber has identified the issue and we have taken corrective measures to return to a full operational mode across the impacted regions. Dubber will be monitoring the performance to verify this issue is fully resolved and will provide additional information once we conclude our review.

9. resolved Jul 04, 2025, 02:54 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 05, 2025, 06:07 PM UTC· resolved Jun 06, 2025, 12:34 AM UTC

1. investigating Jun 05, 2025, 06:07 PM UTC

   We are aware of a slow down or degraded performance in the postings of call recordings to user accounts and are investigating at this time. There is no evidence that this is impacting call recording itself it is just a delayed posting of recordings at this time. We will update with further information as we investigate this.

2. identified Jun 05, 2025, 06:29 PM UTC

   Update, we have confirmed recordings continue to be processed normally however we are working on the backlog of recordings that has built up. We are working to expedite the processing of these queued up recordings to catch back up to near real time. We will update as this progresses

3. identified Jun 05, 2025, 07:09 PM UTC

   Update, we are working to improve the performance of Dubber portal to bring the backlog back under control. Our team is engaged and working on this. Recordings continue to happen without impact based on all available feedback and we see the backlog of recordings and are monitoring those queues and our server performance. Thanks for your patience

4. monitoring Jun 05, 2025, 07:40 PM UTC

   We have implemented some fixes to resolve the problem and we are watching the backlog of recordings trend downwards. This issue will resolve given time. We are continuing to monitor the performance and we are taking additional steps to expedite this recovery. Thanks again for your patience. Note, it is possible during this recovery process that recordings might appear in user accounts but for a short period might not be play-able this is a normal process and will also correct itself during this recovery period.

5. monitoring Jun 05, 2025, 08:34 PM UTC

   We continue to monitor the recovering of the platform and the backlog of pending recordings is moving downwards as expected. This issue will be all caught up in the coming hours and we will continue to keep an eye on it until the backlog is completely resolved.

6. resolved Jun 06, 2025, 12:34 AM UTC

   We have restored service and recordings are appearing in the portal for playback. A small number of customers may still experience slight delays for the next few hours.

Read the full incident report →

Started Apr 01, 2025, 09:22 AM UTC· resolved Apr 01, 2025, 10:03 AM UTC

1. investigating Apr 01, 2025, 09:22 AM UTC

   Dubber is aware of an issue intermittently impacting MS Teams call initiation which we are currently investigating. Please note recording is not impacted.

2. investigating Apr 01, 2025, 09:23 AM UTC

   We are continuing to investigate this issue.

3. resolved Apr 01, 2025, 10:03 AM UTC

   This incident is now resolved and MS Teams calls are now initiating as expected.

4. postmortem Apr 01, 2025, 03:11 PM UTC

   After investigation, and liaising with Microsoft, Microsoft confirmed they experienced a power event in the North Europe region, which impacted their services in this region. Microsoft have confirmed that power and services were fully restored.

Read the full incident report →

Started Mar 17, 2025, 01:06 PM UTC· resolved Mar 17, 2025, 01:50 PM UTC

1. investigating Mar 17, 2025, 01:06 PM UTC

   Dubber is aware of an SSO issue impacting portal access which we're currently investigating. Please note recording of calls is not impacted.

2. investigating Mar 17, 2025, 01:18 PM UTC

   We are continuing to investigate this issue.

3. resolved Mar 17, 2025, 01:50 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 17, 2025, 10:29 PM UTC· resolved Feb 18, 2025, 01:18 AM UTC

1. investigating Feb 17, 2025, 10:29 PM UTC

   Dubber is investigating delays of call recordings appearing in the Dubber portal in our US and CA regions. We are continuing to capture recordings.

2. resolved Feb 18, 2025, 01:18 AM UTC

   We have resolved the incident with call recordings now appearing in the portal within usual timeframes. If you continue to experience issues please contact Dubber Support.

Read the full incident report →

Started Feb 17, 2025, 05:51 AM UTC· resolved Feb 17, 2025, 06:38 AM UTC

1. investigating Feb 17, 2025, 05:51 AM UTC

   We are aware that some customers using Dubber on Microsoft Teams are experiencing delays in accessing recordings. Please be assured that calls are being recorded and all recordings will be available once the incident is resolved. We are working to resolve the incident as soon as possible and will provide regular updates.

2. resolved Feb 17, 2025, 06:38 AM UTC

   Dubber has restored service with calls appearing in the Dubber portal as expected. If you continue to experience service difficulties please contact Dubber support for assistance.

Read the full incident report →

Started Feb 12, 2025, 06:40 PM UTC· resolved Feb 12, 2025, 08:35 PM UTC

1. investigating Feb 12, 2025, 06:40 PM UTC

   We have had reports of call recording issues between MS Teams and Dubber. We are exploring this issue with priority and will work to resolve this in the shortest time possible.

2. investigating Feb 12, 2025, 07:00 PM UTC

   We are continuing to investigate the issue. This has been escalated and the required engineering teams are enguaged.

3. monitoring Feb 12, 2025, 07:37 PM UTC

   We have taken action to address the incident and currently monitoring the systems.

4. monitoring Feb 12, 2025, 08:11 PM UTC

   The team are continuing to investigate with the highest priority.

5. resolved Feb 12, 2025, 08:35 PM UTC

   Our monitoring is indicating the incident is resolved. We are continuing to monitor systems.

Read the full incident report →

Started Jan 30, 2025, 05:32 AM UTC· resolved Jan 30, 2025, 05:58 AM UTC

1. investigating Jan 30, 2025, 05:32 AM UTC

   We are aware that some customers are experiencing issues accessing the Dubber portal. Please be assured that this incident is impacting portal access only and that calls are being recorded. We are working to resolve the incident as soon as possible and will provide regular updates.

2. resolved Jan 30, 2025, 05:58 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 28, 2024, 11:16 AM UTC· resolved Nov 28, 2024, 11:32 AM UTC

1. investigating Nov 28, 2024, 11:16 AM UTC

   We are investigating an incident that is impacting the Payment Services for some customer. We are working to resolve the incident as soon as possible and will provide regular updates.

2. investigating Nov 28, 2024, 11:30 AM UTC

   We are continuing to investigate this issue.

3. resolved Nov 28, 2024, 11:32 AM UTC

   Corrective actions as been completed and we believed the incident is resolved. We are continuing to monitor verify payments are working as expected.

Read the full incident report →