[status] Resolved: After a period of monitoring, all systems are functioning normally. This incident is considered resolved.
We apologize for this disruption to service. https://t.co/6EpbY6aRZ3
[status] Monitoring: From 20:14 to 20:28 UTC the Core API experienced errors affecting customers. We have identified the cause of the errors and have implemented a fix.
We will continue to monitor to ensure the issue is resolved. https://t.co/cP4xhwzrWE
[status] Resolved: The issue of delayed data reporting in the Spreedly Dashboard has been resolved.
We have rerun processes that have restored data to the most up to date point in time.
We apologize for any inconveniences this dela… https://t.co/v2Qy8wJv2y
[status] Investigating: We are currently investigating a potential incident impacting Dashboard reporting. Reports on the Spreedly Dashboard may be delayed.
We will provide updates as they become available. https://t.co/cNC8RBU7e6
[status] Resolved: Most callbacks from our November 1st Account Updater run have been processed. No further updates will be provided via our Status Page, however we are communicating directly with higher volume customers still pendin… https://t.co/mgNh56xlJL
[status] Investigating: We are currently experiencing delays callbacks from our November 1st Account Updater run. Only customers who have subscribed to AU callbacks are being impacted. Our team is investigating and we will update soon… https://t.co/pYy3NurtpH
[status] Monitoring: Callbacks from the November 1st Account Updater run have been successfully processed for most impacted customers. We continue to monitor the remaining callbacks for some customers with higher volume and will prov… https://t.co/PvnNsFN3cR
[status] Resolved: After a period of monitoring, service to the Spreedly Dashboard has remained stable since 4:26pm EST Tuesday November 8th. The root cause has been identified and addressed.
We are considering the issue to be resol… https://t.co/Atuy1fsXp5
[status] Monitoring: During routine maintenance, an issue was identified which interrupted service to the Spreedly Dashboard from 3:41pm to 4:26pm EST. Customers may have had difficulty accessing Dashboard during this time.
A change… https://t.co/vWsyaZEpfi
[status] Resolved: We have identified a code change to our Core Transactional API that has affected Apple Pay transactions. The change resulted in Apple Pay Certificate Not Found errors that prevented Apple Pay transactions from going… https://t.co/MoTQG22XdC
[status] Resolved: We have identified a code change to a secondary service that has resulted in 406 errors for a small number of customers. This change was reverted and the issue is resolved. We have provisional evidence that impacted… https://t.co/yD4KpNQ3D1
[status] Resolved: After a period of monitoring, we have observed that the backlog in our secondary system is now at normal conditions as of 7:00 am EDT.
We apologize for any inconvenience this issue has caused. https://t.co/v3QaQIhOo3
[status] Monitoring: We are currently monitoring an issue where a backup in a secondary system is preventing data from being retrieved in a timely fashion. Customers are seeing impacts when trying to look up vaulted payments, newly cr… https://t.co/TuOFa2RvH4
[status] Monitoring: We have implemented additional measures to reduce the secondary system backlog. Based on the progress, we anticipate this will be cleared by tomorrow morning. Our team will continue monitoring and provide an upd… https://t.co/MBLPUGDDkx