Company Logo

Is there an Spreedly outage?

Spreedly status: Minor Outage

Last checked: 5 minutes ago

Get notified about any outages, downtime or incidents for Spreedly and 1800+ other cloud vendors. Monitor 10 companies, for free.

Subscribe for updates

Spreedly outages and incidents

Outage and incident data over the last 30 days for Spreedly.

There have been 1 outages or incidents for Spreedly in the last 30 days.

Severity Breakdown:

Tired of searching for status updates?

Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!

Sign Up Now

Components and Services Monitored for Spreedly

Outlogger tracks the status of these components for Xero:

3DS Gateway Specific Active
3DS Global Active
Core Secondary API Active
Core Transactional API Active
Express Active
iFrame Active
Payment Method Distribution (PMD) Active
Account Updater Active
Account Updater Callbacks Active
BIN MetaData Active
Fingerprinting Active
Network Tokenization Active
ACH Active
Apple Pay Active
Click to Pay (C2P) Active
Ebanx Local Payment Methods Active
Google Pay Active
Paypal & Offsite Payments Active
PPRO Local Payment Methods Active
Stripe Alternative Payment Methods Active
Adyen Active
Authorize.net Active
Braintree Active
Cybersource Performance Issues
Elavon Active
Gateways Active
Mercado Pago Active
NMI Active
Orbital Active
Payflow Pro Active
PayPal Active
Stripe API Active
Worldpay Active
app.spreedly.com Active
Docs.spreedly.com Active
Spreedly.com Active
Spreedly Dashboard Active
Component Status
3DS Gateway Specific Active
3DS Global Active
Core Secondary API Active
Core Transactional API Active
Express Active
iFrame Active
Payment Method Distribution (PMD) Active
Active
Account Updater Active
Account Updater Callbacks Active
BIN MetaData Active
Fingerprinting Active
Network Tokenization Active
Active
ACH Active
Apple Pay Active
Click to Pay (C2P) Active
Ebanx Local Payment Methods Active
Google Pay Active
Paypal & Offsite Payments Active
PPRO Local Payment Methods Active
Stripe Alternative Payment Methods Active
Performance Issues
Adyen Active
Authorize.net Active
Braintree Active
Cybersource Performance Issues
Elavon Active
Gateways Active
Mercado Pago Active
NMI Active
Orbital Active
Payflow Pro Active
PayPal Active
Stripe API Active
Worldpay Active
Active
app.spreedly.com Active
Docs.spreedly.com Active
Spreedly.com Active
Spreedly Dashboard Active

Latest Spreedly outages and incidents.

View the latest incidents for Spreedly and check for official updates:

Updates:

  • Time: May 7, 2024, 10:48 a.m.
    Status: Resolved
    Update: We are marking this item as resolved. After further review of data, SCA authentications are processing successfully.
  • Time: May 7, 2024, 10:18 a.m.
    Status: Investigating
    Update: We are currently investigating an issue related to Strong Customer Authentication (SCA) authentication rejections. Requests for SCA authentication are being rejected with the error message "Service: Invalid Json response"

Updates:

  • Time: May 7, 2024, 10:48 a.m.
    Status: Resolved
    Update: We are marking this item as resolved. After further review of data, SCA authentications are processing successfully.
  • Time: May 7, 2024, 10:18 a.m.
    Status: Investigating
    Update: We are currently investigating an issue related to Strong Customer Authentication (SCA) authentication rejections. Requests for SCA authentication are being rejected with the error message "Service: Invalid Json response"

