Acquired Outage History

Acquired is up right now

Pingoru has recorded 53 incidents for Acquired: 27 in the last 12 months and 11 in the last 90 days.

Source: acquired.statuspage.io

53incidents recorded
27last 12 months
11last 90 days
3 hourstypical duration
Incidents per month
024AprMayJunJulAugSepOct2
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct6%
Pingoru began tracking Acquired in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 202623 of 744 (0%)
June 202625 of 720 (1%)
July 2026412 of 744 (2%)
August 202648 of 744 (1%)
September 2026415 of 720 (2%)
October 2026229 of 517 (6%)

Incidents, newest first

Minor October 20, 2026 Partial Service Degradation 9h 20m Payments API, Components, Hosted Checkout, Card API

Started Oct 20, 2026, 06:40 AM UTC· resolved Oct 20, 2026, 04:01 PM UTC

  1. identified Oct 20, 2026, 06:40 AM UTC

    We are currently experiencing a partial degradation of service caused by an issue with one of our cloud zones. Our automated failover has activated and our engineering team is actively rerouting traffic to healthy infrastructure. Some customers may experience intermittent errors or increased latency while this takes effect. We will provide a further update shortly.

  2. identified Oct 20, 2026, 07:54 AM UTC

    We are continuing to work on a fix for the issue affecting one of our cloud zones. We will provide a further update within 30 minutes, or sooner if the situation changes.

  3. identified Oct 20, 2026, 08:08 AM UTC

    We are continuing to work on a fix for the issue affecting one of our cloud zones. Webhook delivery has been failing since approximately 07:00 BST. We have now moved webhook services to unaffected infrastructure and are monitoring their recovery. Open banking payments are still affected, and some customers may see failed or delayed open banking payments. We will provide a further update within 30 minutes, or sooner if the situation changes.

  4. identified Oct 20, 2026, 08:37 AM UTC

    We have confirmed that this issue is related to an ongoing incident with our cloud provider, Google Cloud. We are monitoring their progress closely and continuing to mitigate the impact on our services. There is no change to the impact described in our previous update. We will provide a further update within 30 minutes, or sooner if the situation changes.

  5. identified Oct 20, 2026, 09:20 AM UTC

    We have identified additional impact related to this incident: Payouts: Payouts created since approximately 07:00 BST are currently showing as pending. Accounts: The transaction list in Accounts is not currently updating to show recently processed transactions. We are continuing to work on mitigating the impact. The impact described in previous updates remains in place. We will provide a further update within 30 minutes, or sooner if the situation changes.

  6. monitoring Oct 20, 2026, 10:16 AM UTC

    All affected services have now been moved off the impacted cloud zone, which has greatly reduced the impact on our platform. The underlying Google Cloud incident is still ongoing, so this incident remains open while we continue to monitor closely. Customers may still see some intermittent processing issues during this time. We will provide a further update shortly.

  7. monitoring Oct 20, 2026, 03:20 PM UTC

    We're now seeing recovery across the failed cloud zone, and Google Cloud have marked their incident as resolved. We will continue to monitor, but there should be no further impact to service.

  8. resolved Oct 20, 2026, 04:01 PM UTC

    This incident has now been resolved.

Read the full incident report →

Minor October 12, 2026 Cashflows - Visa Processing Issue 19h 24m Payments API

