Is Acquired down?

Last checked 11m ago
Current status
Acquired is up

No incidents right now.

Official status page: https://acquired.statuspage.io · Polled every 5 minutes · 10 components tracked

Acquired is operational right now. Last checked 11m ago; the most recent incident resolved 6d ago.

Real-time Acquired status, recent outages, and incident history — pulled directly from Acquired's official status page at https://acquired.statuspage.io every 5 minutes. Pingoru tracks 10 Acquired services and has captured 6 incidents in the last 90 days (99.56% uptime). Get email, Slack, Discord, or webhook alerts the moment Acquired reports a new incident — free for 5 monitors, no credit card.

Users who monitor Acquired also follow these eCommerce services: Shopify Stripe PayPal Blackbaud NetSuite Squarespace BigCommerce Cybersource Gorgias PayFast View all 6,000+ providers
Acquired uptime 99.56% uptime · past 90 days
Mon Wed Fri
MarAprMayJun
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 44m
    Started Jun 07, 2026, 12:40 PM UTC · Resolved Jun 07, 2026, 01:24 PM UTC
    Cards
    Timeline · 3 updates
    • 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.

    • monitoring · Jun 07, 2026, 01:23 PM UTC

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

    • resolved · Jun 07, 2026, 01:24 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  2. Resolved 4h
    Started Jun 03, 2026, 10:49 AM UTC · Resolved Jun 03, 2026, 02:49 PM UTC
    Pay by Bank
    Timeline · 3 updates
    • identified · Jun 03, 2026, 10:49 AM UTC

      Our team has identified processing errors occuring for Lloyds Personal, Halifax, and Bank of Scotland banks. We will update you shortly on progress.

    • identified · Jun 03, 2026, 10:55 AM UTC

      To prevent further failed transactions, we have temporarily disabled affected banks on Hosted Checkout. This is due to intermittent API response errors from the bank's connection. We are in communication with the affected bank and will provide updates as they become available.

    • resolved · Jun 03, 2026, 02:49 PM UTC

      Lloyds have resolved the issue on their end, and Pay by Bank transactions through Lloyds group banks are processing as normal.

    Latest: Lloyds have resolved the issue on their end, and Pay by Bank transactions through Lloyds group banks are processing as normal.

  3. Resolved 3h 15m
    Started May 12, 2026, 01:35 PM UTC · Resolved May 12, 2026, 04:50 PM UTC
    Payments API
    Timeline · 4 updates
    • 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.

    • 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.

    • 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.

    • resolved · May 12, 2026, 04:50 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  4. Resolved 3m
    Started May 11, 2026, 03:08 PM UTC · Resolved May 11, 2026, 03:12 PM UTC
    Hub
    Timeline · 4 updates
    • 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.

    • identified · May 11, 2026, 03:10 PM UTC

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

    • monitoring · May 11, 2026, 03:12 PM UTC

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

    • resolved · May 11, 2026, 03:12 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

Outage history

Past 90 days · 4 incidents View full outage history →