BCH Digital Outage History

BCH Digital is up right now

BCH Digital had 8 outages in the last 2 years totaling 4153h 34m of downtime, averaging 0.3 incidents per month.

There were 8 BCH Digital outages since November 28, 2024 totaling 4153h 34m of downtime. Each is summarised below. Incident details, duration, and resolution information.

Source: status.telecomstats.co.uk

Notice July 20, 2026

PCI Transaction Emails

Detected by Pingoru
Jul 20, 2026, 11:51 AM UTC
Resolved
Aug 13, 2026, 11:16 AM UTC
Duration
23d 23h
Affected: 📧 Email
Timeline · 2 updates
  1. monitoring Jul 20, 2026, 11:51 AM UTC

    Our PCI outbound email service was impacted after one of our IP addresses was temporarily listed by Spamhaus. As a result, some emails, including transaction reports and payment notifications, may not have been delivered to recipients. We have successfully removed ourselves from the Spamhaus blocklist as of 20 July 2026 at 11:38 UTC. While the issue has been resolved, it may take some time for mail servers around the world to refresh their blocklist data. During this propagation period, some email delivery delays or rejections may still occur. We will continue to monitor the situation until normal email delivery has resumed across all providers. We appreciate your patience and understanding.

  2. resolved Aug 13, 2026, 11:16 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 26, 2026

Delayed Emails

Detected by Pingoru
Jun 26, 2026, 11:03 AM UTC
Resolved
Jun 30, 2026, 08:48 AM UTC
Duration
3d 21h
Affected: 📧 Email
Timeline · 2 updates
  1. monitoring Jun 26, 2026, 11:03 AM UTC

    Our outbound email service was impacted after one of our IP addresses was temporarily listed by Spamhaus. The IP address was successfully removed from the Spamhaus blocklist on 25 June 2026 at 14:10 UTC. While the issue has been resolved, it may take some time for mail servers around the world to refresh their blocklist data. During this propagation period, some email delivery delays or rejections may still occur. We will continue to monitor the situation until normal email delivery has resumed across all providers. We appreciate your patience and understanding.

  2. resolved Jun 30, 2026, 08:48 AM UTC

    This incident has been resolved.

Read the full incident report →

Major February 9, 2026

Long numbers not receiving messages into the platform.

Detected by Pingoru
Feb 09, 2026, 03:36 PM UTC
Resolved
Jun 26, 2026, 10:59 AM UTC
Duration
136d 19h
Affected: 📱 Long numbers (SMS & Voice)
Timeline · 6 updates
  1. identified Feb 09, 2026, 03:36 PM UTC

    Certain long numbers are not receiving SMS into our platform. This has been identified as a network level issue and raised with the carrier.

  2. identified Feb 10, 2026, 10:56 AM UTC

    Service was briefly restored at 07:56 before failing shortly after. The network are continuing to look into the issue.

  3. identified Feb 10, 2026, 12:25 PM UTC

    Service has been partially restored. There could still be a delay in messages being processed into the platform whilst the network complete their updates.

  4. identified Feb 13, 2026, 10:23 AM UTC

    The network has removed some long numbers from service to apply updates to address the downtime.

  5. monitoring Feb 13, 2026, 03:10 PM UTC

    A fix has been implemented and we are monitoring the results.

  6. resolved Jun 26, 2026, 10:59 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 24, 2025

Call delivery to mobile and landline