Started Oct 12, 2026, 07:21 PM UTC· resolved Oct 13, 2026, 02:46 PM UTC

  1. investigating Oct 12, 2026, 07:21 PM UTC

    Visa payments (Card, Apple Pay and Google Pay) processed through CashFlows are failing. CashFlows have confirmed an issue on their side. Where possible, we have moved traffic to other acquirers. Merchants who use only CashFlows will see all their Visa payments fail until it’s fixed.

  2. investigating Oct 12, 2026, 07:59 PM UTC

    We are continuing to monitor the disruption affecting Visa payments (Card, Apple Pay and Google Pay) processed through CashFlows. CashFlows are actively investigating and have raised the issue with Visa as a priority. Where alternative acquirers are available, Visa traffic continues to be routed away from CashFlows. Merchants who process solely through CashFlows may still be unable to take Visa payments until service is restored. We will share a further update as soon as we have more information.

  3. identified Oct 12, 2026, 08:26 PM UTC

    CashFlows have identified the cause of the disruption affecting Visa payments (Card, Apple Pay and Google Pay) and are working to restore service. Visa payments processed through CashFlows have been affected since approximately 19:20 BST. Mastercard payments are not affected. Where alternative acquirers are available, Visa traffic continues to be routed away from CashFlows. Merchants who process solely through CashFlows may still be unable to take Visa payments until service is restored. We are monitoring closely and will confirm here once Visa payments are processing successfully again.

  4. identified Oct 12, 2026, 09:04 PM UTC

    CashFlows are continuing to work through recovery steps to restore Visa processing. Visa payments (Card, Apple Pay and Google Pay) processed through CashFlows remain affected. Mastercard payments are not affected. Merchants who process solely through CashFlows may still be unable to take Visa payments until service is restored. We are monitoring closely and will post a further update once Visa payments are processing successfully again.

  5. monitoring Oct 13, 2026, 07:05 AM UTC

    CashFlows have confirmed the fix for the issue affecting Visa payments (Card, Apple Pay and Google Pay). Visa payments have been processing normally since approximately 04:05 BST, and we have seen no further failures since then. We will continue to monitor and will post a final update once the incident is closed. Mastercard payments were not affected.

  6. resolved Oct 13, 2026, 02:46 PM UTC

    This incident has been resolved. Between approximately 19:20 BST on 12 October and 04:05 BST on 13 October, some Visa payments (Card, Apple Pay and Google Pay) processed through CashFlows failed. Mastercard payments were not affected. Since then, Visa payments have processed normally and we have seen no further failures. CashFlows have confirmed the issue is fully resolved and are carrying out a full review of the incident.

Read the full incident report →

Minor September 11, 2026 Elevated Declined Transactions 19m Payments API

Started Sep 11, 2026, 10:04 AM UTC· resolved Sep 11, 2026, 10:23 AM UTC

  1. investigating Sep 11, 2026, 10:04 AM UTC

    We are currently experiencing elevated declined transactions, we are investigating the issue.

  2. monitoring Sep 11, 2026, 10:12 AM UTC

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

  3. resolved Sep 11, 2026, 10:23 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 4, 2026 Elevated error rates on payment processing 22m Payments API

Started Sep 04, 2026, 01:49 AM UTC· resolved Sep 04, 2026, 02:12 AM UTC

  1. investigating Sep 04, 2026, 01:49 AM UTC

    We are investigating an an elevated rate of errors (HTTP 500) from requests to our payments API. Our team is actively working to identify the cause and will share updates as soon as possible.

Read the full incident report →

Minor September 4, 2026 We are currently investigating elevated failure rates affecting card payments 1h 19m Payments API, Components, Hub, Hosted Checkout and 3 more

Started Sep 04, 2026, 01:47 AM UTC· resolved Sep 04, 2026, 03:07 AM UTC

  1. investigating Sep 04, 2026, 01:47 AM UTC

    We are currently investigating elevated failure rates affecting card payments

  2. identified Sep 04, 2026, 02:06 AM UTC

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

  3. identified Sep 04, 2026, 03:01 AM UTC

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

  4. monitoring Sep 04, 2026, 03:07 AM UTC

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

  5. resolved Sep 04, 2026, 03:07 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 3, 2026 3DS & Network Token Issue With Mastercard Transactions 15h 6m Payments API, Components, Hosted Checkout, Cards and 1 more

Started Sep 03, 2026, 04:43 PM UTC· resolved Sep 04, 2026, 07:49 AM UTC

  1. identified Sep 03, 2026, 04:43 PM UTC

    Please be advised that customers may experience intermittent 3DS transaction failures currently via Mastercard.

  2. identified Sep 03, 2026, 05:20 PM UTC

    We are additionally seeing intermittent failures when processing payments which use a Mastercard Network Tokens. We can see the issue originates within the Mastercard system and are awaiting further updates from Mastercard.

  3. monitoring Sep 03, 2026, 09:00 PM UTC

    Mastercard have confirmed that they have implemented a resolution, and we are no longer observing any issues. The impact appears to have been limited to returning customer journeys (Customer Initiated Transactions).

  4. resolved Sep 04, 2026, 07:49 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice August 27, 2026 Degraded card processing via Trust Payments 4h 30m Payments API

