Last checked: 31 seconds ago
Get notified about any outages, downtime or incidents for Spreedly and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for Spreedly.
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 NowOutlogger tracks the status of these components for Xero:
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 |
Advanced Vault | Active |
Account Updater | Active |
Account Updater Callbacks | Active |
BIN MetaData | Active |
Fingerprinting | Active |
Network Tokenization | Active |
Alternative Payment Methods (APMs) | 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 |
Gateway Integrations | 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 |
Supporting Services | Active |
app.spreedly.com | Active |
Docs.spreedly.com | Active |
Spreedly.com | Active |
Spreedly Dashboard | Active |
View the latest incidents for Spreedly and check for official updates:
Description: From 2024-07-31 12:19:00 (time) EDT until 12:20:00 EDT this afternoon, or approximately one (1) minute, we detected an issue that resulted in minor intermittent 500 errors. Our team has implemented a solution to rectify the problem, and we are currently monitoring the system, but consider this incident resolved.
Status: Resolved
Impact: None | Started At: July 31, 2024, 5:16 p.m.
Description: 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.
Status: Resolved
Impact: Major | Started At: July 18, 2024, 7:59 p.m.
Description: 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.
Status: Resolved
Impact: Major | Started At: July 18, 2024, 7:59 p.m.
Description: # May 30, 2024 —Delays in listing transactions using the API listing endpoints # Executive Summary During a routine maintenance event, a piece of software responsible for reporting activity to systems used to generate customer reports and API listing endpoints silently failed to start. During the 40 minutes in which the software was non-functional, API calls for listing transactions and payment methods created in this timeframe would not have been reported. This reporting issue did not affect the outcome of customer transactions, only the ability for Spreedly systems to report that data to customers. After correcting the issue, Spreedly backfilled all available payment method and transaction data to reporting systems. # What Happened On 2024-05-30 at 15:15 UTC, production traffic was switched to a newly updated system responsible for generating customer activity data. This system silently failed to produce the necessary information, which resulted in a data gap. Upon automated alerting at 15:37, the team halted their maintenance work and reverted the system to a known good state by 15:50. After confirming that all systems were functioning normally and that no transactions were impacted, the team gathered all available data and replayed the data into the system so that reporting systems would accurately reflect that data. ## Next Steps Spreedly will continue to work to eliminate the possibility of silent failures of this functionality, testing to prevent non-functional reporting to receive production traffic, and introduce additional automated monitoring that will more quickly identify any loss of reporting volume. ## Conclusion Spreedly values the trust our customers place in us to handle one of the most critical aspects of their business, and welcome the opportunity to discuss any questions, concerns, or comments you have regarding this incident. Please reach out to our support staff or your account management team with your concerns.
Status: Postmortem
Impact: Minor | Started At: May 30, 2024, 4:10 p.m.
Description: # May 30, 2024 —Delays in listing transactions using the API listing endpoints # Executive Summary During a routine maintenance event, a piece of software responsible for reporting activity to systems used to generate customer reports and API listing endpoints silently failed to start. During the 40 minutes in which the software was non-functional, API calls for listing transactions and payment methods created in this timeframe would not have been reported. This reporting issue did not affect the outcome of customer transactions, only the ability for Spreedly systems to report that data to customers. After correcting the issue, Spreedly backfilled all available payment method and transaction data to reporting systems. # What Happened On 2024-05-30 at 15:15 UTC, production traffic was switched to a newly updated system responsible for generating customer activity data. This system silently failed to produce the necessary information, which resulted in a data gap. Upon automated alerting at 15:37, the team halted their maintenance work and reverted the system to a known good state by 15:50. After confirming that all systems were functioning normally and that no transactions were impacted, the team gathered all available data and replayed the data into the system so that reporting systems would accurately reflect that data. ## Next Steps Spreedly will continue to work to eliminate the possibility of silent failures of this functionality, testing to prevent non-functional reporting to receive production traffic, and introduce additional automated monitoring that will more quickly identify any loss of reporting volume. ## Conclusion Spreedly values the trust our customers place in us to handle one of the most critical aspects of their business, and welcome the opportunity to discuss any questions, concerns, or comments you have regarding this incident. Please reach out to our support staff or your account management team with your concerns.
Status: Postmortem
Impact: Minor | Started At: May 30, 2024, 4:10 p.m.
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.