Spreedly Outage History
Spreedly is up right nowSpreedly had 34 outages in the last 2 years totaling 28h 7m of downtime — averaging 1.4 incidents per month.
There were 34 Spreedly outages since May 30, 2024 totaling 28h 7m of downtime. Each is summarised below — incident details, duration, and resolution information.
CVV Caching Error
Affected: iFrame
Timeline · 4 updates
System Instability - Endpoint Disruptions
Affected: Core Transactional API
Timeline · 2 updates
- monitoring Dec 03, 2024, 04:05 PM UTC
We experienced a brief period of system instability during which multiple endpoints were impacted. This issue resulted in intermittent errors and disruptions in service. Starting at 3:15 PM UTC our team promptly identified the root cause of the issue, and as of 3:20 PM UTC, the problem was resolved. Since then, we have not observed any recurrence of this issue. We are closely monitoring the system to ensure continued stability and are taking steps to prevent similar incidents in the future. If you have any questions or concerns, please reach out and our support team will be happy to assist.
- resolved Dec 03, 2024, 06:22 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 with regard to the causes of the incident and any residual impact. We apologize for any inconvenience or disruption.
3DS2 Global Transaction Processing Degraded
Affected: 3DS Global
Timeline · 2 updates
- investigating Oct 28, 2024, 11:44 AM UTC
We are investigating the potential degradation in 3DS2 processing, with specific focus on transactions not progressing beyond the pending state.
- resolved Oct 28, 2024, 01:16 PM UTC
After investigation, we have determined that there are no systemic issues with 3DS processing. Properly configured 3DS transactions are completing as expected. Thank you for your understanding.
Core Transactional API Experiencing 500 Errors.
Affected: Core Transactional API
Timeline · 2 updates
- identified Sep 26, 2024, 03:37 PM UTC
Since 2024-09-26 11:17 AM ET this morning, an issue has been detected causing 500 errors to our core transactional API. We have reverted to a stable release and are currently monitoring the system.
- resolved Sep 26, 2024, 03:56 PM UTC
Since 2024-09-26 11:17 AM ET this morning, we experienced an issue where a change to enhance how our Access Token validation is performed caused a disruption in services attempting to use the existing methods. At 11:29 AM ET, the change was fully reverted. All services may have been affected during this timeframe. After a period of monitoring, our systems are stable, and no further impact is expected on customers. We apologize for any inconvenience this incident has caused.
Data Syncing Issue
Affected: app.spreedly.com
Timeline · 2 updates
- investigating Sep 03, 2024, 02:30 PM UTC
We are currently investigating an issue affecting data synchronization with app.spreedly.com. Please note that this issue is not transaction-impacting, and all transactions are processing as expected. We will provide updates as we have more information.
- resolved Sep 03, 2024, 02:43 PM UTC
After completing our investigation, we can confirm that all systems are operational, and the reported issue is not affecting functionality. Everything is running as expected, and there is no disruption to service. Thank you for your understanding. Please feel free to reach out if you have any further concerns.
Payment Method Creation
Affected: Core Transactional API
Timeline · 3 updates
- monitoring Aug 30, 2024, 01:59 PM UTC
We are currently investigating an issue affecting payment method creation. Our team has identified the root cause of the issue affecting payment method creation and have implemented a fix. We are currently monitoring the situation to ensure that everything is functioning as expected. We'll provide more updates as soon as they're available
- monitoring Aug 30, 2024, 02:14 PM UTC
We are continuing to monitor for any further issues.
- resolved Aug 30, 2024, 02:41 PM UTC
After closely monitoring the situation and confirming that payment method creation is now stable and functioning as expected, we consider this incident resolved. No further customer impact is anticipated. We apologize for any inconvenience this may have caused and appreciate your patience as we worked to address the issue.
Core Transactional API Issues
Affected: Core Transactional API
Timeline · 3 updates
- investigating Aug 08, 2024, 05:45 PM UTC
We are aware that our Core Transactional API is experiencing some issues which may be impacting customers. We are actively investigating and will update with further details.
- monitoring Aug 08, 2024, 06:19 PM UTC
We experienced increased latency in our Core Transactional API from 17:32 UTC until 17:39 UTC. We immediately mobilized resources to address the issue. API performance has been stabilized. Our team is actively monitoring the situation closely to ensure there are no additional impacts. Please reach out to our Support team if you need any additional help.
- resolved Aug 08, 2024, 08:40 PM UTC
After closely monitoring our Core Transactional API 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 with regard to the causes of the incident and any residual impact. We apologize for any inconvenience or disruption.
Delays in listing transactions using the API listing endpoints.
Affected: Core Secondary API
Timeline · 3 updates
- identified Jul 18, 2024, 07:59 PM UTC
We have identified a gap in reporting for some customers listing recent transactions using the API listing endpoints, which may affect /v1/transactions/ and list Payment Methods /v1/payment_methods. We are aware of the issue and are working to implement a fix.
- monitoring Jul 19, 2024, 04:03 AM UTC
The Spreedly team has identified and implemented a fix to resolve the delay in our API listing endpoint and dashboard reporting. This delay did not affect the state or success of customer transactions, but reporting during this time frame may not be accurately reflected. This incident is being closely monitored, and we apologize for any inconvenience or disruption.
- resolved Jul 19, 2024, 12:45 PM UTC
After closely monitoring our reporting systems and confirming that all systems are stable and functioning as expected, this incident is considered resolved. We apologize for any inconvenience or disruption.