tag:status.w2globaldata.com,2005:/historyW2 Status - Incident History2024-03-29T00:06:32+00:00W2tag:status.w2globaldata.com,2005:Incident/203596162024-03-25T23:30:00+00:002024-03-26T09:59:33+00:00Supplier Platform Outage<p><small>Mar <var data-var='date'>25</var>, <var data-var='time'>23:30</var> GMT</small><br><strong>Resolved</strong> - For a 13 minute window, beginning at 23:40 GMT our platform supplier appears to have lost all connections to a primary database. We have escalated this issue to our supplier as a matter of urgency.</p>tag:status.w2globaldata.com,2005:Incident/193139932024-01-17T11:38:45+00:002024-01-17T11:39:04+00:00Service notification – Partial data unavailable via Portal<p><small>Jan <var data-var='date'>17</var>, <var data-var='time'>11:38</var> GMT</small><br><strong>Resolved</strong> - We are now closing this incident but will continue to monitor the situation.</p><p><small>Dec <var data-var='date'> 4</var>, <var data-var='time'>14:21</var> GMT</small><br><strong>Identified</strong> - We are currently experiencing an issue with the Dashboard in the W2 Portal, where some traffic between 2nd December 2023 10:00 and 4th December 2023 09:00 has not logged correctly, and so is consequently not available to display in the portal.<br /><br />We are actively working on returning all of the data to the correct environment where it will then be available via the W2 portal.<br /><br />All other elements of the W2 Portal are working as expected, and all Monitoring records and alerts are unaffected by this incident.<br /><br />Please accept our apologies for any inconvenience caused by this issue - we will update this incident once the work has been completed.</p>tag:status.w2globaldata.com,2005:Incident/185574132023-09-21T22:00:17+01:002023-09-21T22:00:17+01:00Supplier Maintenance - UK eKYC 005<p><small>Sep <var data-var='date'>21</var>, <var data-var='time'>22:00</var> BST</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Sep <var data-var='date'>21</var>, <var data-var='time'>18:01</var> BST</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Sep <var data-var='date'>20</var>, <var data-var='time'>17:12</var> BST</small><br><strong>Scheduled</strong> - Our supplier will be performing maintenance on the service on Thursday 21st September between 18:00 and 22:00, which is an hour longer than the scheduled maintenance window.<br /> <br />During this period, the Deceased data block will not be available.<br /><br />Any searches completed during this outage will process as usual, but the Deceased data block will be unavailable. All other datablocks will continue to return the correct decision.</p>tag:status.w2globaldata.com,2005:Incident/184783892023-08-29T14:30:00+01:002023-09-12T10:58:15+01:00Important service notification – Incident Resolved<p><small>Aug <var data-var='date'>29</var>, <var data-var='time'>14:30</var> BST</small><br><strong>Resolved</strong> - An issue has been identified and resolved with W2-DATA-EKYB-UK-009. At 15:14 our third-party confirmed a fix was deployed to the affected services and since this time all services have been behaving as expected. Thank you for your patience during this time and we offer our apologies for any inconvenience caused.</p>tag:status.w2globaldata.com,2005:Incident/177814662023-07-16T00:00:01+01:002023-07-16T00:00:02+01:00Supplier Maintenance<p><small>Jul <var data-var='date'>16</var>, <var data-var='time'>00:00</var> BST</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Jul <var data-var='date'>15</var>, <var data-var='time'>12:01</var> BST</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'> 6</var>, <var data-var='time'>16:55</var> BST</small><br><strong>Scheduled</strong> - Dear Customer,<br /><br />We would like to take this opportunity to notify you of some maintenance by one of our service providers on the afternoon of Sunday the 15th of July between 12:00 and 23:59 BST.<br /><br />During the maintenance window the services may be unavailable, however every effort is being made for a smooth service switch that should only result in a few seconds of interruption.<br /> <br />Whilst the service is unavailable, any searches made will result in an error.<br /><br />Please accept our apologies for any inconvenience this may cause you.</p>tag:status.w2globaldata.com,2005:Incident/177079862023-06-27T17:30:00+01:002023-06-28T11:42:44+01:00Service interruption<p><small>Jun <var data-var='date'>27</var>, <var data-var='time'>17:30</var> BST</small><br><strong>Resolved</strong> - We have been alerted to an issue that occurred 27th June 2023 between 17:30 and 20:00, affecting our W2-DATA-EKYC-UK-015 service.<br /><br />Our third party confirmed they were experiencing a "performance degradation to all Credit Online services" which caused our service to return an error. If your bundle has a failover in place, your traffic would have automatically utilised the failover service, if you aren't currently using a failover service, please contact the W2 team to discuss adding this option to your bundles.<br /><br />The underlying issue was resolved by our third party and normal service has resumed since 20:00. We are monitoring the affected services closely.</p>tag:status.w2globaldata.com,2005:Incident/176525822023-06-22T12:40:38+01:002023-06-22T12:40:39+01:00Portal Maintenance<p><small>Jun <var data-var='date'>22</var>, <var data-var='time'>12:40</var> BST</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Jun <var data-var='date'>22</var>, <var data-var='time'>11:40</var> BST</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Jun <var data-var='date'>22</var>, <var data-var='time'>11:39</var> BST</small><br><strong>Scheduled</strong> - Dear Customer, we are carrying out some brief maintenance on our Portal that should only take a few minutes, however you may experience some disruption to the service during this time.<br /><br />Apologies for any inconvenience,<br /><br />W2 Team</p>tag:status.w2globaldata.com,2005:Incident/172534902023-06-01T21:00:10+01:002023-06-01T21:00:11+01:00Supplier Maintenance<p><small>Jun <var data-var='date'> 1</var>, <var data-var='time'>21:00</var> BST</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Jun <var data-var='date'> 1</var>, <var data-var='time'>18:00</var> BST</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>May <var data-var='date'>15</var>, <var data-var='time'>11:47</var> BST</small><br><strong>Scheduled</strong> - Dear Customer,<br /><br />We would like to take this opportunity to notify you of some maintenance by one of our service providers on the evening of Thursday the 1st of June between 18:00 and 21:00 BST.<br /><br />This maintenance may affect some of the searches carried out to our KYC workflows, however if you are using a workflow with failover configured, service during this period should be uninterrupted.<br /><br />During the maintenance window the services will be unavailable for up to three minutes between 18:00 and 18:30 whilst they apply the changes, and for a further 3 minutes between 19:30 and 20:00 whilst they complete post-change testing. <br /> <br />Whilst the service is unavailable, any searches made will result in an error.<br /><br />Please accept our apologies for any inconvenience this may cause you.</p>tag:status.w2globaldata.com,2005:Incident/173654842023-05-26T09:22:51+01:002023-05-26T09:22:51+01:00Important service notification<p><small>May <var data-var='date'>26</var>, <var data-var='time'>09:22</var> BST</small><br><strong>Resolved</strong> - We are happy to say we have been able to resolve the underlying issue with our supplier and all services are now working as expected. <br /><br />We will continue to monitor this closely to ensure it is operating as expected.<br /><br />Sincere apologies for any disruption this issue may have caused.</p><p><small>May <var data-var='date'>25</var>, <var data-var='time'>16:09</var> BST</small><br><strong>Monitoring</strong> - We are pleased to be able to confirm that at 15:56 a fix was deployed to the affected services and since this time all services have been behaving as expected. We will continue to monitor the situation until we are confident we can close the incident. Thank you for your patience during this time and once again offer our apologies for any inconvenience caused.</p><p><small>May <var data-var='date'>25</var>, <var data-var='time'>16:05</var> BST</small><br><strong>Identified</strong> - We are continuing to work with the supplier on the affected components. Apologies for the continued disruption, we will be providing additional updates within the next hour.</p><p><small>May <var data-var='date'>25</var>, <var data-var='time'>15:06</var> BST</small><br><strong>Investigating</strong> - We are currently experiencing a potential issue with one of our suppliers and we are investigating the cause and impact. We hope to provide a further update in the next 60 minutes. Please accept our apologies for any inconvenience this may be causing you.</p>tag:status.w2globaldata.com,2005:Incident/165943822023-03-23T11:08:10+00:002023-03-23T11:08:10+00:00Important service notification – KYB UK Incident<p><small>Mar <var data-var='date'>23</var>, <var data-var='time'>11:08</var> GMT</small><br><strong>Resolved</strong> - As of 10:30 today we are happy to say we have been able to resolve the underlying issue with our supplier and UK KYB is now working as expected. <br /><br />We will continue to monitor this service closely to ensure it is operating as expected.<br /><br />Sincere apologies for any disruption this issue may have caused.</p><p><small>Mar <var data-var='date'>22</var>, <var data-var='time'>17:17</var> GMT</small><br><strong>Update</strong> - Good afternoon, unfortunately, we are still working closely with our supplier to restore our UK KYB service. <br /><br />We do not have an ETA for resolution at this time, we shall endeavor to provide updates as soon as there is any change.<br /><br />Apologies for any inconvenience this issue is causing.</p><p><small>Mar <var data-var='date'>21</var>, <var data-var='time'>17:13</var> GMT</small><br><strong>Identified</strong> - Good afternoon, we have identified an issue with our supplier serving our UK KYB service. We are in contact with our supplier who are endeavoring to resolve the underlying issue, however, we are not able to provide a resolution estimate at present. <br /><br />Best efforts are being made to restore service but we are currently waiting for updates from our supplier. <br /><br />Apologies for the inconvenience this may cause.</p>tag:status.w2globaldata.com,2005:Incident/165773582023-03-20T15:47:15+00:002023-03-20T16:23:43+00:00Portal - Monitoring Dashboard Disruption<p><small>Mar <var data-var='date'>20</var>, <var data-var='time'>15:47</var> GMT</small><br><strong>Resolved</strong> - Unfortunately this afternoon we became aware of a service disruption to our Monitoring Results page. This was caused by a fault in a downstream dependency that was not caught by automated testing. We have identified the fault and are addressing the underlying cause that allowed the change through.</p>tag:status.w2globaldata.com,2005:Incident/163994982023-03-09T09:45:19+00:002023-03-09T09:50:57+00:00API Disruption<p><small>Mar <var data-var='date'> 9</var>, <var data-var='time'>09:45</var> GMT</small><br><strong>Resolved</strong> - This morning we became aware of an issue with our API causing transactions to return an error. This issue lasted between 09:37 and 09:44. We have identified the underlying cause and work is now being carried out to prevent this issue in the future. We are closely monitoring the service, but normal operation has been resumed.</p>tag:status.w2globaldata.com,2005:Incident/163230082023-03-02T06:00:00+00:002023-03-02T11:33:32+00:00Data source connection issue<p><small>Mar <var data-var='date'> 2</var>, <var data-var='time'>06:00</var> GMT</small><br><strong>Resolved</strong> - We have been alerted to an issue that occurred this morning between 06:00 and 06:23, affecting our services across our API and the Portal.<br /><br />At the moment it appears this has been caused by transient backend connection issues with our cloud provider.<br /><br />The underlying issue is now resolved and normal service has been resumed. We are monitoring the affected services closely.</p>tag:status.w2globaldata.com,2005:Incident/162208642023-02-22T09:17:24+00:002023-02-22T09:17:24+00:00Important service notification<p><small>Feb <var data-var='date'>22</var>, <var data-var='time'>09:17</var> GMT</small><br><strong>Resolved</strong> - Following the fix, we have been continuously monitoring the affected components and all behavior is as expected. We are now closing this incident but will continue to monitor the situation.</p><p><small>Feb <var data-var='date'>21</var>, <var data-var='time'>13:52</var> GMT</small><br><strong>Monitoring</strong> - We are pleased to be able to confirm that at 13:45 a fix was deployed to the Portal and since this time all services have been behaving as expected. We will continue to monitor the situation until we are confident we can close the incident. Thank you for your patience during this time and once again offer our apologies for any inconvenience caused.</p><p><small>Feb <var data-var='date'>21</var>, <var data-var='time'>13:21</var> GMT</small><br><strong>Investigating</strong> - We are currently experiencing a potential incident.
<br />We have become aware of a potential issue with our platform and we are currently investigating the cause and impact. We hope to provide a further update in the next 60 minutes. Please accept our apologies for any inconvenience this may be causing you.</p>tag:status.w2globaldata.com,2005:Incident/138623892022-11-29T09:32:50+00:002022-11-29T09:32:50+00:00Important service notification – Incident<p><small>Nov <var data-var='date'>29</var>, <var data-var='time'>09:32</var> GMT</small><br><strong>Resolved</strong> - Following the fix deployed at 13:58 we have been continuously monitoring the affected components and all behaviour is as expected. We are now closing this incident but will continue to monitor the situation for any changes</p><p><small>Nov <var data-var='date'>28</var>, <var data-var='time'>14:06</var> GMT</small><br><strong>Monitoring</strong> - We are pleased to be able to confirm that at 13:58 a fix was deployed by our third party to the affected service and since this time all services have been behaving as expected. We will continue to monitor the situation until we are confident we can close the incident. Thank you for your patience during this time and once again offer our apologies for any inconvenience caused.</p><p><small>Nov <var data-var='date'>28</var>, <var data-var='time'>13:03</var> GMT</small><br><strong>Identified</strong> - Upon investigation we can confirm that we are experiencing service issues and we have identified the problem is isolated to a third party supplier, unfortunately this is a service which we are unable to provide fail-over contingency for, therefore you may see some interrupted traffic during this incident period. Please rest assured we are working with the supplier as a matter of priority to implement a fix and return our service to normal working parameters. We hope to be able to provide an update as soon as possible.</p>tag:status.w2globaldata.com,2005:Incident/131303072022-11-16T11:17:45+00:002022-11-16T11:17:45+00:00Important service notification<p><small>Nov <var data-var='date'>16</var>, <var data-var='time'>11:17</var> GMT</small><br><strong>Resolved</strong> - Following the supplier fix deployed at 21:36 we have been continuously monitoring the affected components and all behaviour is as expected. We are now closing this incident but will continue to monitor the situation.</p><p><small>Nov <var data-var='date'>16</var>, <var data-var='time'>09:06</var> GMT</small><br><strong>Monitoring</strong> - We are pleased to be able to confirm that at 21:36 our third party deployed a fix to the affected services and since this time all services have been behaving as expected. We will continue to monitor the situation until we are confident we can close the incident. Thank you for your patience during this time and once again offer our apologies for any inconvenience caused.</p><p><small>Nov <var data-var='date'>15</var>, <var data-var='time'>14:41</var> GMT</small><br><strong>Identified</strong> - Upon investigation we can confirm that since 23:00 on the 14th November we have been experiencing intermittent service issues and we have identified the problem is isolated to a third party supplier, please note that if you have a fail-over configured in your workflow then you should not notice any service interruption, if you do not have a fail-over service configured then please contact your account manager to discuss this option. Please rest assured we are working with the supplier affected as a matter of priority to implement a fix and return our service to normal working parameters. We hope to be able to provide updates as soon as possible and will update by the end of the day at the latest.</p><p><small>Nov <var data-var='date'>15</var>, <var data-var='time'>13:20</var> GMT</small><br><strong>Investigating</strong> - We are currently experiencing a potential incident.
<br />We have become aware of a potential issue with our platform and we are currently investigating the cause and impact. We hope to provide a further update in the next 60 minutes. Please accept our apologies for any inconvenience this may be causing you.</p>tag:status.w2globaldata.com,2005:Incident/108285922022-08-15T12:07:43+01:002022-08-15T12:07:43+01:00Important service notification<p><small>Aug <var data-var='date'>15</var>, <var data-var='time'>12:07</var> BST</small><br><strong>Resolved</strong> - Following the fix deployed at 09:35 we have been continuously monitoring the affected components and all behaviour is as expected. We are now closing this incident but will continue to monitor the situation closely.</p><p><small>Aug <var data-var='date'>15</var>, <var data-var='time'>09:36</var> BST</small><br><strong>Monitoring</strong> - We are pleased to be able to confirm that at 09:35 a fix was deployed to the affected service and since this time all services have been behaving as expected. We will continue to monitor the situation until we are confident we can close the incident. Thank you for your patience during this time and once again offer our apologies for any inconvenience caused.</p><p><small>Aug <var data-var='date'>15</var>, <var data-var='time'>09:21</var> BST</small><br><strong>Investigating</strong> - We are currently experiencing a potential incident.
<br />We have become aware of a potential issue with our platform and we are currently investigating the cause and impact. We hope to provide a further update in the next 60 minutes. Please accept our apologies for any inconvenience this may be causing you.</p>tag:status.w2globaldata.com,2005:Incident/106683502022-07-22T13:26:47+01:002022-07-22T13:26:48+01:00Portal Service Interruption<p><small>Jul <var data-var='date'>22</var>, <var data-var='time'>13:26</var> BST</small><br><strong>Resolved</strong> - The Incident has been resolved, thank you for your patience.</p><p><small>Jul <var data-var='date'>22</var>, <var data-var='time'>12:04</var> BST</small><br><strong>Monitoring</strong> - An expired SSL certificate has been replaced for one of our backend services.<br /><br />Portal should now be fully functional again.<br /><br />We will continue to monitor the situation.</p><p><small>Jul <var data-var='date'>22</var>, <var data-var='time'>11:53</var> BST</small><br><strong>Identified</strong> - Apologies for the disruption to our online Portal.<br /><br />We have identified the cause of the logging-in issues you're experiencing.<br /><br />We are currently working hard to resolve the issue.<br /><br />Thank you for your patience.</p><p><small>Jul <var data-var='date'>22</var>, <var data-var='time'>11:46</var> BST</small><br><strong>Investigating</strong> - We are currently investigating the issue.</p>tag:status.w2globaldata.com,2005:Incident/103669022022-06-21T14:27:42+01:002022-06-21T14:27:42+01:00W2 Service Disruption<p><small>Jun <var data-var='date'>21</var>, <var data-var='time'>14:27</var> BST</small><br><strong>Resolved</strong> - We are now resolving this incident as we haven't observed any further issues since earlier this morning.</p><p><small>Jun <var data-var='date'>21</var>, <var data-var='time'>08:19</var> BST</small><br><strong>Monitoring</strong> - Dear customer,<br /><br />This morning it appears as though some of W2's services were affected by a widespread outage with our upstream DNS provider Cloudflare.<br /><br />Upon investigation, it now looks as though all services are operational, however, there may have been a few minutes this morning where our services were unreachable.<br /><br />Cloudflare still has an open and active P0 incident on their status page, so there may yet be further disruption but we are monitoring the situation closely.<br /><br />Apologies for any inconvenience this may have caused.</p>tag:status.w2globaldata.com,2005:Incident/102153862022-06-10T16:01:25+01:002022-06-10T16:01:25+01:00Important service notification<p><small>Jun <var data-var='date'>10</var>, <var data-var='time'>16:01</var> BST</small><br><strong>Resolved</strong> - Following the fix we have been continuously monitoring the affected components and all behavior is as expected. We are now closing this incident but will continue to monitor the situation.</p><p><small>Jun <var data-var='date'>10</var>, <var data-var='time'>11:17</var> BST</small><br><strong>Monitoring</strong> - We are pleased to be able to confirm that at 11:15 a fix was deployed to the affected services and since this time all services have been behaving as expected. We will continue to monitor the situation until we are confident we can close the incident. Thank you for your patience during this time and once again offer our apologies for any inconvenience caused.</p><p><small>Jun <var data-var='date'>10</var>, <var data-var='time'>10:41</var> BST</small><br><strong>Identified</strong> - Upon investigation, we can confirm that since 15:25 on the 9th of June we have been experiencing service issues and we have identified the problem is isolated to a third-party supplier, please note that if you have a fail-over configured in your workflow then you should not notice any service interruption, if you do not have a fail-over service configured then please contact your account manager to discuss this option. Please rest assured we are working with the supplier affected as a matter of priority to implement a fix and return our service to normal working parameters. We hope to be able to provide updates every 60 minutes.</p><p><small>Jun <var data-var='date'>10</var>, <var data-var='time'>09:54</var> BST</small><br><strong>Investigating</strong> - We are currently experiencing a potential incident.
<br />We have become aware of a potential issue with our platform and we are currently investigating the cause and impact. We hope to provide a further update in the next 60 minutes. Please accept our apologies for any inconvenience this may be causing you.</p>tag:status.w2globaldata.com,2005:Incident/98132412022-04-19T15:00:00+01:002022-04-19T17:05:05+01:00W2-DATA-PEP_AND_SANCTION-006 Service Error<p><small>Apr <var data-var='date'>19</var>, <var data-var='time'>15:00</var> BST</small><br><strong>Resolved</strong> - Our data import procedure introduced a config mismatch causing the W2-DATA-PEP_AND_SANCTION-006 service to go offline.<br /><br />Automated alerting caught the error and we were able to get the service back online quickly.<br /><br />The service was offline from 3:13 PM - 3:29 PM<br /><br />Apologies to all affected.</p>tag:status.w2globaldata.com,2005:Incident/96101812022-03-24T13:55:10+00:002022-03-24T13:55:10+00:00Important service notification – Manual Document Verification - Portal<p><small>Mar <var data-var='date'>24</var>, <var data-var='time'>13:55</var> GMT</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Mar <var data-var='date'>23</var>, <var data-var='time'>15:37</var> GMT</small><br><strong>Monitoring</strong> - We are pleased to be able to confirm that at 15:30 a fix was deployed to the Portal and since this time all services have been behaving as expected. We will continue to monitor the situation until we are confident we can close the incident. Thank you for your patience during this time and once again offer our apologies for any inconvenience caused.</p><p><small>Mar <var data-var='date'>23</var>, <var data-var='time'>14:57</var> GMT</small><br><strong>Update</strong> - We are currently testing our fix to this issue prior to it being rolled out.</p><p><small>Mar <var data-var='date'>23</var>, <var data-var='time'>13:43</var> GMT</small><br><strong>Update</strong> - We are continuing to work on a fix for this issue.</p><p><small>Mar <var data-var='date'>23</var>, <var data-var='time'>12:50</var> GMT</small><br><strong>Identified</strong> - Dear Customer,<br /><br />We have identified and are currently resolving an issue with the manual document verification service within the Portal. The API for this service is currently fully operational. <br /><br />Apologies for any inconvenience this may cause. We will be delivering another update on this issue within an hour.<br /><br /><br /><br />W2 Operations Team</p>tag:status.w2globaldata.com,2005:Incident/91767012022-02-21T04:00:29+00:002022-02-21T04:00:30+00:00Supplier Maintenance<p><small>Feb <var data-var='date'>21</var>, <var data-var='time'>04:00</var> GMT</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Feb <var data-var='date'>21</var>, <var data-var='time'>02:00</var> GMT</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'>27</var>, <var data-var='time'>14:23</var> GMT</small><br><strong>Scheduled</strong> - Dear Customer,<br /><br />We would like to take this opportunity to notify you of some maintenance by one of our service providers on the morning of Monday the 21st of February between 02:00 and 04:00 GMT.<br /><br />This maintenance may affect some of the searches carried out to our KYC workflows, however if you are using a workflow with failover configured, service during this period should be uninterrupted.<br /><br />We expect services to be fully operational again by 04:00 GMT on Monday, if there are any delays or issues relating to this maintenance window we will update our status page which can be accessed at https://status.w2globaldata.com<br /><br />Please accept our apologies for any inconvenience this may cause you.</p>tag:status.w2globaldata.com,2005:Incident/93441242022-02-17T21:33:27+00:002022-03-08T11:47:07+00:00Important service notification – Incident<p><small>Feb <var data-var='date'>17</var>, <var data-var='time'>21:33</var> GMT</small><br><strong>Resolved</strong> - Following the fix deployed at 17:55 we have been continuously monitoring the affected components and all behaviour is as expected. We are now closing this incident but will continue to monitor the situation.</p><p><small>Feb <var data-var='date'>17</var>, <var data-var='time'>17:56</var> GMT</small><br><strong>Monitoring</strong> - We are pleased to be able to confirm that at 17:55 a fix was deployed to the affected [services/components] and since this time all services have been behaving as expected. We will continue to monitor the situation until we are confident we can close the incident. Thank you for your patience during this time and once again offer our apologies for any inconvenience caused.</p><p><small>Feb <var data-var='date'>17</var>, <var data-var='time'>16:49</var> GMT</small><br><strong>Update</strong> - We are continuing to work on a fix for this issue.</p><p><small>Feb <var data-var='date'>17</var>, <var data-var='time'>16:47</var> GMT</small><br><strong>Identified</strong> - Upon investigation we can confirm that since 00:15 we have been experiencing service issues and we have identified the problem is isolated to a third party supplier, please note that if you have a fail-over configured in your workflow then you should not notice any service interruption, if you do not have a fail-over service configured then please contact your account manager to discuss this option. Please rest assured we are working with the supplier affected as a matter of priority to implement a fix and return our service to normal working parameters. We hope to provide as soon as possible.</p>tag:status.w2globaldata.com,2005:Incident/88562942021-12-15T21:00:30+00:002021-12-15T21:00:31+00:00Supplier Maintenance<p><small>Dec <var data-var='date'>15</var>, <var data-var='time'>21:00</var> GMT</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Dec <var data-var='date'>15</var>, <var data-var='time'>18:02</var> GMT</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Dec <var data-var='date'>15</var>, <var data-var='time'>16:16</var> GMT</small><br><strong>Scheduled</strong> - Dear Customer,<br /><br />Apologies for the short notice, but a supplier is carrying out essential maintenance this evening to mitigate the log4j RCE vulnerability and some of our services may be affected between 18:00 and 21:00 GMT.<br /><br />We will monitor the situation closely to ensure service has been restored after the window.<br /><br />W2 Operations</p>