Updates:

  • Time: April 19, 2024, 7:51 p.m.
    Status: Resolved
    Update: After a period of monitoring, this incident is considered resolved. We appreciate your patience and apologize for any inconvenience. We will publish a post mortem related to this incident.
  • Time: April 19, 2024, 7:51 p.m.
    Status: Resolved
    Update: After a period of monitoring, this incident is considered resolved. We appreciate your patience and apologize for any inconvenience. We will publish a post mortem related to this incident.
  • Time: April 17, 2024, 6:02 p.m.
    Status: Monitoring
    Update: We are monitoring the degraded performance for some users accessing Spreedly ID via Single Sign-On (SSO) connections using using OpenID Connect (OIDC). We have implemented a workaround for users experiencing this issue. If you are still impacted, please <a href="https://support.spreedly.com/hc/en-us/requests/new">reach out</a> and our support team will gladly assist you with gaining access. We apologize for any inconvenience this issue has caused and are working on a longer term solution
  • Time: April 17, 2024, 6:02 p.m.
    Status: Monitoring
    Update: We are monitoring the degraded performance for some users accessing Spreedly ID via Single Sign-On (SSO) connections using using OpenID Connect (OIDC). We have implemented a workaround for users experiencing this issue. If you are still impacted, please <a href="https://support.spreedly.com/hc/en-us/requests/new">reach out</a> and our support team will gladly assist you with gaining access. We apologize for any inconvenience this issue has caused and are working on a longer term solution
  • Time: April 16, 2024, 3:17 p.m.
    Status: Investigating
    Update: We are currently investigating reports of degraded performance for Single Sign-On (SSO) users accessing Spreedly ID. Users may experience delays or timeout issues when logging in or accessing the Spreedly dashboard or certain features. Our engineering team is actively investigating the root cause of the issue. please <a href="https://support.spreedly.com/hc/en-us/requests/new">reach out</a> to our support team if you are experiencing any log in issues.
  • Time: April 16, 2024, 3:17 p.m.
    Status: Investigating
    Update: We are currently investigating reports of degraded performance for Single Sign-On (SSO) users accessing Spreedly ID. Users may experience delays or timeout issues when logging in or accessing the Spreedly dashboard or certain features. Our engineering team is actively investigating the root cause of the issue. please <a href="https://support.spreedly.com/hc/en-us/requests/new">reach out</a> to our support team if you are experiencing any log in issues.
  • Time: April 11, 2024, 7:50 p.m.
    Status: Monitoring
    Update: We observed degraded performance for some users accessing Spreedly ID via Single Sign-On (SSO). Our team has investigated and we have implemented a workaround for users experiencing this issue. If you are still impacted, please reach out, and our support team will gladly assist you with gaining access. We apologize for any inconvenience this issue has caused.
  • Time: April 11, 2024, 7:50 p.m.
    Status: Monitoring
    Update: We observed degraded performance for some users accessing Spreedly ID via Single Sign-On (SSO). Our team has investigated and we have implemented a workaround for users experiencing this issue. If you are still impacted, please reach out, and our support team will gladly assist you with gaining access. We apologize for any inconvenience this issue has caused.
  • Time: April 11, 2024, 3:27 p.m.
    Status: Investigating
    Update: We are currently investigating reports of degraded performance for Single Sign-On (SSO) users accessing Spreedly ID. Users may experience delays or timeout issues when logging in or accessing the Spreedly dashboard or certain features. Our engineering team is actively investigating the root cause of the issue. We will provide updates as soon as more information becomes available.
  • Time: April 11, 2024, 3:27 p.m.
    Status: Investigating
    Update: We are currently investigating reports of degraded performance for Single Sign-On (SSO) users accessing Spreedly ID. Users may experience delays or timeout issues when logging in or accessing the Spreedly dashboard or certain features. Our engineering team is actively investigating the root cause of the issue. We will provide updates as soon as more information becomes available.

