Spreedly Outage History

33 incidents recorded over the last 365 days, 19 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Spreedly status100.00% uptime history

Every Recorded Spreedly Incident

Spreedly incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Sep 2, 2026Degraded performance on transactional APIs### _September 9, 2026_ — _Elevated Error Rates Affecting Transaction Processing_ ### ‌High Level Summary On September 2, 2026, between 14:35 and 15:19 UTC, Spreedly experienced a period of elevated error rates…6h 20mResolved
Aug 14, 2026Elevated 5xx Errors on Core API### Service Disruption on Transaction Endpoints ### ‌High Level Summary On August 14, 2026, Spreedly experienced a brief service disruption affecting some transaction-related API endpoints for approximately 20 minutes…20 minResolved
Jul 31, 2026Dodgeball Database MaintenanceThe scheduled maintenance has been completed.4h 0mScheduled
Jul 27, 2026Errors with While Tokenizing and Transacting### High Level Summary On July 27, 2026, Spreedly experienced intermittent errors on a subset of transaction requests, including purchases, authorizations, and webhooks. ### What Happened A database migration updated…7h 51mResolved
Jul 24, 2026Dodgeball Database MaintenanceThe scheduled maintenance has been completed.4h 0mScheduled
Jul 20, 2026Database MaintenanceThe scheduled maintenance has been completed.6h 0mScheduled
Jul 11, 2026Intermittent 500 Errors on List and Show EndpointsWe 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…1h 4mResolved
Jul 8, 2026Degraded performance on Cybersource Credit transactionsAfter 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…1h 32mResolved
Jun 17, 2026Asynchronous transactions with degraded performanceJune 24, 2026 — Asynchronous Transaction Processing Disruption **High Level Summary** On June 17, 2026 from approximately 10:02 AM to 10:41 AM UTC, Spreedly experienced a disruption affecting asynchronous gateway…6h 46mResolved
Jun 13, 2026Dodgeball Database MaintenanceThe scheduled maintenance has been completed.4h 0mScheduled
Jun 8, 2026Database MaintenanceThe scheduled maintenance has been completed.6h 0mScheduled
May 12, 2026Infrastructure Optimization - Dodgeball RDS Proxy RolloutThe scheduled maintenance has been completed.2h 0mScheduled
May 8, 2026Elevated Latency Dodgeball PlatformThis incident has been resolved.5 minResolved
Mar 19, 2026Dodgeball Checkpoint LatencyThis incident has been resolved.55 minResolved
Mar 16, 2026Increased errors with Core Transactional API### Mar 18th 2026 — _Decryption Errors on API endpoints_ ### Summary Between 5:40 PM and 5:43 PM UTC on March 16, 2026, we experienced a brief issue during a key rotation that caused a small subset of API requests to…21 minResolved
Mar 13, 2026Dodgeball maintenanceThe scheduled maintenance has been completed.1h 0mScheduled
Feb 27, 2026Dodgeball MaintenanceThe scheduled maintenance has been completed.2h 0mScheduled
Feb 26, 2026Dodgeball Production Instance Storage Critically LowThe 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…1h 58mResolved
Feb 25, 2026Dodgeball Checkpoint LatencyAfter 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…2h 34mResolved
Feb 24, 2026Dodgeball Database MaintenanceThe scheduled maintenance has been completed.4h 0mScheduled
Feb 18, 2026System MaintenanceThe scheduled maintenance has been completed.1h 0mScheduled
Feb 17, 2026Mastercard Network Tokenization Scheduled MaintenanceThe scheduled maintenance has been completed.1h 0mScheduled
Feb 5, 2026Credits Referencing Capture Transactions Failing### February 10, 2026 — Credits Referencing Capture Transactions Failing ### ‌High Level Summary Between approximately 1:56 PM UTC and 4:15 PM UTC on February 5, 2026, credit transactions where the reference…1h 5mResolved
Feb 4, 2026Multiple merchants using Payflow Pro with experiencing intermittent payment failuresThis incident has been resolved.1h 41mResolved
Jan 27, 2026Dodgeball: Elevated levels of latency for CheckpointsWe’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…13 minResolved
Jan 27, 20263DS2 Global Transactions Pending### February 3rd, 2026 — 3DS2 Global Transactions Pending ‌ Between 5:40 pm UTC and 7:24 PM UTC on January 27, 2026 the latest version of the Spreedly iFrame \(`iframe-v1`\) was configured to use version 1.180 which…21 minResolved
Jan 21, 2026Database MaintenanceThe scheduled maintenance has been completed.15h 0mScheduled
Jan 9, 2026Higher error rates on when using Dodgeball runtimeAfter 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.24 minResolved
Dec 29, 2025Increased LatencyBetween 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…-2450 minResolved
Dec 16, 2025Delayed Processing of Some 3DS Global Transactions# _December 18, 2025 — Delayed Processing of Some 3DS Global Transactions_ ‌ _A targeted update intended for Gateway-Specific 3DS processing impacted a subset of 3DS Global transactions. This caused a small number of…0 minResolved
Dec 9, 2025Transaction Reporting Degraded### _Postmortem: January 2, 2026_ — _Transaction Reporting Degraded_ ### ‌High Level Summary Select data related to transactions did not make it into our downstream systems, causing inaccurate reports in…28h 6mResolved
Dec 3, 2025Database MaintenanceThe scheduled maintenance has been completed.2h 0mScheduled
Nov 18, 2025Database MaintenanceThe scheduled maintenance has been completed.3h 0mScheduled

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Spreedly incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Spreedly Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Spreedly acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Spreedly outage in this window ran 1d 4h, against a mean recovery of 3h 39m. If you depend on Spreedly in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.