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.

Scheduled Maintenance

System Maintenance Feb 18, 2026 10:00-11:00 EST

On February 18th, 2026, from 10:00 AM to 11:00 AM EST, our systems will undergo scheduled maintenance. We will be performing dependency upgrades to improve overall security and performance. Our team will be closely monitoring the activity throughout the maintenance window

If you experience any unexpected impacts during this time, please reach out and our Support team will be happy to assist.
Posted on Feb 13, 2026 - 10:06 EST

Dodgeball Database Maintenance Feb 23, 2026 19:00-23:00 EST

On February 23rd, 2026, from 7:00 PM to 11:00 PM EST, our systems will undergo scheduled database maintenance. We will be performing a database version upgrade for DodgeballHQ. Our team will be closely monitoring the activity throughout the maintenance window
Posted on Feb 16, 2026 - 17:38 EST
Feb 17, 2026
Mastercard Network Tokenization Scheduled Maintenance
Completed - The scheduled maintenance has been completed.
Feb 17, 11:00 EST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 17, 10:00 EST
Scheduled - On February 17th 2026 from 10 am ET to 11am ET, our systems will undergo scheduled Annual Rotation of Mastercard Network Token keys. Note that while transactions attempted with a Mastercard network token during this rotation will not be rejected, attempts to provision a network token with a Mastercard card will not succeed during the key rotation portion of this activity. If you experience any unexpected impacts during this time, please reach out and our support team will be happy to assist.
Feb 10, 16:56 EST
Feb 16, 2026

No incidents reported.

Feb 15, 2026

No incidents reported.

Feb 14, 2026

No incidents reported.

Feb 13, 2026

No incidents reported.

Feb 12, 2026

No incidents reported.

Feb 11, 2026

No incidents reported.

Feb 10, 2026

No incidents reported.

Feb 9, 2026

No incidents reported.

Feb 8, 2026

No incidents reported.

Feb 7, 2026

No incidents reported.

Feb 6, 2026

No incidents reported.

Feb 5, 2026
Credits Referencing Capture Transactions Failing
Postmortem - Read details
Feb 10, 12:24 EST
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.

← Incident History Powered by Atlassian Statuspage