Started Aug 27, 2026, 01:20 AM UTC· resolved Aug 27, 2026, 05:50 AM UTC

  1. monitoring Aug 27, 2026, 01:20 AM UTC

    Between 00:25 and 00:48 UTC on 27 August, card transactions routed through one of our acquiring partners did not receive a response and were returned as declined (response code C0101). Transactions via other acquirers were unaffected. Processing recovered at 00:48 UTC and has been normal since. We are monitoring closely and have raised the issue with the partner.

  2. resolved Aug 27, 2026, 05:50 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 18, 2026 Intermittent 3DS issues 41m Card API

Started Aug 18, 2026, 12:16 PM UTC· resolved Aug 18, 2026, 12:58 PM UTC

  1. investigating Aug 18, 2026, 12:16 PM UTC

    We are currently experiencing intermittent issues with our 3DS service. We are investigating the cause and will post timely updates as more information becomes available.

  2. investigating Aug 18, 2026, 12:24 PM UTC

    We believe the issue is related to Lloyds Group and are continuing to investigate the issue.

  3. monitoring Aug 18, 2026, 12:44 PM UTC

    A fix has been implemented and we are monitoring the results. We will provide a further update once we have confirmed full resolution on our end.

  4. resolved Aug 18, 2026, 12:58 PM UTC

    This incident has been resolved.

Read the full incident report →

Major August 15, 2026 Elevated decline rates for Mastercard payments 2h 59m Payments API, Components, Hosted Checkout, Cards and 2 more

Started Aug 15, 2026, 05:29 AM UTC· resolved Aug 15, 2026, 08:29 AM UTC

  1. investigating Aug 15, 2026, 05:29 AM UTC

    We are currently investigating an issue affecting payments processed on the Mastercard network. Affected transactions may be declined or fail to complete. We will provide an update within 30 minutes.

  2. identified Aug 15, 2026, 05:35 AM UTC

    We have confirmed that this is an issue on the Mastercard network affecting transaction processing. Visa and other card schemes are unaffected.

  3. monitoring Aug 15, 2026, 05:38 AM UTC

    Authorisation rates on the Mastercard network have returned to normal levels. We are monitoring to confirm full recovery.

  4. resolved Aug 15, 2026, 08:29 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 13, 2026 Card Processing Issues –

Started Aug 13, 2026, 04:27 AM UTC· resolved Aug 13, 2026, 04:27 AM UTC

  1. resolved Aug 13, 2026, 05:40 AM UTC

    We are currently experiencing issues with 3D Secure authentication affecting card processing due to a failure in a downstream provider. This has caused cardholder present transactions to fail with card not enrolled errors. The upstream provider has recovered as of 06:15, and transactions are flowing successfully again.

Read the full incident report →

Minor July 27, 2026 Open Banking Processing Issues 9h 45m Pay by Bank

Started Jul 27, 2026, 12:49 PM UTC· resolved Jul 27, 2026, 10:34 PM UTC

  1. identified Jul 27, 2026, 12:49 PM UTC

    We have identified processing errors from Barclays, Lloyds Personal, Halifax, and Bank of Scotland for Pay by Bank. To avoid disruption, we have temporarily disabled affected banks on Hosted Checkout. We will provide updates as they become available.

  2. identified Jul 27, 2026, 01:10 PM UTC

    We are now also seeing processing errors affecting Faster Payments for affected banks. Barclays have acknowledged the outage and are investigating. The affected banks remain temporarily disabled on Hosted Checkout. We will provide further updates as they become available.

  3. identified Jul 27, 2026, 06:12 PM UTC

    Barclays have confirmed their Faster Payments queues have cleared and payments are processing as normal. They are continuing work to restore full resilience this evening. Lloyds, Halifax, and Bank of Scotland are reporting normal service and we have re-enabled these banks on Hosted Checkout. Barclays remains temporarily disabled while their Open Banking service continues to report downtime. Payments to Barclays-banked sort codes, including Revolut, may still be rejected. Where a payment has shown as failed today, please do not retry it, as the beneficiary may already have been credited. We will provide updates as they become available.

  4. resolved Jul 27, 2026, 10:34 PM UTC

    Barclays have confirmed their Faster Payments service is fully restored, and we are no longer seeing processing errors on any bank. All banks have been re-enabled on Hosted Checkout.

