Is Acquired down?

Last checked just now
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 just now; the most recent incident resolved 3d 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 13 incidents in the last 90 days (96.61% 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 96.61% uptime · past 90 days
Mon Wed Fri
JunJulAugSep
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 19m
    Started Sep 11, 2026, 10:04 AM UTC · Resolved Sep 11, 2026, 10:23 AM UTC
    Payments API
    Timeline · 3 updates
    • investigating · Sep 11, 2026, 10:04 AM UTC

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

    • monitoring · Sep 11, 2026, 10:12 AM UTC

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

    • resolved · Sep 11, 2026, 10:23 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  2. Resolved 22m
    Started Sep 04, 2026, 01:49 AM UTC · Resolved Sep 04, 2026, 02:12 AM UTC
    Payments API
    Timeline · 1 update
    • 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.

    Latest: 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 a…

  3. Resolved 1h 19m
    Started Sep 04, 2026, 01:47 AM UTC · Resolved Sep 04, 2026, 03:07 AM UTC
    Payments APIComponentsHubHosted CheckoutCardsHosted Payment PageCard API
    Timeline · 5 updates
    • investigating · Sep 04, 2026, 01:47 AM UTC

      We are currently investigating elevated failure rates affecting card payments

    • identified · Sep 04, 2026, 02:06 AM UTC

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

    • identified · Sep 04, 2026, 03:01 AM UTC

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

    • monitoring · Sep 04, 2026, 03:07 AM UTC

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

    • resolved · Sep 04, 2026, 03:07 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  4. Resolved 15h 6m
    Started Sep 03, 2026, 04:43 PM UTC · Resolved Sep 04, 2026, 07:49 AM UTC
    Payments APIComponentsHosted CheckoutCardsHosted Payment Page
    Timeline · 4 updates
    • identified · Sep 03, 2026, 04:43 PM UTC

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

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

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

    • resolved · Sep 04, 2026, 07:49 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  5. Resolved 4h 30m
    Started Aug 27, 2026, 01:20 AM UTC · Resolved Aug 27, 2026, 05:50 AM UTC
    Payments API
    Timeline · 2 updates
    • 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.

    • resolved · Aug 27, 2026, 05:50 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

See the full Acquired outage history

7 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Acquired outage history →

Or sign up free to get alerts when Acquired breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 12 incidents View full outage history →