Spreedly Outage History

Spreedly is up right now

Spreedly had 19 outages in the last 2 years totaling 52h 34m of downtime — averaging 0.8 incidents per month.

There were 19 Spreedly outages since August 20, 2025 totaling 52h 34m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: http://status.spreedly.com

Minor July 11, 2026

Intermittent 500 Errors on List and Show Endpoints

Detected by Pingoru
Jul 11, 2026, 02:33 PM UTC
Resolved
Jul 11, 2026, 03:38 PM UTC
Duration
1h 4m
Affected: Core Transactional API
Timeline · 2 updates
  1. investigating Jul 11, 2026, 02:33 PM UTC

    We are investigating elevated error rates affecting certain API requests. Some list and retrieval endpoints may return intermittent 500 responses while we work to identify the root cause.

  2. resolved Jul 11, 2026, 03:38 PM UTC

    We identified and resolved the issue causing intermittent 500 responses on certain list and retrieval endpoints. A configuration update has been deployed to prevent requests from being prematurely terminated, and we are continuing to monitor the service.

Read the full incident report →

Minor July 8, 2026

Degraded performance on Cybersource Credit transactions

Detected by Pingoru
Jul 08, 2026, 03:22 PM UTC
Resolved
Jul 08, 2026, 04:54 PM UTC
Duration
1h 32m
Affected: Core Transactional API
Timeline · 3 updates
  1. investigating Jul 08, 2026, 03:22 PM UTC

    Spreedly has detected an issue potentially resulting in degraded performance on Cybersource Credit transactions. While we are providing this early notification in an effort to alert you as quickly as possible, we are still investigating the actual scope and impact. We will provide an update as soon as more details are available.

  2. identified Jul 08, 2026, 04:08 PM UTC

    We have identified transient internal DNS resolution error that occurred between 15:00 and 15:05 UTC causing select 500 errors across Spreedly services. We continue to investigate the full impact and will provide additional information as it becomes available.

  3. resolved Jul 08, 2026, 04:54 PM UTC

    After closely monitoring and confirming that all systems are stabilized and functioning as expected, this incident is considered resolved. No further customer impact is expected. We are completing our investigation concerning the causes of the incident and any residual impact. We apologize for any inconvenience or disruption.

Read the full incident report →

Notice May 8, 2026

Elevated Latency Dodgeball Platform

Detected by Pingoru
May 08, 2026, 06:00 PM UTC
Resolved
May 08, 2026, 06:05 PM UTC
Duration
5m
Affected: Dodgeball
Timeline · 2 updates
  1. monitoring May 08, 2026, 06:00 PM UTC

    A fix has been implemented and we are monitoring results.

  2. resolved May 08, 2026, 06:05 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 19, 2026

Dodgeball Checkpoint Latency

Detected by Pingoru
Mar 19, 2026, 03:13 PM UTC
Resolved
Mar 19, 2026, 04:09 PM UTC
Duration
55m
Affected: Dodgeball
Timeline · 5 updates
  1. identified Mar 19, 2026, 03:13 PM UTC

    We are currently investigating performance of the Dodgeball service.

  2. identified Mar 19, 2026, 03:30 PM UTC

    We are working to resolve an issue with delayed processing of requests to the Dodgeball services.

  3. monitoring Mar 19, 2026, 03:55 PM UTC

    We’ve implemented a fix and stabilized the Dodgeball component that was experiencing a partial outage. We are continuing to monitor

  4. monitoring Mar 19, 2026, 04:07 PM UTC

    After closely monitoring and confirming that all systems are stabilized and functioning as expected, this incident is considered resolved. No further customer impact is expected. We apologize for any inconvenience or disruption.

  5. resolved Mar 19, 2026, 04:09 PM UTC

    This incident has been resolved.

Read the full incident report →

Major February 26, 2026

Dodgeball Production Instance Storage Critically Low

