Is Silverfin down?

We are currently receiving reports that some users are encountering the error message: "There was an issue getting your page." Our team is actively investigating the issue and working to identify the root cause. We will provide updates as soon as more information becomes available. Our apologies for the inconvenience.

Silverfin experienced a temporary increase in system load, which caused some service issues. Everything should now be working as expected. If you continue to experience any issues, please contact our Support team directly. We apologize for any inconvenience caused.

We are aware that workflows and reconciliations might be experiencing slowness/failing to load certain parts. We are working on resolving this as soon as possible. Our apologies for the inconvenience!

The cause of the slowness has been resolved. Once again our apologies for the inconvenience!

We are aware there was a brief login issue for multiple users. While migrating firms to our new sign-in solution, we made a mistake for multiple firms, blocking some users from accessing their firms. This has been resolved and should no longer be blocking users from accessing Silverfin. Our sincere apologies for the inconvenience!

This incident has been resolved.

We are receiving reports that users are experiencing issues/error message ("There was an issue getting your page") accessing workflows within the files. Our developers are aware of the issue and are currently investigating it.

We are receiving reports that users are experiencing issues/error message ("There was an issue getting your page") accessing workflows within the files. Our developers are aware of the issue and are currently investigating it.

Following the update we provided, the issue with accessing workflows has been resolved and the situation is now stable again.

If you are experiencing Exact Online issues, please let an admin user re-authenticate this connection. If you are noticing mapping issues, we are currently still investigating the issue.

We are currently investigating an issue affecting the sync performance and application speed. We are actively working on a resolution. Updates will be communicated as soon as they are available.

To alleviate platform-wide slowdowns caused by high data volume, we have implemented batch processing to manage the workload more efficiently. While the general platform looks stable now, please note that some synchronizations may experience temporary delays as we process the remaining queue.

We notice the platform is still experiencing a general delay impacting syncs, mapping, and manual uploads. We are processing the remaining as quickly as possible. Our apologies for the inconveniences!

We continue to experience syncing delays due to the large volume of data being processed. We are actively working to mitigate this issue and will provide regular updates throughout the day.

Our technical team is currently taking action to resolve the ongoing sync issues. Our next steps will be: All current syncs will be cancelled so that the sync queues are reset. This should unblock affected client files so you can continue working again. After that, if you are (still) seeing an error message in a file, you will be able to restart the sync for that specific client file by clicking the sync button at the top of the file page. New syncs may run a bit slower at first, but they are expected to complete successfully. We are treating this issue with the highest priority and will continue to monitor the situation closely. The next update will be provided at 13:00 CET.

We have implemented a solution and are actively monitoring the situation. You may experience minor delays until your sync begins and is processed, as we are working through a significant backlog. The next update is scheduled for 3 PM CET.

The solution we implemented is stable, and we continue to monitor the situation with priority. Minor sync delays may still occur. The next update is scheduled for 5 PM CET.

The solution we implemented is still running stably, and we will continue monitoring the backlog overnight. If you still encounter an error in your file, you can always trigger the sync manually (at the top of the page), but minor delays may still occur. The next update is scheduled for Wednesday, 25/3 at 9:00 CET.

The solution we implemented is still running stably, and we will continue monitoring the backlog overnight. If you still encounter an error in your file, you can always trigger the sync manually (at the top of the page), but minor delays may still occur. The next update is scheduled for Wednesday, 25/3 at 9:00 CET.

Our nightly sync completed successfully, and file syncing is now behaving normally. We will continue to monitor the situation, and the next update is expected at 12 PM. If you notice anything out of the ordinary, please contact support.

Our nightly sync completed successfully, and file syncing is now behaving normally. We will continue to monitor the situation, and the next update is expected at 12 PM. If you notice anything out of the ordinary, please contact support.

Following the implemented solution, sync behavior has returned to normal, and mapping issues have been restored. Please address any future sync-related issues to the support team. This incident will now be closed.