Spreedly logo

All Systems Operational

About This Site

Welcome to Spreedly's StatusPage!

This has the latest data detailing the current operational health of Spreedly. To view the health of downstream 3rd party integrations, see our connection status page: https://status-connections.spreedly.com/

Uptime over the past 90 days. View historical uptime.
Core Transactional API Operational
90 days ago
99.98 % uptime
Today
Core Secondary API Operational
90 days ago
100.0 % uptime
Today
3DS Global Operational
90 days ago
100.0 % uptime
Today
Alternative Payment Methods (APMs) Operational
90 days ago
100.0 % uptime
Today
Composer Operational
90 days ago
100.0 % uptime
Today
Express Operational
90 days ago
100.0 % uptime
Today
iFrame Operational
90 days ago
100.0 % uptime
Today
Payment Method Distribution (PMD) Operational
90 days ago
100.0 % uptime
Today
Recover Operational
90 days ago
100.0 % uptime
Today
Spreedly Payment Fraud Prevention Operational
90 days ago
100.0 % uptime
Today
Dodgeball Operational
90 days ago
99.98 % uptime
Today
Advanced Vault Operational
BIN MetaData Operational
Fingerprinting Operational
Lifecycle Management (Account Updater) Operational
Lifecycle Management (Account Updater) Callbacks Operational
Network Tokenization Operational
Supporting Services Operational
app.spreedly.com Operational
Spreedly.com Operational
Docs.spreedly.com Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Feb 5, 2026
Credits Referencing Capture Transactions Failing
Resolved - After monitoring the system post-deploy, we’re no longer seeing errors related to credits referencing Capture transactions, and processing has returned to normal.

Thank you for your patience.
Feb 5, 12:01 EST
Monitoring - We’ve deployed a revert to address the issue where credit transactions referencing Capture transactions were failing.

We’re actively monitoring to ensure credit requests referencing Captures are processing as expected. At this time, we’re not seeing further errors related to this behavior.
Feb 5, 11:25 EST
Investigating - We are currently investigating an issue where credit transactions referencing Capture transactions are failing in production.

Some customers may see errors when attempting to issue credits against Capture transactions. Capture transactions themselves are processing successfully.

Our engineering team is actively investigating this behavior to determine the cause and confirm whether this is a regression or an unintended change. We will provide updates as soon as more information is available.
Feb 5, 10:56 EST
Feb 4, 2026
Multiple merchants using Payflow Pro with experiencing intermittent payment failures
Resolved - This incident has been resolved.
Feb 4, 14:56 EST
Monitoring - 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.
Feb 4, 14:52 EST
Investigating - 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.
Feb 4, 13:15 EST
Feb 3, 2026

No incidents reported.

Feb 2, 2026

No incidents reported.

Feb 1, 2026

No incidents reported.

Jan 31, 2026

No incidents reported.

Jan 30, 2026

No incidents reported.

Jan 29, 2026

No incidents reported.

Jan 28, 2026

No incidents reported.

Jan 27, 2026
Dodgeball: Elevated levels of latency for Checkpoints
Resolved - 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.
Jan 27, 15:12 EST
Investigating - 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.
Jan 27, 14:59 EST
3DS2 Global Transactions Pending
Postmortem - Read details
Feb 3, 10:41 EST
Resolved - 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.
Jan 27, 14:29 EST
Monitoring - We’ve implemented a fix and stabilized the 3DS2 Global transactions. Our team is monitoring the situation closely to ensure there are no additional impacts.

Please continue to follow our StatusPage for the latest update.
Jan 27, 14:25 EST
Investigating - Spreedly has detected an issue potentially resulting in a high number of pending 3DS2 Global transactions. 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.
Jan 27, 14:08 EST
Jan 26, 2026

No incidents reported.

Jan 25, 2026

No incidents reported.

Jan 24, 2026

No incidents reported.

Jan 23, 2026

No incidents reported.

Jan 22, 2026

No incidents reported.

← Incident History Powered by Atlassian Statuspage