Detected by Pingoru
Feb 26, 2026, 04:45 PM UTC
Resolved
Feb 26, 2026, 06:44 PM UTC
Duration
1h 58m
Affected: Dodgeball
Timeline · 3 updates
  1. investigating Feb 26, 2026, 04:45 PM UTC

    We are currently investigating an issue affecting customers using Dodgeball. The production database backing Dodgeball has reached critically low available storage, which is expected to result in elevated error rates. Customers may begin experiencing errors within the next 10 minutes as the system’s ability to process requests degrades. Our engineering team is actively investigating and working to restore normal capacity as quickly as possible. We will provide further updates as more information becomes available.

  2. monitoring Feb 26, 2026, 04:59 PM UTC

    The engineering team has successfully resolved the storage issue affecting the Dodgeball production PostgreSQL instance. Capacity has been restored and the system is now operating normally. At this time, we are not observing any elevated error rates for customers using Dodgeball. We will continue to monitor the system closely to ensure stability. Further updates will be provided if necessary.

  3. resolved Feb 26, 2026, 06:44 PM UTC

    The storage issue affecting the Dodgeball production instance has been fully resolved. Capacity has been restored and systems are operating normally. We are no longer observing elevated error rates for customers using Dodgeball. Thank you for your patience while we worked to resolve this issue.

Read the full incident report →

Major February 4, 2026

Multiple merchants using Payflow Pro with experiencing intermittent payment failures

Detected by Pingoru
Feb 04, 2026, 06:15 PM UTC
Resolved
Feb 04, 2026, 07:56 PM UTC
Duration
1h 41m
Affected: Core Transactional API
Timeline · 3 updates
  1. investigating Feb 04, 2026, 06:15 PM UTC

    Spreedly has detected an issue that is affecting multiple customers using Payflow Pro where some transactions fail with the error: “Invalid Request. Malicious string found in XML document”. While we are providing an early notification in an effort to alert you as quickly as possible, we are still investigating the actual scope and impact and will provide an update as soon as more details are available. Thank you for your patience.

  2. monitoring Feb 04, 2026, 07:52 PM UTC

    We are no longer seeing errors at this time, and the issue appears to have subsided. We are working with Payflow Pro to identify the root cause. Our team continues to monitor the situation closely to ensure stability. Please continue to follow our StatusPage for the latest updates.

  3. resolved Feb 04, 2026, 07:56 PM UTC

    This incident has been resolved.

Read the full incident report →

Major January 27, 2026

Dodgeball: Elevated levels of latency for Checkpoints

Detected by Pingoru
Jan 27, 2026, 07:59 PM UTC
Resolved
Jan 27, 2026, 08:12 PM UTC
Duration
13m
Affected: Dodgeball
Timeline · 2 updates
  1. investigating Jan 27, 2026, 07:59 PM UTC

    Spreedly has detected an issue related to a dodgeball component experiencing a partial outage. While we are providing an early notification in an effort to alert you as quickly as possible, we are still investigating the actual scope and impact and will provide an update as soon as more details are available. Thank you for your patience.

  2. resolved Jan 27, 2026, 08:12 PM UTC

    We’ve implemented a fix and stabilized the Dodgeball component that was experiencing a partial outage. After closely monitoring and confirming that all systems are stabilized and functioning as expected, this incident is considered resolved. No further customer impact is expected. We apologize for any inconvenience or disruption.

Read the full incident report →

Major January 9, 2026

Higher error rates on when using Dodgeball runtime

Detected by Pingoru
Jan 09, 2026, 06:46 PM UTC
Resolved
Jan 09, 2026, 07:10 PM UTC
Duration
24m
Affected: Dodgeball
Timeline · 4 updates
  1. investigating Jan 09, 2026, 06:46 PM UTC

    We are currently investigating this issue.

  2. investigating Jan 09, 2026, 06:52 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Jan 09, 2026, 07:07 PM UTC

    A fix has been deployed and we are seeing systems recover. We will continue to monitor to ensure stability and will provide further updates as needed.

  4. resolved Jan 09, 2026, 07:10 PM UTC

    After a period of monitoring, we have confirmed that the issue has been resolved and systems are operating normally. If you continue to experience any issues, please reach out to Support.

Read the full incident report →

Minor December 29, 2025

Increased Latency