Read the full incident report →

Major July 23, 2026 Degraded 3DSv2 availability –

Started Jul 23, 2026, 10:16 AM UTC· resolved Jul 23, 2026, 10:16 AM UTC

  1. resolved Jul 23, 2026, 12:15 PM UTC

    We experienced an interruption to our 3DSv2 service between 11:16am and 11:25am, causing card_not_enrolled responses. Our team were immediately alerted, and mitigations were put in place to increase system capacity. Card processing which does not use 3DSv2 (such as MOTO, Recurring, Apple Pay and Cryptogram Google Pay) was not affected.

Read the full incident report →

Critical July 17, 2026 Issue processing 3D Secure enrolment 57m Cards

Started Jul 17, 2026, 05:30 AM UTC· resolved Jul 17, 2026, 06:28 AM UTC

  1. investigating Jul 17, 2026, 06:00 AM UTC

    An issue has been identified in the 3D Secure processing that is causing transactions to be rejected. We're investigating the issue.

  2. investigating Jul 17, 2026, 06:02 AM UTC

    We are continuing to investigate this issue.

  3. monitoring Jul 17, 2026, 06:15 AM UTC

    We have implemented a fix and are monitoring closely.

  4. resolved Jul 17, 2026, 06:28 AM UTC

    The issue has been resolved with processing returned to normal.

Read the full incident report →

Minor July 15, 2026 Mastercard 3D Secure Failures 1h 26m Hosted Payment Page, Card API

Started Jul 15, 2026, 08:01 AM UTC· resolved Jul 15, 2026, 09:28 AM UTC

  1. identified Jul 15, 2026, 08:01 AM UTC

    Card payments requiring 3DS authentication are experiencing elevated declines since 08:00 BST due to an upstream 3DS authentication provider issue; non-3DS flows unaffected; provider engaged.

  2. identified Jul 15, 2026, 08:11 AM UTC

    We have identified that this is only affecting Mastercard transactions. Mastercard have acknowledged a service disruption. We will provide updates as soon as possible.

  3. identified Jul 15, 2026, 08:19 AM UTC

    Customers may experience intermittent authentication failures when attempting Mastercard 3DS-secured transactions. This may result in some transactions being declined or unable to complete authentication. Based on information provided by Mastercard, the issue originates within the Mastercard Identity Check (3DS) service. Mastercard has confirmed they are actively investigating the incident. We are continuing to monitor the situation closely and will provide further updates as more information becomes available from Mastercard.

  4. monitoring Jul 15, 2026, 08:29 AM UTC

    Mastercard 3-D Secure authentication services have recovered, and transaction authentication success rates are back to normal levels. The issue appears to be resolved. We are continuing to monitor the service closely while Mastercard confirms stability on their end. We will post a final update once the incident is confirmed fully resolved.

  5. monitoring Jul 15, 2026, 08:45 AM UTC

    As of 09:10 BST, error volumes have dropped significantly and remained stable. However, authentication success rates have not yet fully returned to expected levels, so we are not marking this as resolved just yet. We will provide a further update as soon as we have confirmation from Mastercard that the issue is fully resolved.

  6. resolved Jul 15, 2026, 09:28 AM UTC

    We have now received confirmation from Mastercard that the 3DS issue has been resolved.

Read the full incident report →

Minor June 7, 2026 Third-party 3D Secure issue affecting some card payments 44m Cards