Updates:

  • Time: April 5, 2024, 5:17 p.m.
    Status: Postmortem
    Update: ### **March 27th, 204 — ID Server Misconfiguration** A server configuration issue resulted in the ID service being unable to handle all incoming requests, which led to intermittent availability of Spreedly services, some transaction impacts, and 500 type errors being served to customers. ### **What Happened** On 3/27, at 2:30 PM UTC, Spreedly engineers began scheduled maintenance of the Spreedly ID service which handles authentication and authorization for other Spreedly services. A redeploy of the ID service, following the maintenance, revealed a latent server misconfiguration which led to application issues on specific servers in the ID cluster. At 5:41 PM UTC, the Spreedly Core service began intermittently responding with errors, as the ID service was no longer able to handle all incoming authorization requests. At 5:47 PM UTC, Spreedly engineers observed the increase in 500s from ID and began investigating. The misconfiguration was discovered and corrected at 6:22 PM UTC at which point the ID service began to recover. Errors from Spreedly Core services ceased entirely at 6:26 PM UTC. ### **Next Steps** Spreedly engineers have corrected the configurations that contributed to the application issues and are working to determine additional improvements that would prevent reoccurrence. Spreedly engineers are taking steps to lower the alerting thresholds for the ID service to provide earlier notification of similar issues. ### **Conclusion** We apologize for the disruption of the service, our goal is to maintain a reliable service for our customers so avoiding these kind of events is one of our top priorities. We’ll drive our efforts to keep improving our services.
  • Time: April 5, 2024, 5:17 p.m.
    Status: Postmortem
    Update: ### **March 27th, 204 — ID Server Misconfiguration** A server configuration issue resulted in the ID service being unable to handle all incoming requests, which led to intermittent availability of Spreedly services, some transaction impacts, and 500 type errors being served to customers. ### **What Happened** On 3/27, at 2:30 PM UTC, Spreedly engineers began scheduled maintenance of the Spreedly ID service which handles authentication and authorization for other Spreedly services. A redeploy of the ID service, following the maintenance, revealed a latent server misconfiguration which led to application issues on specific servers in the ID cluster. At 5:41 PM UTC, the Spreedly Core service began intermittently responding with errors, as the ID service was no longer able to handle all incoming authorization requests. At 5:47 PM UTC, Spreedly engineers observed the increase in 500s from ID and began investigating. The misconfiguration was discovered and corrected at 6:22 PM UTC at which point the ID service began to recover. Errors from Spreedly Core services ceased entirely at 6:26 PM UTC. ### **Next Steps** Spreedly engineers have corrected the configurations that contributed to the application issues and are working to determine additional improvements that would prevent reoccurrence. Spreedly engineers are taking steps to lower the alerting thresholds for the ID service to provide earlier notification of similar issues. ### **Conclusion** We apologize for the disruption of the service, our goal is to maintain a reliable service for our customers so avoiding these kind of events is one of our top priorities. We’ll drive our efforts to keep improving our services.
  • Time: March 27, 2024, 6:07 p.m.
    Status: Resolved
    Update: After a period of monitoring, this incident is considered resolved. We appreciate your patience and apologize for any inconvenience. We will publish a post mortem related to this incident.
  • Time: March 27, 2024, 6:07 p.m.
    Status: Resolved
    Update: After a period of monitoring, this incident is considered resolved. We appreciate your patience and apologize for any inconvenience. We will publish a post mortem related to this incident.
  • Time: March 27, 2024, 5:48 p.m.
    Status: Monitoring
    Update: We identified an issue that resulted in intermittent transaction failures. A fix has been implemented at 1:22 EST, we are monitoring the results. We apologize for any disruption to service.
  • Time: March 27, 2024, 5:48 p.m.
    Status: Monitoring
    Update: We identified an issue that resulted in intermittent transaction failures. A fix has been implemented at 1:22 EST, we are monitoring the results. We apologize for any disruption to service.
  • Time: March 27, 2024, 5:25 p.m.
    Status: Investigating
    Update: We are currently investigating an issue with access to the Dashboard application and related intermittent 500 errors. We apologize for any disruption to service.
  • Time: March 27, 2024, 5:25 p.m.
    Status: Investigating
    Update: We are currently investigating an issue with access to the Dashboard application and related intermittent 500 errors. We apologize for any disruption to service.

Updates:

  • Time: March 1, 2024, 4:58 p.m.
    Status: Resolved
    Update: After careful monitoring, we consider this incident resolved. We apologize for any inconvenience or disruption.
  • Time: March 1, 2024, 4:14 p.m.
    Status: Monitoring
    Update: A fix has been implemented and we are monitoring the results.
  • Time: March 1, 2024, 4:11 p.m.
    Status: Identified
    Update: Since 2024-02-29 11:02 am EST, we have identified an issue causing some Braintree 3DS transactions in the challenge flow to remain in a pending state. Our team is actively working towards a solution. We value your patience as we work to resolve this issue.

Check the status of similar companies and alternatives to Spreedly

NetSuite
NetSuite

Systems Active

ZoomInfo
ZoomInfo

Systems Active

SPS Commerce
SPS Commerce

Systems Active

Miro
Miro

Systems Active

Field Nation
Field Nation

Systems Active

Outreach
Outreach

Systems Active

Own Company

Systems Active

Mindbody
Mindbody

Systems Active

TaskRabbit
TaskRabbit

Systems Active

Nextiva
Nextiva

Systems Active

6Sense

Systems Active

BigCommerce
BigCommerce

Systems Active

Frequently Asked Questions - Spreedly

Is there a Spreedly outage?
The current status of Spreedly is: Minor Outage
Where can I find the official status page of Spreedly?
The official status page for Spreedly is here
How can I get notified if Spreedly is down or experiencing an outage?
To get notified of any status changes to Spreedly, simply sign up to OutLogger's free monitoring service. OutLogger checks the official status of Spreedly every few minutes and will notify you of any changes. You can veiw the status of all your cloud vendors in one dashboard. Sign up here
What does Spreedly do?
Spreedly connects businesses to payment services in 100+ countries through a single API connection, as a leading Payments Orchestration Platform.

Start monitoring now!

Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.

Get Started for Free