Dubber experienced a major incident on June 26, 2026 affecting Payment Services, lasting 6d 23h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jun 26, 2026, 08:37 AM UTC
Dubber are currently investigating an incident impacting customer payment services.
- 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.
- identified Jun 26, 2026, 09:35 AM UTC
We are continuing to restore service. We will provide another update in the next 20 minutes.
- 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.
- 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
- 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
- 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
- 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
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.