Started Jun 07, 2026, 12:40 PM UTC· resolved Jun 07, 2026, 01:24 PM UTC

  1. investigating Jun 07, 2026, 12:40 PM UTC

    We are investigating intermittent failures affecting 3D Secure (3DS) authentication on a small proportion of card transactions, caused by an issue with a third-party provider. Most payments are processing normally. Affected transactions may need to be retried. We are working with the provider to resolve this and will post an update shortly.

  2. monitoring Jun 07, 2026, 01:23 PM UTC

    The issue appears to resolved and we are monitoring the results.

  3. resolved Jun 07, 2026, 01:24 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 12, 2026 Potential Issue with Cashflows 3h 15m Payments API

Started May 12, 2026, 01:35 PM UTC· resolved May 12, 2026, 04:50 PM UTC

  1. investigating May 12, 2026, 01:35 PM UTC

    We are currently investigating a potential issue affecting cashflows. We are working to identify the cause and will provide a further update as soon as possible.

  2. identified May 12, 2026, 01:41 PM UTC

    We have confirmed that this is an issue on the part of Cashflows. We have enabled load balancing as a mitigation measure, if you have alternative acquirers available.

  3. monitoring May 12, 2026, 02:10 PM UTC

    Cashflows have confirmed that a fix has been implemented and the issue is now resolved. We have re-enabled Cashflows MIDs and transactions should be processing as normal.

  4. resolved May 12, 2026, 04:50 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 11, 2026 Hub Availability Issue 3m Hub

Started May 11, 2026, 03:08 PM UTC· resolved May 11, 2026, 03:12 PM UTC

  1. investigating May 11, 2026, 03:08 PM UTC

    We are currently investigating an issue affecting the Acquired Hub. Payment processing is not impacted and continues to operate as normal. We will provide further updates as our investigation progresses.

  2. identified May 11, 2026, 03:10 PM UTC

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

  3. monitoring May 11, 2026, 03:12 PM UTC

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

  4. resolved May 11, 2026, 03:12 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 14, 2026 Intermittent PBB Failures –

Started Mar 14, 2026, 11:56 AM UTC· resolved Mar 14, 2026, 11:56 AM UTC

  1. resolved Mar 14, 2026, 01:29 PM UTC

    Pay by bank suffering from internmittent failures / timeouts

Read the full incident report →

Minor February 27, 2026 Service Degradation for Processing Payments 5h 26m Payments API, Components, Hosted Checkout, Hosted Payment Page

Started Feb 27, 2026, 08:14 AM UTC· resolved Feb 27, 2026, 01:41 PM UTC

  1. investigating Feb 27, 2026, 08:14 AM UTC

    We are investigating reports of delayed payment processing. Our team is actively working to identify the cause and will share updates as soon as possible.

  2. investigating Feb 27, 2026, 08:41 AM UTC

    We are continuing to investigate this issue.

  3. investigating Feb 27, 2026, 09:18 AM UTC

    We are continuing to investigate this issue.

  4. investigating Feb 27, 2026, 09:38 AM UTC

    We are continuing to investigate this issue.

  5. investigating Feb 27, 2026, 09:56 AM UTC

    We are continuing to investigate this issue.

  6. investigating Feb 27, 2026, 10:17 AM UTC

    We are continuing to investigate reports of delayed payment processing. We are currently experiencing significantly elevated traffic levels, which are contributing to increased processing latency. As an immediate mitigation, we are scaling additional infrastructure capacity, including CPU and memory resources, to stabilise performance while we continue root cause analysis. No data integrity issues have been identified. We will provide a further update by 10:45 GMT.

  7. investigating Feb 27, 2026, 10:46 AM UTC

    We are continuing to investigate reports of delayed payment processing. We are still experiencing significantly elevated transaction volumes, currently approximately 6–8× normal levels, which have contributed to increased processing latency. We are rolling out two sets of infrastructure upgrades across the server estate to increase available capacity. The first set of changes, which is expected to have the highest performance impact, will complete within the next 15 minutes. A second set of capacity enhancements is also being deployed in parallel and will continue to roll out in a controlled manner to allow traffic to drain and rebalance safely. We are observing performance improvements and will provide a further update by 11:00 GMT.

  8. monitoring Feb 27, 2026, 10:55 AM UTC

    The first phase of infrastructure capacity upgrades has now been successfully completed. Transaction volumes remain elevated but processing performance has returned to expected levels, and we are no longer observing widespread latency. We are continuing to deploy additional capacity enhancements as part of phase two and will closely monitor platform performance. The incident status has now moved to Monitoring while we ensure stability is sustained. We will provide a further update if there are any material changes.

  9. monitoring Feb 27, 2026, 11:51 AM UTC

    We are continuing to monitor for any further issues.

  10. resolved Feb 27, 2026, 01:41 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice February 10, 2026 Service degradation affecting the Hub 7m Hub

