tag:status.spreedly.com,2005:/historySpreedly Status - Incident History2024-03-28T20:06:01-04:00Spreedlytag:status.spreedly.com,2005:Incident/203803132024-03-27T14:07:38-04:002024-03-27T14:07:38-04:00Intermittent 500 Errors<p><small>Mar <var data-var='date'>27</var>, <var data-var='time'>14:07</var> EDT</small><br><strong>Resolved</strong> - After a period of monitoring, this incident is considered resolved. <br /><br />We appreciate your patience and apologize for any inconvenience. We will publish a post mortem related to this incident.</p><p><small>Mar <var data-var='date'>27</var>, <var data-var='time'>13:48</var> EDT</small><br><strong>Monitoring</strong> - We identified an issue that resulted in intermittent transaction failures. A fix has been implemented at 1:22 EST, we are monitoring the results.<br />We apologize for any disruption to service.</p><p><small>Mar <var data-var='date'>27</var>, <var data-var='time'>13:25</var> EDT</small><br><strong>Investigating</strong> - We are currently investigating an issue with access to the Dashboard application and related intermittent 500 errors.<br /><br />We apologize for any disruption to service.</p>tag:status.spreedly.com,2005:Incident/203052232024-03-21T17:00:56-04:002024-03-21T17:00:56-04:00Maintenance to 3DS Braintree Integration<p><small>Mar <var data-var='date'>21</var>, <var data-var='time'>17:00</var> EDT</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Mar <var data-var='date'>21</var>, <var data-var='time'>15:00</var> EDT</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Mar <var data-var='date'>19</var>, <var data-var='time'>18:45</var> EDT</small><br><strong>Scheduled</strong> - On Mar 21st 2024 at 3PM EST, our system will be undergoing maintenance on Spreedly's Braintree 3DS Challenge Flow. During this time, if customers experience an elevated number of transactions in a pending state for Braintree 3DS challenge flows, please <a href="https://support.spreedly.com/hc/en-us/requests/new">reach out</a> and our support team will be happy to assist.</p>tag:status.spreedly.com,2005:Incident/201343932024-03-01T11:58:05-05:002024-03-01T11:58:05-05:00Braintree 3DS Challenge Flow Issues<p><small>Mar <var data-var='date'> 1</var>, <var data-var='time'>11:58</var> EST</small><br><strong>Resolved</strong> - After careful monitoring, we consider this incident resolved.<br /><br />We apologize for any inconvenience or disruption.</p><p><small>Mar <var data-var='date'> 1</var>, <var data-var='time'>11:14</var> EST</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Mar <var data-var='date'> 1</var>, <var data-var='time'>11:11</var> EST</small><br><strong>Identified</strong> - 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. <br /><br />Our team is actively working towards a solution. We value your patience as we work to resolve this issue.</p>tag:status.spreedly.com,2005:Incident/201197542024-02-29T21:51:04-05:002024-02-29T21:51:04-05:00Apple Pay Vantiv Errors<p><small>Feb <var data-var='date'>29</var>, <var data-var='time'>21:51</var> EST</small><br><strong>Resolved</strong> - After closely monitoring our ApplePay integration through Vantiv and confirming that all systems are stabilized and functioning as expected, this incident is considered resolved. No further customer impact is expected.<br /><br />We are completing our investigation with regard to the causes of the incident and any residual impact. A post-mortem review will be published.<br /><br />We apologize for any inconvenience or disruption.</p><p><small>Feb <var data-var='date'>29</var>, <var data-var='time'>21:35</var> EST</small><br><strong>Monitoring</strong> - We experienced an issue causing some transactions that use ApplePay through the Vantiv integration to fail. Once identified, we immediately began working on a resolution. We’ve implemented a fix and stabilized the integration, and our team is monitoring the situation closely to ensure no additional impacts. <br /><br />Please reach out to our Support team if you need any additional help.</p><p><small>Feb <var data-var='date'>29</var>, <var data-var='time'>21:22</var> EST</small><br><strong>Identified</strong> - Since 2024-02-29 11:32 am ET this morning, an issue has been detected, causing some transactions that use ApplePay through the Vantiv integration to fail. Other service degradation may be related.<br /> <br />Our team is actively working towards a solution to rectify the problem, and we will keep you updated on any progress made in resolving the matter. We value your patience as we work to resolve this issue.</p>tag:status.spreedly.com,2005:Incident/200587752024-02-26T07:00:56-05:002024-02-26T07:00:56-05:00Scheduled Maintenance: Database Cluster Version Upgrade<p><small>Feb <var data-var='date'>26</var>, <var data-var='time'>07:00</var> EST</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Feb <var data-var='date'>26</var>, <var data-var='time'>06:00</var> EST</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Feb <var data-var='date'>23</var>, <var data-var='time'>11:32</var> EST</small><br><strong>Scheduled</strong> - On Feb 26th 2024 at 6AM EST, our system will be undergoing system maintenance to perform an upgrade to our Database cluster versioning, a process that may cause a small subset of transaction failures (Error 500s) in which the failed transactions will not be retried.<br /><br />If you experience any unexpected impacts during this time, please <a href="https://support.spreedly.com/hc/en-us/requests/new">reach out</a> and our support team will be happy to assist.</p>tag:status.spreedly.com,2005:Incident/199775062024-02-16T13:01:51-05:002024-02-16T13:01:51-05:00AU Callbacks<p><small>Feb <var data-var='date'>16</var>, <var data-var='time'>13:01</var> EST</small><br><strong>Resolved</strong> - After closely monitoring our fix on AU Callback Deliveries and confirming that all systems are stabilized and functioning as expected, this incident is considered resolved. No further customer impact is expected.<br /><br />We apologize for any inconvenience or disruption.</p><p><small>Feb <var data-var='date'>15</var>, <var data-var='time'>18:46</var> EST</small><br><strong>Monitoring</strong> - Since 2024-01-13, there has been an issue detected causing AU Callbacks to fail delivery. We’ve implemented a fix and stabilized AU Callback Deliveries and our team is monitoring the situation closely to ensure there are no additional impacts. <br /><br />Please reach out to our Support team if you need any additional help.</p><p><small>Feb <var data-var='date'>13</var>, <var data-var='time'>14:07</var> EST</small><br><strong>Identified</strong> - Since 2024-01-13, there has been an issue detected causing AU Callbacks to fail delivery. All impacted customers have been notified.<br /><br />Our team is actively working towards a solution to rectify the problem, and we will keep you updated on any progress made in resolving the matter. We value your patience as we work to resolve this issue.</p>tag:status.spreedly.com,2005:Incident/199839302024-02-16T09:19:20-05:002024-02-16T09:19:20-05:003DS Global Errors<p><small>Feb <var data-var='date'>16</var>, <var data-var='time'>09:19</var> EST</small><br><strong>Resolved</strong> - We have closely monitored the situation and received official confirmation that the issue has been resolved. As a result, we consider the incident resolved and do not anticipate any further impact on our customers.<br /><br />We apologize for any inconvenience or disruption.</p><p><small>Feb <var data-var='date'>15</var>, <var data-var='time'>14:02</var> EST</small><br><strong>Monitoring</strong> - Since 2024-02-14 09:14 ET, there has been an issue outside of our platform detected with our 3DS Global Provider.<br /><br />A fix has been implemented, and our team is monitoring the situation closely to ensure there are no additional impacts.<br /><br />Please reach out to our Support team if you need any additional help.</p><p><small>Feb <var data-var='date'>15</var>, <var data-var='time'>11:42</var> EST</small><br><strong>Update</strong> - Since 2024-02-14 09:14 ET, there has been an issue outside of our platform detected with our 3DS Global Provider.<br /><br />Our service provider is in the process of implementing a fix today to address the intermittent issues being noticed by some customers when conducting 3DS Global transactions with Visa. <br /><br />Once we've received confirmation from our service provider that the fix is in place, we will monitor the changes and communicate this status.</p><p><small>Feb <var data-var='date'>14</var>, <var data-var='time'>16:15</var> EST</small><br><strong>Identified</strong> - Since 2024-02-14 09:14 ET this morning, there has been an issue outside of our platform detected with our 3DS Global Provider.<br /><br />Our service provider has identified the source of the issue and is actively working to address. Spreedly continues to work with the provider on this issue and our team is monitoring the situation closely to ensure there are no additional impacts.<br /><br />The next update will be provided as soon as a material update is available.<br /><br />Please reach out to our Support team if you need any additional help.</p><p><small>Feb <var data-var='date'>14</var>, <var data-var='time'>09:14</var> EST</small><br><strong>Investigating</strong> - Spreedly identified an issue outside of our platform that could impact our services with 3DS. This may lead to degraded performance with 3DS Global.<br /><br />We are taking all necessary measures to investigate the matter with our service provider to determine the extent of the situation. We will provide an update as soon as more details are available.<br /><br />Thank you for your patience.</p>tag:status.spreedly.com,2005:Incident/198289102024-01-25T09:01:54-05:002024-01-25T09:01:54-05:00Mastercard Network Tokenization Scheduled Maintenance<p><small>Jan <var data-var='date'>25</var>, <var data-var='time'>09:01</var> EST</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Jan <var data-var='date'>25</var>, <var data-var='time'>08:00</var> EST</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Jan <var data-var='date'>25</var>, <var data-var='time'>07:12</var> EST</small><br><strong>Scheduled</strong> - Our system is currently undergoing maintenance activity. We are performing our annual production key rotation of our Mastercard Network Tokenization service, a process that may cause the service to be temporarily unavailable for about 15 minutes while we perform the key rotation. Note that while transactions attempted with a Mastercard network token during this rotation will not be rejected, attempts to provision a network token with a Mastercard card will not succeed during the key rotation portion of this activity. If you experience any unexpected impacts during this time, please <a href="https://support.spreedly.com/hc/en-us/requests/new">reach out</a> and our support team will be happy to assist.</p>tag:status.spreedly.com,2005:Incident/198072982024-01-24T12:11:08-05:002024-01-24T12:11:08-05:00BIN MetaData Requests<p><small>Jan <var data-var='date'>24</var>, <var data-var='time'>12:11</var> EST</small><br><strong>Resolved</strong> - We have mitigated the 1% errors seen with the BIN MetaData service after a period of monitoring and are taking further steps to make our system more resilient. We consider this incident resolved.<br /><br />We apologize for any inconvenience.</p><p><small>Jan <var data-var='date'>23</var>, <var data-var='time'>15:13</var> EST</small><br><strong>Update</strong> - We are continuing to investigate and are working towards mitigating this issue. <br /><br />We apologize for any inconvenience.</p><p><small>Jan <var data-var='date'>23</var>, <var data-var='time'>11:30</var> EST</small><br><strong>Update</strong> - We are investigating an issue related to the BIN metadata service. This is a service which provides data in the Spreedly response, but does not affect transaction success rates. We are seeing that in 1% of requests which access payment methods, the bin_metadata portion of the response ‘BIN metadata service unavailable.’ will be returned.</p><p><small>Jan <var data-var='date'>23</var>, <var data-var='time'>10:47</var> EST</small><br><strong>Investigating</strong> - We are currently investigating this issue.</p>tag:status.spreedly.com,2005:Incident/194757702023-12-18T22:43:44-05:002023-12-18T22:43:44-05:00Degraded performance with dLocal Gateway.<p><small>Dec <var data-var='date'>18</var>, <var data-var='time'>22:43</var> EST</small><br><strong>Resolved</strong> - This incident is considered resolved after closely monitoring our dLocal gateway connection and confirming that all systems are stabilized and functioning as expected. No further customer impact is expected.<br /><br />We apologize for any inconvenience or disruption.</p><p><small>Dec <var data-var='date'>18</var>, <var data-var='time'>22:26</var> EST</small><br><strong>Monitoring</strong> - We recently encountered a technical issue with Dlocal that resulted in errors for customers. Once identified, we immediately began working with the gateway on a resolution. We are pleased to report that we are now seeing successful transactions with Dlocal.<br /><br />Our team is monitoring the situation closely to ensure there are no additional impacts. <br /><br />Please reach out to our Support team if you need any additional help.</p><p><small>Dec <var data-var='date'>18</var>, <var data-var='time'>22:07</var> EST</small><br><strong>Identified</strong> - Spreedly has identified an issue outside of our platform that could impact our services with Dlocal.<br /><br />Our team is actively working towards a solution with the gateway to rectify the problem, and we will keep you updated on any progress made in resolving the matter. <br /><br />We value your patience as we work to resolve this issue.</p><p><small>Dec <var data-var='date'>18</var>, <var data-var='time'>21:06</var> EST</small><br><strong>Investigating</strong> - Spreedly has identified an issue outside of our platform that could impact our services with Dlocal. This may lead to degraded performance with all transactions with this gateway.<br /><br />We are taking all necessary measures to investigate the matter and determine the extent of the situation. We will provide an update as soon as more details are available.<br /><br />Thank you for your patience.</p>tag:status.spreedly.com,2005:Incident/194204682023-12-12T14:20:00-05:002023-12-12T14:20:00-05:00Gateway Specific 3DS Service Degradation via iFrame<p><small>Dec <var data-var='date'>12</var>, <var data-var='time'>14:20</var> EST</small><br><strong>Resolved</strong> - At 16:10 UTC a change was deployed to the Spreedly iFrame that introduced errors with Gateway Specific 3DS. A fix has been implemented at 18:52 UTC and the issue is now resolved.</p>tag:status.spreedly.com,2005:Incident/190622612023-11-08T17:30:15-05:002023-11-08T17:30:15-05:00Status Page Components Update<p><small>Nov <var data-var='date'> 8</var>, <var data-var='time'>17:30</var> EST</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Nov <var data-var='date'> 8</var>, <var data-var='time'>15:31</var> EST</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Nov <var data-var='date'> 8</var>, <var data-var='time'>15:28</var> EST</small><br><strong>Scheduled</strong> - This page is currently undergoing maintenance as we strive to make improvements.<br /><br />We are happy to bring to your attention our upcoming upgrades on Spreedly's Status page. We are following through on our commitment to ensuring that our systems component's status remains easy to understand should an incident arise. Through this maintenance, we can consistently deliver high-quality service and provide clear and precise information when a component is experiencing issues. <br /><br />Thank you for your continued support, and we look forward to serving you better.</p>tag:status.spreedly.com,2005:Incident/189721392023-10-30T17:07:27-04:002023-10-30T17:07:27-04:00Errors while trying to reach id.spreedly.com and dashboard.spreedly.com<p><small>Oct <var data-var='date'>30</var>, <var data-var='time'>17:07</var> EDT</small><br><strong>Resolved</strong> - After closely monitoring id.spreedly.com and dashboard.spreedly.com and confirming that all systems are stabilized and functioning as expected, this incident is considered resolved. No further customer impact is expected.<br /><br />We are completing our investigation with regard to the causes of the incident and any residual impact.<br /><br />We apologize for any inconvenience or disruption.</p><p><small>Oct <var data-var='date'>30</var>, <var data-var='time'>16:42</var> EDT</small><br><strong>Monitoring</strong> - Spreedly had detected an issue that prevented access to id.spreedly.com and dashboard.spreedly.com.<br /><br />Since that time the issue has been resolved, and we apologize for any inconvenience it may have caused.<br />We will be working with one of our partners to determine the cause of the issue.<br /><br />Thank you for your patience and understanding.</p>tag:status.spreedly.com,2005:Incident/185779722023-09-22T16:43:22-04:002023-09-22T16:43:22-04:00Spreedly Dashboard<p><small>Sep <var data-var='date'>22</var>, <var data-var='time'>16:43</var> EDT</small><br><strong>Resolved</strong> - Spreedly has monitored the results of the deployed fix and have now deemed this incident to be resolved.</p><p><small>Sep <var data-var='date'>22</var>, <var data-var='time'>14:08</var> EDT</small><br><strong>Identified</strong> - The issue has been identified and a fix is being implemented.</p><p><small>Sep <var data-var='date'>22</var>, <var data-var='time'>11:53</var> EDT</small><br><strong>Investigating</strong> - We are investigating an issue with the Spreedly Dashboard.</p>tag:status.spreedly.com,2005:Incident/185595342023-09-20T21:10:37-04:002023-09-29T16:01:30-04:00Increased timeouts for a small number of transactions<p><small>Sep <var data-var='date'>20</var>, <var data-var='time'>21:10</var> EDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Sep <var data-var='date'>20</var>, <var data-var='time'>20:47</var> EDT</small><br><strong>Update</strong> - We have closely monitored the situation and received official confirmation from our third-party provider that the issue has been resolved. As a result, we consider the incident resolved and do not anticipate any further impact on our customers.<br /><br />We apologize for any inconvenience or disruption.</p><p><small>Sep <var data-var='date'>20</var>, <var data-var='time'>18:15</var> EDT</small><br><strong>Monitoring</strong> - Since 2023-09-20 2:41 PM ET this afternoon, there has been an issue outside of our platform detected with regional network service.<br /><br />Traffic has been rerouted in this region, and we continue to monitor traffic. Please reach out to our Support team if you need any additional help.</p><p><small>Sep <var data-var='date'>20</var>, <var data-var='time'>16:37</var> EDT</small><br><strong>Investigating</strong> - Spreedly has discovered an issue that could potentially impact our services, leading to Increased timeouts for a small number of transactions.<br /><br />We are taking all necessary measures to investigate the matter and determine the extent of the situation. We provide an update as soon as more details are available.<br /><br />Thank you for your patience.</p>tag:status.spreedly.com,2005:Incident/185024042023-09-14T12:44:03-04:002023-09-14T12:44:03-04:00Errors with Payment Method Distribution Service<p><small>Sep <var data-var='date'>14</var>, <var data-var='time'>12:44</var> EDT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Sep <var data-var='date'>14</var>, <var data-var='time'>12:33</var> EDT</small><br><strong>Monitoring</strong> - A fix has been implemented and are confident the issue is resolved. We are continuing to monitor our systems closely.</p><p><small>Sep <var data-var='date'>14</var>, <var data-var='time'>12:15</var> EDT</small><br><strong>Identified</strong> - Spreedly is aware that some customers received 500 errors for PMD transactions. We have identified the fix and it has been implemented.</p>tag:status.spreedly.com,2005:Incident/183368132023-08-31T11:00:00-04:002023-08-31T11:50:39-04:00503 Errors<p><small>Aug <var data-var='date'>31</var>, <var data-var='time'>11:00</var> EDT</small><br><strong>Resolved</strong> - At 2023-08-31 11:18:00 AM ET this morning, a change was made causing 503 Errors.<br /><br />After rolling back our changes and close monitoring, we have confirmed that all systems are stabilized and functioning as expected, this incident is considered resolved. No further customer impact is expected.<br /><br />We are completing our investigation with regard to the causes of the incident and any residual impact. **A post-incident review will be published.**<br /><br />We apologize for any inconvenience or disruption.</p>tag:status.spreedly.com,2005:Incident/182981612023-08-28T17:41:44-04:002023-08-28T17:41:44-04:00Monitoring potential issue with third-party service provider<p><small>Aug <var data-var='date'>28</var>, <var data-var='time'>17:41</var> EDT</small><br><strong>Resolved</strong> - We have closely monitored the situation and received official confirmation from Fastly that the issue has been resolved. As a result, we consider the incident resolved and do not anticipate any further impact on our customers.<br /><br />We apologize for any inconvenience or disruption.</p><p><small>Aug <var data-var='date'>28</var>, <var data-var='time'>17:22</var> EDT</small><br><strong>Monitoring</strong> - A Fix has been implemented by Fastly and they are monitoring results<br /><br />Please reach out to our Support team if you need any additional help.<br /><br />For additional information: https://www.fastlystatus.com/</p><p><small>Aug <var data-var='date'>28</var>, <var data-var='time'>17:09</var> EDT</small><br><strong>Investigating</strong> - We continue to see no worsening symptoms of an impact from the outage. We'll continue to monitor Fastly Status for resolution and intend on updating Spreedly status to resolved when Fastly has reported as resolved or if this moves into more formal incident territory. We are reporting our systems as operational alongside the status page post. Support is keeping watch on the inbound queue.<br /><br />We will provide an update as soon as more details are available. <br /> <br />Thank you for your patience.</p><p><small>Aug <var data-var='date'>28</var>, <var data-var='time'>16:37</var> EDT</small><br><strong>Identified</strong> - Spreedly is monitoring an issue we’ve identified with our third-party CDN, Fastly, who is reporting an issue that we believe is resulting in a very small number of intermittent 503 error responses. <br /><br />We're in communication with Fastly and are closely monitoring the situation. Fastly has communicated the issue has been identified and a fix is being implemented. We'll continue to provide updates as soon as more details are available.</p>tag:status.spreedly.com,2005:Incident/181663322023-08-16T21:14:08-04:002023-08-16T21:14:08-04:00Transaction Errors with Payeezy<p><small>Aug <var data-var='date'>16</var>, <var data-var='time'>21:14</var> EDT</small><br><strong>Resolved</strong> - After a period of monitoring, we have not seen any recurrence of this issue.<br /><br />We consider this incident resolved and do not anticipate any further impact on our customers.<br /><br />We apologize for the impact this caused to affected customers.</p><p><small>Aug <var data-var='date'>16</var>, <var data-var='time'>18:56</var> EDT</small><br><strong>Monitoring</strong> - We have been in contact with Payeezy and they confirmed there was an outage on their side. It appears this has been corrected as we are seeing successful transactions with this payments gateway now. <br /><br />We will monitor for some time to make sure all has returned to normal.</p><p><small>Aug <var data-var='date'>16</var>, <var data-var='time'>17:49</var> EDT</small><br><strong>Investigating</strong> - Our team is actively investigating an issue that led to Payeezy payments gateway outage. <br /><br /><br />We are taking all necessary measures to investigate the matter and determine the extent of the situation. We will provide an update as soon as more details are available. <br /><br /><br />Thank you for your patience.</p><p><small>Aug <var data-var='date'>16</var>, <var data-var='time'>16:39</var> EDT</small><br><strong>Identified</strong> - We have identified an issue with the Payeezy payments gateway which is impacting customers transacting through this integration. <br /><br />We are currently investigating and will provide an update within the next hour.</p>tag:status.spreedly.com,2005:Incident/181261742023-08-14T15:09:56-04:002023-08-14T15:09:56-04:00Degraded Performance With Elavon Gateway<p><small>Aug <var data-var='date'>14</var>, <var data-var='time'>15:09</var> EDT</small><br><strong>Resolved</strong> - We have closely monitored the situation and received official confirmation from Elavon, as well from our customers, that the issue has been resolved. As a result, we consider the incident resolved and do not anticipate any further impact on our customers or their capability to transact using this gateway.<br /><br />We apologize for any inconvenience or disruption.</p><p><small>Aug <var data-var='date'>14</var>, <var data-var='time'>10:45</var> EDT</small><br><strong>Monitoring</strong> - We have been notified by Elavon that a fix has been implemented. We also see evidence of an increased success rate in our internal systems and will continue monitoring.<br /><br />Please reach out to our Support team if you need any additional help.</p><p><small>Aug <var data-var='date'>14</var>, <var data-var='time'>10:28</var> EDT</small><br><strong>Update</strong> - We are continuing to work on a fix for this issue.</p><p><small>Aug <var data-var='date'>14</var>, <var data-var='time'>09:19</var> EDT</small><br><strong>Update</strong> - We are continuing to reach out to Elavon in an effort to have this issue resolved as soon as possible. We will provide another update an hour from now.<br /> <br />Thank you for your patience.</p><p><small>Aug <var data-var='date'>13</var>, <var data-var='time'>15:50</var> EDT</small><br><strong>Update</strong> - We continue to actively reach out to Elavon in an effort to achieve a resolution on this issue, however the current expectations are that we will see further traction tomorrow, Monday. We will provide another update by 9 AM ET, unless we have any information from Elavon sooner.</p><p><small>Aug <var data-var='date'>13</var>, <var data-var='time'>13:07</var> EDT</small><br><strong>Update</strong> - We continue to actively reach out to Elavon in an effort to achieve resolution as soon as possible. We will provide another update by 4 pm ET, unless we have any information sooner.</p><p><small>Aug <var data-var='date'>13</var>, <var data-var='time'>09:57</var> EDT</small><br><strong>Update</strong> - We will continue to reach out to Elavon to pursue a fix for this issue.</p><p><small>Aug <var data-var='date'>13</var>, <var data-var='time'>09:56</var> EDT</small><br><strong>Update</strong> - We will continue to reach out to Elavon to pursue a fix for this issue.</p><p><small>Aug <var data-var='date'>12</var>, <var data-var='time'>20:12</var> EDT</small><br><strong>Update</strong> - We have been in touch with Elavon throughout the day. The issue is known and we have requested Elavon dispatch additional resources to resolve their network issue. We will provide another update no later than 10 EDT tomorrow, or sooner if the issue is able to be resolved before then.</p><p><small>Aug <var data-var='date'>12</var>, <var data-var='time'>16:57</var> EDT</small><br><strong>Update</strong> - We continue to actively follow up on status of this issue with Elavon and while they are still investigating, we do not have an estimated resolution time yet. We will provide another update as soon as we receive additional information from their organization.</p><p><small>Aug <var data-var='date'>12</var>, <var data-var='time'>14:42</var> EDT</small><br><strong>Update</strong> - Our team has been assured that Elavon continues to actively investigate this issue. We will follow up with them and provide another update within the next couple of hours.</p><p><small>Aug <var data-var='date'>12</var>, <var data-var='time'>13:16</var> EDT</small><br><strong>Update</strong> - We have actively engaged with Elavon and are currently jointly investigating this issue. <br />We will provide another update once we have more information.</p><p><small>Aug <var data-var='date'>12</var>, <var data-var='time'>12:00</var> EDT</small><br><strong>Update</strong> - We are continuing to work on a fix for this issue.</p><p><small>Aug <var data-var='date'>12</var>, <var data-var='time'>11:53</var> EDT</small><br><strong>Identified</strong> - Since 2023-08-11 at 20:06 ET we started to detect intermittent errors when communicating with the Elavon gateway.<br /><br />This issue appears to be similar to a previous one we experienced on August 1st. Approximately a third of the transactions traffic is being blocked by the payments gateway. <br /><br />We have reached out to Elavon for immediate assistance in resolving this issue and will provide an update as soon as we have additional information</p>tag:status.spreedly.com,2005:Incident/180114872023-08-01T19:09:22-04:002023-08-01T19:09:22-04:00Degraded Performance with Elavon Gateway<p><small>Aug <var data-var='date'> 1</var>, <var data-var='time'>19:09</var> EDT</small><br><strong>Resolved</strong> - We have closely monitored the situation since Elavon notified us earlier that the issue was resolved, and we have confirmed that the errors that were previously experienced are no longer being experienced. We consider this incident resolved and do not anticipate any further impact on our customers.<br /><br />We apologize for any inconvenience or disruption. We will continue working with Elavon on root cause analysis and in jointly ensuring that we prevent a similar issue in the future.</p><p><small>Aug <var data-var='date'> 1</var>, <var data-var='time'>17:28</var> EDT</small><br><strong>Update</strong> - We are continuing to monitor for any further issues.</p><p><small>Aug <var data-var='date'> 1</var>, <var data-var='time'>15:01</var> EDT</small><br><strong>Monitoring</strong> - We have been notified by Elavon that a fix has been implemented. We also see evidence of an increased success rate in our internal systems and will continue monitoring.</p><p><small>Aug <var data-var='date'> 1</var>, <var data-var='time'>10:52</var> EDT</small><br><strong>Update</strong> - We are continuing to investigate this issue. We are in contact with Elavon and are confident that our investigation is progressing towards a resolution. <br /><br />Thank you for your patience and we sincerely apologize for any inconvenience.</p><p><small>Jul <var data-var='date'>31</var>, <var data-var='time'>18:23</var> EDT</small><br><strong>Update</strong> - We are continuing to investigate this issue. We are currently working with Elavon to work toward a resolution.<br /><br />Thank you for your patience.</p><p><small>Jul <var data-var='date'>31</var>, <var data-var='time'>11:06</var> EDT</small><br><strong>Investigating</strong> - Spreedly identified an issue outside of our platform that could impact our services with Elavon Gateway. This may affect customers transacting against this gateway. <br /><br />We are taking all necessary measures to investigate the matter and determine the extent of the situation. We will provide an update as soon as more details are available.<br /><br />Thank you for your patience.</p>tag:status.spreedly.com,2005:Incident/178926042023-07-19T10:08:34-04:002023-07-21T15:44:03-04:00Spreedly API Errors<p><small>Jul <var data-var='date'>19</var>, <var data-var='time'>10:08</var> EDT</small><br><strong>Resolved</strong> - After closely monitoring our Core Transactional API and confirming that all systems are stabilized and functioning as expected, this incident is considered resolved. <br /><br />We are completing our investigation with regard to the causes of the incident and any residual impact. A post-incident review will be published.<br /><br />We apologize for any inconvenience or disruption.</p><p><small>Jul <var data-var='date'>18</var>, <var data-var='time'>20:56</var> EDT</small><br><strong>Monitoring</strong> - Our Engineering team has identified and implemented some changes to address the issue. As we actively monitor the fix, we are seeing a reduction in error rates indicating the fix is stabilizing the errors and addressing the issue.<br /><br />We’ll continue to monitor the fix closely and provide updates.</p><p><small>Jul <var data-var='date'>18</var>, <var data-var='time'>18:20</var> EDT</small><br><strong>Update</strong> - Our team is actively investigating an issue with one of the libraries that feeds our Core component resulting in some transactions receiving errors. Some customers may have experienced 500 errors. We are still investigating a potential solution.<br /><br />Thank you for your patience.</p><p><small>Jul <var data-var='date'>18</var>, <var data-var='time'>15:38</var> EDT</small><br><strong>Identified</strong> - Since 2023-07-18 3:01 ET, there has been an issue detected causing intermittent errors on the Spreedly API. <br /><br />Our team is actively working towards a solution to rectify the problem, and we will keep you updated on any progress made in resolving the matter. We value your patience as we work to resolve this issue.</p>tag:status.spreedly.com,2005:Incident/178471242023-07-13T16:12:40-04:002023-07-13T16:12:40-04:00Status Page Components Update<p><small>Jul <var data-var='date'>13</var>, <var data-var='time'>16:12</var> EDT</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Jul <var data-var='date'>13</var>, <var data-var='time'>15:11</var> EDT</small><br><strong>Update</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Jul <var data-var='date'>13</var>, <var data-var='time'>15:10</var> EDT</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Jul <var data-var='date'>13</var>, <var data-var='time'>15:09</var> EDT</small><br><strong>Scheduled</strong> - We are very happy to bring to your attention our upcoming upgrades on Spreedly's Status page. We are committed to ensuring that our systems component's status remains easy and clear to understand should an incident arise. Through this maintenance, we can consistently deliver high-quality service and provide clear and precise information when a component is experiencing issues.<br /><br />Thank you for your continued support, and we look forward to serving you better.</p>tag:status.spreedly.com,2005:Incident/177219262023-06-29T17:15:56-04:002023-06-29T17:15:56-04:00Intermittent iFrame Errors<p><small>Jun <var data-var='date'>29</var>, <var data-var='time'>17:15</var> EDT</small><br><strong>Resolved</strong> - After a period of monitoring, we have confirmed that the issue has been resolved.</p><p><small>Jun <var data-var='date'>29</var>, <var data-var='time'>16:08</var> EDT</small><br><strong>Monitoring</strong> - The intermittent errors with the Spreedly iFrame have subsided.<br /><br />We are continuing to monitor to ensure that the issue is fully resolved</p><p><small>Jun <var data-var='date'>29</var>, <var data-var='time'>15:37</var> EDT</small><br><strong>Identified</strong> - We have identified an issue with an upstream service provider causing intermittent errors on the Spreedly iFrame.<br /><br />We are communicating with our service provider as they work to resolve the issue.</p><p><small>Jun <var data-var='date'>29</var>, <var data-var='time'>13:22</var> EDT</small><br><strong>Investigating</strong> - We are currently investigating an issue with the Spreedly iFrame. Users may experience that iFrame will intermittently not load when requested.</p>tag:status.spreedly.com,2005:Incident/175485232023-06-12T18:14:59-04:002023-06-12T18:14:59-04:003DS2 Errors with some Mastercard transactions<p><small>Jun <var data-var='date'>12</var>, <var data-var='time'>18:14</var> EDT</small><br><strong>Resolved</strong> - We have received confirmation from Mastercard that a service disruption, which was identified for their Smart Interface and caused customers to experience intermittent transaction failures during the impact period, has now been restored.<br /><br />We appreciate your patience while we tracked this issue with our partners.</p><p><small>Jun <var data-var='date'>12</var>, <var data-var='time'>15:24</var> EDT</small><br><strong>Update</strong> - Our team is still tracking an issue that started June 12th, 2023, at 07:03 am EST (12:03 UTC).<br /><br />Customers may continue to experience transaction failures within our 3DS2 Global Solution. Our Global 3DS2 provider and Mastercard have both confirmed this is an ongoing issue impacting Mastercard's card types. We understand that the Mastercard team is working to mitigate the issue and restore service to all customers as soon as possible.<br /><br />We will provide an update as soon as more details are available.<br /><br />Thank you for your patience at this time.</p><p><small>Jun <var data-var='date'>12</var>, <var data-var='time'>11:04</var> EDT</small><br><strong>Identified</strong> - We have identified an issue which is impacting some Mastercard 3DS2 transactions for a subset of our customers using our 3DS2 Global solution. These transactions are failing with the following error "Remote Error: Intermediate layer error - error in intermediate layer (message received invalid. could not read the message. authentication response)". We have logged a ticket with our third party 3DS2 provider and they are actively investigating. We will provide updates as these become available to us.</p>