Detected by Pingoru
Dec 29, 2025, 04:50 PM UTC
Resolved
Dec 28, 2025, 12:00 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Dec 29, 2025, 04:50 PM UTC

    Between 7:00 PM EST on Saturday, December 27th, and 1:00 AM EST on Sunday, December 28th, we identified a period of higher-than-normal latency caused by a pre-planned customer event that resulted in a significant traffic spike. Although we did not observe any service failures or timeouts, our systems experienced degraded service due to the increased latency. Systems recovered quickly once peak traffic subsided and are now operating normally. We expect performance to remain stable moving forward.

Read the full incident report →

Minor October 20, 2025

AWS Outage Impact

Detected by Pingoru
Oct 20, 2025, 03:41 PM UTC
Resolved
Oct 20, 2025, 08:22 PM UTC
Duration
4h 40m
Affected: Core Secondary API
Timeline · 3 updates
  1. identified Oct 20, 2025, 03:41 PM UTC

    The major AWS outage on October 20, 2025, has been largely resolved for most affected services, though some residual issues may persist. Spreedly’s core platform remains stable and fully available. However, due to downstream impact from the AWS outage, some of Spreedly’s indexing endpoints and callback processing are experiencing delays. This is related to dependencies on third-party systems that were affected by the outage and are still undergoing recovery. As a result, you may continue to see intermittent latency or delayed responses for API requests involving these systems. We are actively monitoring the situation as AWS and its downstream services continue recovery efforts. For ongoing updates, please refer to the AWS status page here

  2. resolved Oct 20, 2025, 08:22 PM UTC

    After closely monitoring and confirming that all systems are stabilized and functioning as expected, this incident is considered resolved. No further customer impact is expected.

  3. postmortem Oct 23, 2025, 06:27 PM UTC

    ### Postmortem: October 24, 2025 — _AWS outage_ Monday's AWS outage had downstream impact on some 3rd-party systems utilized by Spreedly's platform. Namely, our indexing endpoints and callbacks lagged behind due to the outage and recovery steps. ### What Happened Spreedly's 3DS global service and legacy smart routing product both faced a period of failures due to 3rd-party systems relying on AWS. ### Next Steps Spreedly will improve its response to our alerts platform, and are actively working on multi-region support slated for 2026, which should mitigate the impact of similar events going forward. -The Spreedly Team

Read the full incident report →

Critical September 30, 2025

Core 500s

Detected by Pingoru
Sep 30, 2025, 06:22 PM UTC
Resolved
Sep 30, 2025, 07:45 PM UTC
Duration
1h 22m
Affected: Core Transactional API
Timeline · 6 updates

Read the full incident report →

Major September 19, 2025

Elevated 3DS Failures

Detected by Pingoru
Sep 19, 2025, 03:53 PM UTC
Resolved
Sep 19, 2025, 05:46 PM UTC
Duration
1h 52m
Affected: 3DS Global
Timeline · 2 updates
  1. investigating Sep 19, 2025, 03:53 PM UTC

    We are currently investigating elevated 3DS failures with our Global 3DS provider, Seglan.

  2. resolved Sep 19, 2025, 05:46 PM UTC

    At 1:08 PM, 3DS provider, Seglan, deployed changes to address the issue. After a period of monitoring, we’ve observed normal performance and are declaring this incident resolved.

Read the full incident report →

Notice August 20, 2025

Elevated Rate of SCA Authentication Failures

Detected by Pingoru
Aug 20, 2025, 10:31 PM UTC
Resolved
Aug 19, 2025, 01:34 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Aug 20, 2025, 10:31 PM UTC

    On August 19th, 2025, from 9:34 a.m. to 12:55 p.m. EST, an unexpected interruption in 3DS execution occurred during a configuration change in one of our 3DS MPI providers' systems. Customers experienced an increased rate of SCA Authentication failures, resulting in the following error: "Gateway transaction not attempted due to failed SCA authentication." Our 3DS provider has since resolved the issue and is implementing stronger safeguards to prevent this from happening again. This issue is considered resolved, and no further customer impact is expected.

Read the full incident report →