Started Feb 10, 2026, 07:27 PM UTC· resolved Feb 10, 2026, 07:35 PM UTC

  1. investigating Feb 10, 2026, 07:27 PM UTC

    We are currently experiencing a service degradation affecting the Hub. Some users may see reduced performance or intermittent issues. Our engineering team is investigating and working to restore normal service as quickly as possible. Further updates will follow.

  2. resolved Feb 10, 2026, 07:35 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor December 16, 2025 Minor Service Degradation –

Started Dec 16, 2025, 12:00 AM UTC· resolved Dec 16, 2025, 12:00 AM UTC

  1. resolved Dec 16, 2025, 01:42 PM UTC

    Issue resolved.

Read the full incident report →

Notice December 10, 2025 Processing issues & the Hub 13m Payments API, Hub

Started Dec 10, 2025, 03:49 PM UTC· resolved Dec 10, 2025, 04:03 PM UTC

  1. investigating Dec 10, 2025, 03:49 PM UTC

    We are currently investigating the issue

  2. monitoring Dec 10, 2025, 03:55 PM UTC

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

  3. resolved Dec 10, 2025, 04:03 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 12, 2025 Service degradation for Trust Payments MIDs 1h 32m Components, Hosted Checkout, Cards, Hosted Payment Page and 1 more

Started Nov 12, 2025, 02:25 PM UTC· resolved Nov 12, 2025, 03:58 PM UTC

  1. investigating Nov 12, 2025, 02:25 PM UTC

    We are currently investigating a service degradation affecting Trust Payments MIDs. Where multiple acquirers are configured, transactions have been automatically rerouted to maintain processing continuity. Merchants with only a Trust Payments MID may experience intermittent transaction errors during this time.

  2. investigating Nov 12, 2025, 02:26 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Nov 12, 2025, 03:30 PM UTC

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

  4. resolved Nov 12, 2025, 03:58 PM UTC

    This service degradation has now been resolved.

Read the full incident report →

Notice October 31, 2025 Service Degradation - Platform Performance 52m Components, Hub, Pay by Bank, Hosted Checkout and 2 more

Started Oct 31, 2025, 09:13 AM UTC· resolved Oct 31, 2025, 10:05 AM UTC

  1. investigating Oct 31, 2025, 09:13 AM UTC

    We are currently investigating reports of degraded performance affecting parts of our platform. Users may experience slower than usual response times or intermittent errors.

  2. monitoring Oct 31, 2025, 09:53 AM UTC

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

  3. monitoring Oct 31, 2025, 10:04 AM UTC

    We are continuing to monitor for any further issues.

  4. resolved Oct 31, 2025, 10:05 AM UTC

    This service degradation has been resolved.

Read the full incident report →

Minor October 29, 2025 Service Degradation – Subset of Reuse and Rebill Transactions 1h 30m Cards

Started Oct 29, 2025, 03:09 PM UTC· resolved Oct 29, 2025, 04:39 PM UTC

  1. investigating Oct 29, 2025, 03:09 PM UTC

    We’re currently investigating an issue affecting a subset of Mastercard reuse and rebill transactions. Some transactions may experience delays or failures during processing. Our team is working to identify the cause and restore full service as soon as possible.

  2. resolved Oct 29, 2025, 04:39 PM UTC

    This incident has been resolved.

Read the full incident report →