Is Spreedly down?

Last checked just now
Current status
Spreedly is up

No incidents right now.

Official status page: http://status.spreedly.com · Polled every 5 minutes · 20 components tracked

Spreedly is operational right now. Last checked just now; the most recent incident resolved 5d ago.

Real-time Spreedly status, recent outages, and incident history — pulled directly from Spreedly's official status page at http://status.spreedly.com every 5 minutes. Pingoru tracks 20 Spreedly services and has captured 5 incidents in the last 90 days (99.86% uptime). Get email, Slack, Discord, or webhook alerts the moment Spreedly reports a new incident — free for 5 monitors, no credit card.

Users who monitor Spreedly also follow these Payments services: Square Authorize.Net Cash App FreedomPay Worldpay Clover Klarna JotForm Wise Breadcrumb View all 6,000+ providers
Spreedly uptime 99.86% uptime · past 90 days
Mon Wed Fri
MarAprMayJun
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 5m
    Started May 08, 2026, 06:00 PM UTC · Resolved May 08, 2026, 06:05 PM UTC
    Dodgeball
    Timeline · 2 updates
    • monitoring · May 08, 2026, 06:00 PM UTC

      A fix has been implemented and we are monitoring results.

    • resolved · May 08, 2026, 06:05 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  2. Resolved 55m
    Started Mar 19, 2026, 03:13 PM UTC · Resolved Mar 19, 2026, 04:09 PM UTC
    Dodgeball
    Timeline · 5 updates
    • identified · Mar 19, 2026, 03:13 PM UTC

      We are currently investigating performance of the Dodgeball service.

    • identified · Mar 19, 2026, 03:30 PM UTC

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

    • 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

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

    • resolved · Mar 19, 2026, 04:09 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  3. Resolved 21m
    Started Mar 16, 2026, 05:45 PM UTC · Resolved Mar 16, 2026, 06:07 PM UTC
    Core Transactional API
    Timeline · 4 updates
    • investigating · Mar 16, 2026, 05:45 PM UTC

      We are currently investigating elevated errors on API endpoints

    • monitoring · Mar 16, 2026, 05:51 PM UTC

      A fix has been implemented and we are monitoring to ensure services are operating correctly

    • resolved · Mar 16, 2026, 06: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 are completing our investigation concerning the causes of the incident and any residual impact. We apologize for any inconvenience or disruption.

    • postmortem · Mar 19, 2026, 07:07 PM UTC

      ### 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 fail due to decryption errors. These errors occurred within our system before any external processing took place. The issue was quickly identified, and traffic was immediately redirected to a stable environment, restoring normal service. ### What Happened At 5:36 PM UTC, we routed traffic to a newly deployed cluster of our encryption service running with the latest security keys. Shortly after, we observed decryption errors affecting a small subset of records, which resulted in some requests returning 500 error responses. We promptly redirected traffic back to the existing cluster, restoring normal operation. Further investigation determined that these records were still associated with a key in the process of rotation, and we updated them as a follow-up action to prevent the issue from recurring. ### Next Steps We have enhanced our process to ensure that a key’s usage is fully verified before it is removed from the encryption service. -The Spreedly Team

    Latest: ### 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 caus…

Outage history

Past 90 days · 3 incidents View full outage history →