tag:silverfinnv.statuspage.io,2005:/historySilverfin Status - Incident History2024-03-29T06:22:39+01:00Silverfintag:silverfinnv.statuspage.io,2005:Incident/200772852024-03-25T23:30:06+01:002024-03-25T23:30:06+01:00Scheduled Maintenance Notice: Downtime on March 25 (22:00 CET)<p><small>Mar <var data-var='date'>25</var>, <var data-var='time'>23:30</var> CET</small><br><strong>Completed</strong> - Scheduled Maintenance successfully completed. All operations around the platform, including syncs, will resume immediately.<br /><br />We appreciate your patience and understanding. As always, if you have any questions or issues, do not hesitate to contact us at support@silverfin.com.</p><p><small>Mar <var data-var='date'>25</var>, <var data-var='time'>22:00</var> CET</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'>26</var>, <var data-var='time'>11:02</var> CET</small><br><strong>Scheduled</strong> - To ensure the highest level of performance and reliability of our services, we are planning a routine update to our database systems. This maintenance is a part of our commitment to continue providing you with the best possible experience.<br /><br />Maintenance Window:<br />* Date: 2024-03-25<br />* Time: 22:00 CET<br />* Expected Downtime: up to 2 hours<br /><br />During this maintenance window, the Silverfin platform will be inaccessible. All operations around the platform, including syncs, will resume immediately after the maintenance window.<br /><br />We understand the importance of minimizing downtime and its impact on your activities. Our team will work diligently to complete the maintenance as quickly and efficiently as possible.<br /><br />We appreciate your patience and understanding. As always, if you have any questions or issues, do not hesitate to contact us at support@silverfin.com.</p>tag:silverfinnv.statuspage.io,2005:Incident/198649452024-01-30T11:15:43+01:002024-01-30T11:15:43+01:00Synchronisation with ExactOnline not working<p><small>Jan <var data-var='date'>30</var>, <var data-var='time'>11:15</var> CET</small><br><strong>Resolved</strong> - As the incident has no impact any more in Silverfin, this incident is now resolved at Silverfin. Based on the Status page of Exact, we see that Exact is monitoring this further on their side (Timestamp: 30/01/24 at 11:15). We of course keep monitoring everything at Silverfin.</p><p><small>Jan <var data-var='date'>30</var>, <var data-var='time'>10:22</var> CET</small><br><strong>Monitoring</strong> - ExactOnline services are fully operational again. We and ExactOnline are continuing to monitor the situation.</p><p><small>Jan <var data-var='date'>30</var>, <var data-var='time'>09:54</var> CET</small><br><strong>Identified</strong> - At the moment, we see that the Exact Online synchronisations are not working. This is caused by a partial outage at ExactOnline. Please check https://status.exact.com for the latest updates. We are also actively monitoring the situation as well.</p>tag:silverfinnv.statuspage.io,2005:Incident/198572992024-01-29T14:45:58+01:002024-01-29T14:45:58+01:00Slower Response Times in Silverfin<p><small>Jan <var data-var='date'>29</var>, <var data-var='time'>14:45</var> CET</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jan <var data-var='date'>29</var>, <var data-var='time'>14:43</var> CET</small><br><strong>Monitoring</strong> - The issue has been resolved. You should no longer experience any slower response times.</p><p><small>Jan <var data-var='date'>29</var>, <var data-var='time'>14:33</var> CET</small><br><strong>Identified</strong> - We're currently experiencing slower response time and delayed synchronisations across Silverfin. We have identified the issue and we are working on a fix. Our apologies for the inconvenience.</p>tag:silverfinnv.statuspage.io,2005:Incident/196654772024-01-10T11:52:53+01:002024-01-10T11:52:53+01:00Slower response times due to high load<p><small>Jan <var data-var='date'>10</var>, <var data-var='time'>11:52</var> CET</small><br><strong>Resolved</strong> - This incident has been resolved</p><p><small>Jan <var data-var='date'>10</var>, <var data-var='time'>10:45</var> CET</small><br><strong>Monitoring</strong> - The issue has been resolved. You should no longer experience any slower response times. Currently, we're continuing to monitor the situation closely.</p><p><small>Jan <var data-var='date'>10</var>, <var data-var='time'>10:32</var> CET</small><br><strong>Identified</strong> - We have identified the issue and are working on resolving the issue at the moment.</p><p><small>Jan <var data-var='date'>10</var>, <var data-var='time'>10:07</var> CET</small><br><strong>Update</strong> - We are continuing to investigate this issue.</p><p><small>Jan <var data-var='date'>10</var>, <var data-var='time'>10:05</var> CET</small><br><strong>Investigating</strong> - We're currently experiencing slower response time across Silverfin. We're aware of this and are investigating it</p>tag:silverfinnv.statuspage.io,2005:Incident/193996502023-12-11T11:47:32+01:002023-12-11T11:47:32+01:00Slower Response Times in Silverfin<p><small>Dec <var data-var='date'>11</var>, <var data-var='time'>11:47</var> CET</small><br><strong>Resolved</strong> - This incident is resolved.</p><p><small>Dec <var data-var='date'>11</var>, <var data-var='time'>11:22</var> CET</small><br><strong>Monitoring</strong> - The cause has been identified and addressed. Silverfin is functioning normally again. We are monitoring further.</p><p><small>Dec <var data-var='date'>11</var>, <var data-var='time'>11:11</var> CET</small><br><strong>Investigating</strong> - We're currently experiencing slower response time across Silverfin. We're aware of this and are investigating it.</p>tag:silverfinnv.statuspage.io,2005:Incident/191861652023-11-22T11:57:43+01:002023-11-22T11:57:43+01:00Yuki new or changed bookings are not coming through<p><small>Nov <var data-var='date'>22</var>, <var data-var='time'>11:57</var> CET</small><br><strong>Resolved</strong> - We see that new and change bookings now coming through as expected. This incident is resolved<br /><br />---<br /><br />We zien dat nieuwe en gewijzigde boekingen nu terug goed doorkomen, zoals verwacht. Dit incident is opgelost.</p><p><small>Nov <var data-var='date'>22</var>, <var data-var='time'>10:17</var> CET</small><br><strong>Monitoring</strong> - A new fix has been implemented for Yuki. Please resync your file to sync your latest updates. If you still encounter any synchronisation issues after your new sync run, please contact our Support team for assistance.<br /><br />---<br /><br />Een nieuwe fix is geïmplementeerd voor Yuki. Gelieve je dossier opnieuw te synchroniseren, zodat jouw laatste wijzigingen worden gesynchroniseerd. Als je na jouw synchronisatie nog steeds hinder ondervindt, gelieve ons dit te laten weten via ons Support team.</p><p><small>Nov <var data-var='date'>21</var>, <var data-var='time'>15:06</var> CET</small><br><strong>Identified</strong> - We discovered a side effect in the recent fix that resulted in synchronization delays. To tackle this issue, we've temporarily rolled back the fix, identified the root cause, and are actively working on a permanent solution. We appreciate your patience and understanding, and we apologize for any inconvenience caused.<br /><br />---<br /><br />We hebben een neveneffect ontdekt in de recente fix die resulteerde in synchronisatie vertragingen. Om deze hinder te verhelpen, hebben we de fix tijdelijk teruggedraaid, de hoofdoorzaak geïdentificeerd en werken we actief aan een permanente oplossing. We stellen uw geduld en begrip op prijs en bieden onze excuses aan voor het ongemak.</p><p><small>Nov <var data-var='date'>21</var>, <var data-var='time'>12:44</var> CET</small><br><strong>Monitoring</strong> - We've implemented a fix. We're closely monitoring the fix to ensure its effectiveness.<br />Please resync your file to ensure you have the latest updates. If you still encounter any synchronization issues after your new sync run, please contact our Support team for assistance.<br /><br />---<br /><br />We hebben een oplossing geïmplementeerd. We volgen momenteel de oplossing verder op. Gelieve eerst je dossier opnieuw te synchroniseren, zodat zeker de laatste wijzigingen zijn gesynchroniseerd. Als je na jouw synchronisatie nog steeds hinder ondervindt, gelieve ons dit via ons Support team te laten weten.</p><p><small>Nov <var data-var='date'>21</var>, <var data-var='time'>10:55</var> CET</small><br><strong>Identified</strong> - We're currently experiencing technical difficulties with Yuki, which may affect your ability to synchronize new or updated bookings. We are actively working on a permanent solution to resolve this issue. If you require immediate assistance, please contact our support team. For non-urgent matters, we kindly request you to wait patiently as we address this issue. We will continue to provide updates on the status page.<br /><br />---<br /><br />Op dit moment ondervind je mogelijk hinder bij het synchroniseren van nieuwe of gewijzigde boekingen in Yuki. We werken actief aan een permanente oplossing. Wanneer je het dossier onmiddellijk nodig hebt, vragen we je om contact met ons op te nemen, we helpen je graag verder. Voor niet-dringende dossiers vragen we je even te wachten, tot de permanente oplossing gepubliceerd is. We houden jullie via deze status pagina verder op de hoogte.</p>tag:silverfinnv.statuspage.io,2005:Incident/191872132023-11-21T17:15:33+01:002023-11-21T17:15:33+01:00You can experience delayed synchronisations<p><small>Nov <var data-var='date'>21</var>, <var data-var='time'>17:15</var> CET</small><br><strong>Resolved</strong> - The issue was identified and related to the recent Yuki fix, which has been temporarily reverted. Synchronizations are now functioning as intended. This incident is resolved now.</p><p><small>Nov <var data-var='date'>21</var>, <var data-var='time'>14:14</var> CET</small><br><strong>Identified</strong> - We have noticed that you can experience delayed synchronisations. We have identified the cause, and are working on fixing this as soon as possible. Thank you for your patience. Our apologies for the inconvenience.</p>tag:silverfinnv.statuspage.io,2005:Incident/189092882023-10-24T11:21:43+02:002023-10-24T11:21:43+02:00Degraded performance<p><small>Oct <var data-var='date'>24</var>, <var data-var='time'>11:21</var> CEST</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Oct <var data-var='date'>24</var>, <var data-var='time'>10:07</var> CEST</small><br><strong>Identified</strong> - We have identified the issue and are looking into resolving the issue at the moment.</p><p><small>Oct <var data-var='date'>24</var>, <var data-var='time'>09:20</var> CEST</small><br><strong>Investigating</strong> - We are experiencing degraded services for a small amount of customers. This means that you can experience for example slow loading speeds. We are investigating the issue and will provide an update as soon as possible.</p>tag:silverfinnv.statuspage.io,2005:Incident/186691632023-10-02T20:10:40+02:002023-10-02T20:10:40+02:00Update Incident 28/09/2023<p><small>Oct <var data-var='date'> 2</var>, <var data-var='time'>20:10</var> CEST</small><br><strong>Resolved</strong> - We’ve concluded our investigation on the incident of last week (28 September). We want to share our analysis in the interest of transparency, even though most environments were not impacted:<br />A rollback to a previous version of Silverfin caused a very limited set of users to have temporary access to client files in another environment. Based on our analysis and detailed logs, we know 34 users in a total of 20 environments were affected. All impacted Silverfin customers have been personally contacted and informed of the specific actions that happened during the 2h time window this change was active.<br />We take security very seriously and have done a thorough root cause analysis. We are working on modifying our process, so this can’t happen in the future, and be detected earlier should a new root cause create a similar outcome. Overall, we would like to apologise that this could happen in the first place.</p>tag:silverfinnv.statuspage.io,2005:Incident/186418222023-09-29T13:54:48+02:002023-09-29T14:13:57+02:00Update on yesterday's downtime<p><small>Sep <var data-var='date'>29</var>, <var data-var='time'>13:54</var> CEST</small><br><strong>Resolved</strong> - English:<br />Yesterday (28 September) you may have noticed that Silverfin was offline for a period of approximately 60 minutes between CET15:02 and CET16:02. We sincerely apologise for any inconvenience caused. Unfortunately we released a software change (as we regularly do each day) that caused an issue that was most quickly and efficiently fixed with the system in maintenance mode. Rest assured that whilst it was unplanned, this outage totally was controlled by the Silverfin technology team and was not any external threat or attack.<br /><br />Nederlands:<br />Gisteren (28 september) heb je misschien gemerkt dat Silverfin offline was voor een periode van ongeveer 60 minuten tussen CET15:02 en CET16:02. Onze oprechte excuses voor het ongemak. Helaas hebben we een software wijziging doorgevoerd (zoals we elke dag doen) die een probleem veroorzaakte dat snel en efficiënt verholpen kon worden met het systeem in onderhoudsmodus. Wees gerust dat, hoewel het ongepland was, deze storing volledig werd gecontroleerd door het Silverfin technologie team en geen externe bedreiging of aanval was.<br /><br />Français:<br />Hier (28 septembre), vous avez peut être remarqué que Silverfin était hors ligne pendant environ 60 minutes entre 15h02 CET et 16h02 CET. Nous nous excusons sincèrement pour tout éventuel désagrément occasionné. Malheureusement, nous avons déployé une mise à jour logiciel (comme nous le faisons régulièrement chaque jour) qui a provoqué un problème. Lequel a été résolu le plus rapidement et le plus efficacement possible en mettant le système en mode maintenance. Nous tenons à vous assurez que, bien que cela n’était pas planifié, cette interruption a été entièrement gérée par l’équipe technologique de Silverfin et n’a pas été due à une menace ou à une attaque externe.</p>tag:silverfinnv.statuspage.io,2005:Incident/186317902023-09-28T16:51:34+02:002023-09-28T16:51:34+02:00Application issues<p><small>Sep <var data-var='date'>28</var>, <var data-var='time'>16:51</var> CEST</small><br><strong>Resolved</strong> - We have closely monitored the incident and successfully addressed the issue. A comprehensive investigation into its impact on both the platform and users is currently ongoing. Once this investigation is complete, we will communicate this.</p><p><small>Sep <var data-var='date'>28</var>, <var data-var='time'>16:03</var> CEST</small><br><strong>Monitoring</strong> - The solution has been successfully applied, and Silverfin is now back online. Due to an application change, you will need to re-login to access the platform. We are conducting a thorough investigation into the impact on the platform. We apologize for any inconvenience this may have caused.</p><p><small>Sep <var data-var='date'>28</var>, <var data-var='time'>15:37</var> CEST</small><br><strong>Identified</strong> - We've identified the root cause and are currently in the process of implementing a solution. Our goal is to restore the platform within the next 30 minutes.</p><p><small>Sep <var data-var='date'>28</var>, <var data-var='time'>15:09</var> CEST</small><br><strong>Update</strong> - At this moment, we are experiencing issues on the platform. In the meantime, we have placed Silverfin in maintenance mode to investigate this further. We will bring Silverfin back online as soon as possible. Our apologies for any inconvenience.</p><p><small>Sep <var data-var='date'>28</var>, <var data-var='time'>14:53</var> CEST</small><br><strong>Investigating</strong> - We've identified issues with the platform, and we are putting it into maintenance mode, for further investigation.</p>tag:silverfinnv.statuspage.io,2005:Incident/181819042023-08-18T09:58:48+02:002023-08-18T09:58:48+02:00Slower response times due to high load<p><small>Aug <var data-var='date'>18</var>, <var data-var='time'>09:58</var> CEST</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Aug <var data-var='date'>18</var>, <var data-var='time'>09:32</var> CEST</small><br><strong>Monitoring</strong> - The incident, regarding slow performance, has been resolved. We are monitoring this now.</p><p><small>Aug <var data-var='date'>18</var>, <var data-var='time'>09:14</var> CEST</small><br><strong>Investigating</strong> - We're currently experiencing slower response time across Silverfin. We're aware of this and are investigating it.</p>tag:silverfinnv.statuspage.io,2005:Incident/180324582023-08-02T17:40:34+02:002023-08-02T17:40:34+02:00Partial downtime in the European region<p><small>Aug <var data-var='date'> 2</var>, <var data-var='time'>17:40</var> CEST</small><br><strong>Resolved</strong> - The systems are up and running again in all regions.<br /><br />During the rollout of a maintenance patch one of the database servers in the European region was restarted. No data was lost during this process.<br /><br />We will investigate why this maintenance patch caused only one of our database servers to restart to ensure we mitigate such issues in future maintenances.</p><p><small>Aug <var data-var='date'> 2</var>, <var data-var='time'>17:26</var> CEST</small><br><strong>Investigating</strong> - We're currently suffering a partial downtime in our European region. We're currently investigating and resolving this issue.</p>tag:silverfinnv.statuspage.io,2005:Incident/178868202023-07-18T13:01:16+02:002023-07-18T13:01:16+02:00Yuki synchronisations experiencing delays<p><small>Jul <var data-var='date'>18</var>, <var data-var='time'>13:01</var> CEST</small><br><strong>Resolved</strong> - Degraded Yuki syncing performance was caused because of a change request of our partner on the Yuki synchronisations. The progress on the final solution still ongoing. If there are delays on the synchronisations, this will now be displayed in the yellow synchronisation bar.</p><p><small>Jul <var data-var='date'>18</var>, <var data-var='time'>10:13</var> CEST</small><br><strong>Identified</strong> - Yuki synchronisations can experience some delays. This is caused of a tuning process to improve Yuki synchronisations in the future. The synchronisation will run, but can stay in the queue for a while. If the sync is failing due Time-out error, please try again via the syncing arrows. We apologise for any inconvenience.</p>tag:silverfinnv.statuspage.io,2005:Incident/178314202023-07-12T13:30:07+02:002023-07-12T13:30:07+02:00Degraded performance<p><small>Jul <var data-var='date'>12</var>, <var data-var='time'>13:30</var> CEST</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jul <var data-var='date'>12</var>, <var data-var='time'>12:28</var> CEST</small><br><strong>Monitoring</strong> - The issue is resolved and files are now syncing again. The remaining queues are now processing. It can take a while till the syncing of the queues are finished. Thank you for your patience.</p><p><small>Jul <var data-var='date'>12</var>, <var data-var='time'>09:29</var> CEST</small><br><strong>Identified</strong> - General performance issues have been solved. You still can experience delays on synchronisations. We are still actively working on this.</p><p><small>Jul <var data-var='date'>12</var>, <var data-var='time'>08:47</var> CEST</small><br><strong>Investigating</strong> - The platform is currently experiencing issues, which is impacting the synchronisations and the performance in general. We are actively working to mitigate the issue.</p>tag:silverfinnv.statuspage.io,2005:Incident/178113572023-07-10T10:52:56+02:002023-07-10T10:52:56+02:00Degraded performance<p><small>Jul <var data-var='date'>10</var>, <var data-var='time'>10:52</var> CEST</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Jul <var data-var='date'>10</var>, <var data-var='time'>10:11</var> CEST</small><br><strong>Update</strong> - We are continuing to monitor for any further issues.</p><p><small>Jul <var data-var='date'>10</var>, <var data-var='time'>09:33</var> CEST</small><br><strong>Update</strong> - We've resolved the issue that was causing degraded application performance. All services are back to normal. We are continuing to monitor the situation</p><p><small>Jul <var data-var='date'>10</var>, <var data-var='time'>09:33</var> CEST</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Jul <var data-var='date'>10</var>, <var data-var='time'>09:03</var> CEST</small><br><strong>Investigating</strong> - The platform is current experiencing a degraded quality of service. You may experience issues including logging in, degraded performance in the synchronisation,.... We are actively working to mitigate the issue.</p>tag:silverfinnv.statuspage.io,2005:Incident/175108802023-06-09T10:36:30+02:002023-06-09T10:36:30+02:00Yuki sync issue<p><small>Jun <var data-var='date'> 9</var>, <var data-var='time'>10:36</var> CEST</small><br><strong>Resolved</strong> - Yuki API was stable last night and we do not longer notice failures in the Yuki sync.</p><p><small>Jun <var data-var='date'> 8</var>, <var data-var='time'>14:07</var> CEST</small><br><strong>Update</strong> - We are continuing to monitor for any further issues.</p><p><small>Jun <var data-var='date'> 8</var>, <var data-var='time'>14:07</var> CEST</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Jun <var data-var='date'> 8</var>, <var data-var='time'>12:53</var> CEST</small><br><strong>Update</strong> - This night and morning there were intermittent issues with Yuki synchronisations, due to some persisting issues with the Yuki API. As result, there is a possibility that a Yuki sync failed. If the sync failed, you can try to sync again. If the problem persists, please contact Silverfin or Yuki support (support@yuki.com).</p><p><small>Jun <var data-var='date'> 8</var>, <var data-var='time'>11:37</var> CEST</small><br><strong>Investigating</strong> - Yesterday, most of the Yuki sync issues were off. This morning, we keep getting tickets about this. As these issues are not at Silverfin's side, we unfortunately cannot help you. We therefore advise you to contact the Yuki support team at support@yuki.be. We are in contact with them as well. As soon as we are informed that the issue is solved, we will update the status page.</p>tag:silverfinnv.statuspage.io,2005:Incident/174981092023-06-07T15:14:10+02:002023-06-07T15:14:10+02:00Delay experience with Synchronisations<p><small>Jun <var data-var='date'> 7</var>, <var data-var='time'>15:14</var> CEST</small><br><strong>Resolved</strong> - We have addressed the main incident causing disruptions to the Yuki Synchronisation service. We are glad to report a marked improvement in service stability. However, we want to bring to your attention that we are still facing intermittent issues with Yuki synchronisations, due to some persisting issues with the Yuki API. As result, there is a possibility that a Yuki sync fails with a (execution expired) message, we receive from the API of Yuki. We have taken measures to prevent Yuki sync issues from affecting the rest of our services.</p><p><small>Jun <var data-var='date'> 7</var>, <var data-var='time'>11:42</var> CEST</small><br><strong>Monitoring</strong> - We identified and solved the issue. All synchronisations, except Yuki synchronisation are running as normal again. We are investigating the error we receive from Yuki. We will update the statuspage as soon we know more.</p><p><small>Jun <var data-var='date'> 7</var>, <var data-var='time'>09:33</var> CEST</small><br><strong>Investigating</strong> - We are experiencing higher load in part of our infrastructure. We are currently investigating the issue. Until this is resolved, you can experience a slow or stuck synchronisation.</p>tag:silverfinnv.statuspage.io,2005:Incident/169702522023-04-26T16:58:10+02:002023-04-26T16:58:10+02:00We are experiencing higher load in part of our infrastructure.<p><small>Apr <var data-var='date'>26</var>, <var data-var='time'>16:58</var> CEST</small><br><strong>Resolved</strong> - This issue is solved.</p><p><small>Apr <var data-var='date'>26</var>, <var data-var='time'>14:31</var> CEST</small><br><strong>Monitoring</strong> - We have deployed infrastructure changes that have mitigated the issue, but we are still actively monitoring.</p><p><small>Apr <var data-var='date'>26</var>, <var data-var='time'>11:25</var> CEST</small><br><strong>Identified</strong> - We are experiencing higher load in part of our infrastructure. The root cause has been identified and we are implementing mitigations. Until this is resolved, users may experience parts of functionality working slower than usual.</p>tag:silverfinnv.statuspage.io,2005:Incident/169102122023-04-19T14:57:15+02:002023-04-19T14:57:15+02:00Issues on downloading a document<p><small>Apr <var data-var='date'>19</var>, <var data-var='time'>14:57</var> CEST</small><br><strong>Resolved</strong> - Everything works as expected again. Issue is resolved.</p><p><small>Apr <var data-var='date'>19</var>, <var data-var='time'>13:58</var> CEST</small><br><strong>Monitoring</strong> - Fix has been implemented. We are monitoring this now.</p><p><small>Apr <var data-var='date'>19</var>, <var data-var='time'>13:01</var> CEST</small><br><strong>Identified</strong> - We are experiencing some issues when you want to download a document from Silverfin. A new version resolving the issue is being deployed now.</p>tag:silverfinnv.statuspage.io,2005:Incident/167099342023-04-16T12:20:05+02:002023-04-16T12:20:05+02:00Scheduled Maintenance Notice: Silverfin Downtime on April 15-16<p><small>Apr <var data-var='date'>16</var>, <var data-var='time'>12:20</var> CEST</small><br><strong>Completed</strong> - The maintenance has been completed successfully, and all systems are back to normal. Thank you for your patience and understanding during this time. If you experience any issues, please don't hesitate to contact our support team.</p><p><small>Apr <var data-var='date'>16</var>, <var data-var='time'>11:23</var> CEST</small><br><strong>Update</strong> - We apologize for the inconvenience, but we wanted to inform you that the maintenance is taking longer than expected. Based on our test runs, we anticipated the maintenance to finish earlier, but it will require additional time to complete. We appreciate your patience and understanding.</p><p><small>Apr <var data-var='date'>15</var>, <var data-var='time'>20:00</var> CEST</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'>31</var>, <var data-var='time'>16:37</var> CEST</small><br><strong>Scheduled</strong> - We would like to inform you about an upcoming scheduled maintenance for Silverfin, which will require a temporary downtime. This maintenance is part of our ongoing commitment to provide you with the best possible user experience.<br /><br />The maintenance window is as follows:<br /><br />Start: April 15, 2023, at 20:00 CEST<br />End: April 16, 2023, at 12:00 CEST (noon)<br /><br />During this time, the Silverfin platform will be inaccessible. We understand the inconvenience this may cause, and we appreciate your patience and understanding as we perform this necessary maintenance to improve our platform.<br /><br />Please make sure to plan accordingly and complete any critical tasks on Silverfin before the maintenance period begins.<br /><br />We will do our best to complete the maintenance as quickly as possible and minimize any disruptions. Once the maintenance is completed, you will be able to access Silverfin and all its features as usual. All operations around the platform, including syncs, will resume immediately.<br /><br />If you have any questions or concerns, please don't hesitate to contact our support team at support@silverfin.com.<br /><br />Thank you for your support and understanding.<br /><br />Best regards,<br />Silverfin</p>tag:silverfinnv.statuspage.io,2005:Incident/166948452023-03-30T09:36:35+02:002023-03-30T09:39:40+02:00Degraded performance<p><small>Mar <var data-var='date'>30</var>, <var data-var='time'>09:36</var> CEST</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Mar <var data-var='date'>30</var>, <var data-var='time'>09:30</var> CEST</small><br><strong>Identified</strong> - The issue has been identified and a fix is being implemented.</p><p><small>Mar <var data-var='date'>30</var>, <var data-var='time'>09:25</var> CEST</small><br><strong>Investigating</strong> - The platform is currently experiencing a higher-than-usual load, which is impacting performance. We are actively working to mitigate the issue.</p>tag:silverfinnv.statuspage.io,2005:Incident/166857172023-03-29T13:36:54+02:002023-03-29T13:49:19+02:00Degraded performance<p><small>Mar <var data-var='date'>29</var>, <var data-var='time'>13:36</var> CEST</small><br><strong>Resolved</strong> - This incident has been resolved and all our users should no longer be affected by any performance issues.</p><p><small>Mar <var data-var='date'>29</var>, <var data-var='time'>12:07</var> CEST</small><br><strong>Investigating</strong> - The platform is currently experiencing a higher-than-usual load, which is impacting performance. We are actively working to mitigate the issue.</p>tag:silverfinnv.statuspage.io,2005:Incident/164196192023-03-10T17:48:54+01:002023-03-10T17:48:54+01:00Some users may notice issues when creating new reports. We're actively working on this issue.<p><small>Mar <var data-var='date'>10</var>, <var data-var='time'>17:48</var> CET</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Mar <var data-var='date'>10</var>, <var data-var='time'>15:22</var> CET</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Mar <var data-var='date'>10</var>, <var data-var='time'>15:16</var> CET</small><br><strong>Investigating</strong> - We are currently investigating this issue.</p>tag:silverfinnv.statuspage.io,2005:Incident/162212632023-02-21T15:52:10+01:002023-02-21T15:52:10+01:00A faulty deploy caused degraded performance which we quickly reverted.<p><small>Feb <var data-var='date'>21</var>, <var data-var='time'>15:52</var> CET</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Feb <var data-var='date'>21</var>, <var data-var='time'>15:03</var> CET</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Feb <var data-var='date'>21</var>, <var data-var='time'>14:50</var> CET</small><br><strong>Identified</strong> - The issue has been identified and a fix is being implemented.</p>