Detected by Pingoru
Jul 24, 2025, 01:18 PM UTC
Resolved
Jul 28, 2025, 09:05 AM UTC
Duration
3d 19h
Affected: ☎️ Voice
Timeline · 5 updates
  1. investigating Jul 24, 2025, 01:18 PM UTC

    There is currently widespread issues in the telephony network with delivering calls to mobile networks and some landlines. Inbound calls with onward destinations of any of the below could fail. These include, but are not limited to: Vodafone: Asda Mobile Lebara Talkmobile VOXI EE: Lyca Mobile Utility Warehouse Co-op Mobile O2: giffgaff Sky Mobile Tesco Mobile Three: ID Mobile Smarty BT landlines also appear impacted. Networks across the country are investigating.

  2. investigating Jul 24, 2025, 07:49 PM UTC

    EE/BT confirmed that they have made changes in a effort to restore services. Our network providers are monitoring traffic levels. We will provide a further update as soon as details become available.

  3. monitoring Jul 24, 2025, 07:49 PM UTC

    .

  4. monitoring Jul 25, 2025, 02:16 PM UTC

    EE are continuing to work on restoring services including re-introducing Interconnects. Over the past few hours we have continued to observe small amounts of successful traffic between the network and EE. Our network providers continue to monitor traffic levels. We will provide a further update as soon as details become available.

  5. resolved Jul 28, 2025, 09:05 AM UTC

    This incident has been resolved.

Read the full incident report →

Major May 29, 2025

Cashflows Down

Detected by Pingoru
May 29, 2025, 09:25 AM UTC
Resolved
May 30, 2025, 08:17 AM UTC
Duration
22h 52m
Affected: 💳 Payments
Timeline · 3 updates
  1. investigating May 29, 2025, 09:25 AM UTC

    Cashflows have reported that they are urgently investigating an incident that is affecting transaction processing this morning. Our monitoring has identified that transactions have been receiving a 65550 response since 09:47 BST 29/05. We will provide any further updates once received from Cashflows.

  2. monitoring May 29, 2025, 09:47 AM UTC

    Cashflows have advised that a fix has been implemented and that they are monitoring the results.

  3. resolved May 30, 2025, 08:17 AM UTC

    Cashflows have confirmed that no further issues have been observed.

Read the full incident report →

Major May 29, 2025

Natwest/Monzo Transactions Declining

Detected by Pingoru
May 29, 2025, 09:23 AM UTC
Resolved
May 30, 2025, 10:26 PM UTC
Duration
1d 13h
Affected: 💳 Payments
Timeline · 4 updates
  1. investigating May 29, 2025, 09:23 AM UTC

    We have been made aware of issues affecting some transactions from Natwest/Monzo customers being declined with gateway response (Additional customer authentication required). We've been advised that NatWest Group made some security updates in the early hours of 28/05, which has affected payments for their customers. NatWest are currently working to resolve the issue. We will provide any further updates once received.

  2. identified May 29, 2025, 02:43 PM UTC

    We have now been informed by Cashflows that the root cause of the issue is down to the handling of transactions in relation to 3D Secure / Strong Customer Authentication (SCA). Certain payment methods are exempt from this scheme, including Mail Order Telephone Order (MOTO), however the security change removed the small limit exception and caused the issues experienced. They are actively working on fix for this, and are looking to deploy to their production environment as soon as testing and reviews have been completed.

  3. monitoring May 30, 2025, 11:23 AM UTC

    We have been monitoring transactions this morning and haven't seen any of the "Additional customer authentication required" responses, so it seems Cashflows have managed to resolve the issue, however we have had no official notification at this time. We will continue to monitor throughout the day.

  4. resolved May 30, 2025, 10:26 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 28, 2024

Unable to access portal

Detected by Pingoru
Nov 28, 2024, 03:34 PM UTC
Resolved
Nov 29, 2024, 03:51 PM UTC
Duration
1d
Affected: 📞 Softphone💻 Web Portal
Timeline · 3 updates
  1. investigating Nov 28, 2024, 03:34 PM UTC

    We are getting reports of degraded access to our web portals. This appears to be an wider issue with certain ISPs accessing websites, primarily BT and EE and will monitor for any resolutions they put in place.

  2. investigating Nov 28, 2024, 03:42 PM UTC

    We are continuing to investigate this issue.

  3. resolved Nov 29, 2024, 03:51 PM UTC

    This incident has been resolved.

Read the full incident report →