Sep <var data-var='date'>23</var>, <var data-var='time'>06:00</var> CEST Resolved - Root cause: a network switch failed — the kind of thing our setup is built to shrug off without anyone noticing. This time, failover didn't kick in the way it should have, so the failure took prod down with it instead of quietly stepping aside. We've restored service by rebooting the switch, and a full root cause analysis is underway to find out why the safety net had a day off. The total downtime was 2 hours and 14 minutes between 06:03 and 08:17. We'll share more once we know more.

Service outage

Sep <var data-var='date'>23</var>, <var data-var='time'>06:00</var> CEST Resolved - Down since 06:10 today. Not slow, not flaky — down. If you're trying to reach us and getting nothing back, that's not your connection, that's ours. Our team is on it and treating it with the appropriate level of "why is everything dark." We'll post again the moment we have a real update — or the moment the network lets us. Update 08:22 Root cause: a network switch failed — the kind of thing our setup is built to shrug off without anyone noticing. This time, failover didn't kick in the way it should have, so the failure took prod down with it instead of quietly stepping aside. We've restored service by rebooting the switch, and a full root cause analysis is underway to find out why the safety net had a day off. We'll share more once we know more. Thanks for bearing with us.

Network Outage

Jun <var data-var='date'>18</var>, <var data-var='time'>09:39</var> CEST Resolved - Good news, everyone! The urgent maintenance on our network switches is officially complete, and all systems are firing on all cylinders. As it turns out, the ancient IT ritual of "turning it off and on again" works wonders. While there was indeed a brief, scheduled snooze for our services during the restart, we have successfully vanquished the root cause of last week's lingering network gremlins. The system is now significantly more stable, and our engineering team is currently high-fiving in the hallway. The Post-Game Report: Status: Fully Resolved (and we are thoroughly pleased about it). Impact: A tiny, temporary nap for our servers during the reboot window, but performance is back to a crisp 100%. Resolution: The stubborn switches have been restarted, optimized, and taught some manners. Thank you so much for your patience, your trust, and for bearing with us through a brief moment of silence while we chased down the root cause! Jun <var data-var='date'>17</var>, <var data-var='time'>14:25</var> CEST Monitoring - A fix has been implemented and we are monitoring the results. Jun <var data-var='date'>17</var>, <var data-var='time'>14:25</var> CEST Update - We are continuing to work on a fix for this issue. Jun <var data-var='date'>17</var>, <var data-var='time'>12:37</var> CEST Update - We are continuing to work on a fix for this issue. Jun <var data-var='date'>17</var>, <var data-var='time'>11:59</var> CEST Identified - As a follow-up to last week's brief service disruption caused by a faulty switch, our engineering team is performing an urgent, proactive restart on two of our network switches to completely resolve the remaining lingering issues. While we fully expect operations to continue as normal during this window, we want to be entirely transparent: there is a small possibility of a brief service interruption lasting less than 30 minutes. Restarts will begin 12:15 today. Note: Our team is actively monitoring all systems to ensure minimal to no impact on your workflow. We will post a final update here as soon as the restart is successfully completed. Thank you for your patience and understanding as we work to ensure maximum platform stability!

Urgent Network Switch Optimization

Jun <var data-var='date'>11</var>, <var data-var='time'>12:55</var> CEST Resolved - The issue has now been resolved. All components are stable and operational. Jun <var data-var='date'>11</var>, <var data-var='time'>11:58</var> CEST Investigating - We have experienced a temporary internal network disruption. No login was possible during the event. We are currently investigating the issue and will post updates as we learn more.

Temporary internal network disruption

Feb <var data-var='date'> 6</var>, <var data-var='time'>11:18</var> CET Resolved - This incident has been resolved. Feb <var data-var='date'> 5</var>, <var data-var='time'>08:41</var> CET Update - The problem has been identified by Danske Bank. They are currently working on a solution. We are continuing to monitor the situation and will add more updates as we learn more. Feb <var data-var='date'> 3</var>, <var data-var='time'>13:12</var> CET Monitoring - Danske Bank has confirmed a delay in the delivery of invoice files. The issue originates with Danske Bank, and they are currently working on a resolution. We are monitoring this and will update this status once we know more, or the problem has been resolved.

Delayed invoice files from Danske Bank

Oct <var data-var='date'> 1</var>, <var data-var='time'>14:59</var> CEST Resolved - This incident has been resolved. Oct <var data-var='date'> 1</var>, <var data-var='time'>13:58</var> CEST Identified - Payments through Swish are currently unavailable. We're looking into the issue and will update this incident when we learn more.

Swish payments issue

Sep <var data-var='date'>26</var>, <var data-var='time'>16:03</var> CEST Resolved - This incident has been resolved. Sep <var data-var='date'>25</var>, <var data-var='time'>14:52</var> CEST Monitoring - We are currently experiencing an issue with connecting Mastercards to the platform. We are monitoring the situation closely and will update this incident as soon as the issue is resolved.

Mastercard connection issue

Sep <var data-var='date'>20</var>, <var data-var='time'>16:01</var> CEST Completed - The scheduled maintenance has been completed. Sep <var data-var='date'>20</var>, <var data-var='time'>10:00</var> CEST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Aug <var data-var='date'>22</var>, <var data-var='time'>17:20</var> CEST Scheduled - We hope you’re having a great summer! Unfortunately, we had a bit of a mishap in August - our platform went down for a brief period due to some faulty hardware and a few minor issues that combined to cause chaos. Don’t worry, it was quickly resolved, but we’re determined to make sure something like this doesn’t happen again. We take the stability of our platform very seriously (as you might have gathered by now), and we’re always looking for ways to improve. So, we’ve decided to do some behind-the-scenes work to boost our resilience and prevent any future surprises. And that’s where our scheduled maintenance window comes in… On September 20th, we’ll be taking a brief timeout (don’t worry, it won’t take long!) to update our systems and make sure everything is running smoothly. This will help us provide an even better experience for you in the long run. To reiterate: this maintenance window is scheduled to minimize any potential impact on your work. We’re confident that with these upgrades, we can keep our platform running like a well-oiled machine (or at least, that’s the plan!). If you have any questions or concerns, please don’t hesitate to reach out. We appreciate your understanding and cooperation as we strive to continually improve our services. Thanks for choosing Findity!

Improve network resilience

Aug <var data-var='date'>18</var>, <var data-var='time'>10:10</var> CEST Resolved - This incident has been resolved. Aug <var data-var='date'>18</var>, <var data-var='time'>08:00</var> CEST Update - We are continuing to investigate this issue. Aug <var data-var='date'>18</var>, <var data-var='time'>07:01</var> CEST Investigating - At the moment we are experiencing issues with access to the service. We are currently working to resolve this.

Access issue

Jul <var data-var='date'> 1</var>, <var data-var='time'>16:59</var> CEST Resolved - This incident has been resolved. Jun <var data-var='date'>30</var>, <var data-var='time'>14:17</var> CEST Monitoring - We're currently experiencing an issue with the integration to Fortnox Payroll. Fortnox are currently attempting to find a solution to this. We don't currently have an estimated time for when the issue will be resolved, but it's a high priority, and we'll update our status page as soon as we have more information.

Integration issue with Fortnox Payroll

May <var data-var='date'> 7</var>, <var data-var='time'>07:09</var> CEST Resolved - This incident has been resolved. May <var data-var='date'> 5</var>, <var data-var='time'>11:18</var> CEST Identified - The issue has been identified and a fix is being implemented.

We are currently experiencing issues retrieving card transactions from Handelsbanken.

May <var data-var='date'> 1</var>, <var data-var='time'>05:30</var> CEST Resolved - This incident has been resolved. Apr <var data-var='date'>29</var>, <var data-var='time'>11:41</var> CEST Identified - The issue has been identified and a fix is being implemented.

We're currently experiencing some delay in email delivery to outlook hosted domains

Apr <var data-var='date'>27</var>, <var data-var='time'>18:00</var> CEST Completed - The scheduled maintenance has been completed. Apr <var data-var='date'>25</var>, <var data-var='time'>18:00</var> CEST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Mar <var data-var='date'>26</var>, <var data-var='time'>17:33</var> CET Scheduled - We hope this finds you well. At Findity, we take pride in our ability to perform most maintenance tasks without causing any fuss. But, as with all good things, there's an exception to the rule. To ensure our platform continues to hum along smoothly, we're embarking on a project to update our public IP addresses. We know what you're thinking: "IP addresses? Who gets excited about those?" Well, we do! (Just kidding, but they are important.) The good news is that this update won't require any drastic changes from your end. However, it does mean we'll be scheduling a maintenance window over the weekend (Saturday, 26 April to Sunday, 27 April). The actual downtime will likely be brief, but please note that DNS propagation might take up to 48 hours to complete. To make things easier for you, our new IP range is 46.246.120.64/28. If you've got whitelisting configured for our existing IP addresses, just update those bad boys and we're good to go! We apologize in advance for any inconvenience this might cause and appreciate your understanding as we work on making Findity an even better platform. If you have any questions or concerns, feel free to reach out. We're always here to help. Thanks for your continued support, and happy maintenance window-ing!

We're Updating Our IP Addresses (Don't Panic!)

Apr <var data-var='date'> 1</var>, <var data-var='time'>16:37</var> CEST Resolved - This incident has been resolved. Apr <var data-var='date'> 1</var>, <var data-var='time'>15:27</var> CEST Investigating - Some users may be unable to access our platform due to network-related issues. Our team is actively working on a solution, and we expect services to be restored soon. Thank you for your patience!

Platform Access Disruption

Mar <var data-var='date'>18</var>, <var data-var='time'>12:05</var> CET Resolved - This incident has been resolved. Mar <var data-var='date'>18</var>, <var data-var='time'>11:15</var> CET Identified - When sending reports to the integrations we are experiencing longer loading times for the files to be created.

Longer loading times for sending reports

Dec <var data-var='date'> 5</var>, <var data-var='time'>11:48</var> CET Resolved - This incident has been resolved. Dec <var data-var='date'> 2</var>, <var data-var='time'>08:48</var> CET Identified - The issue has been identified and a fix is being implemented. Nov <var data-var='date'>28</var>, <var data-var='time'>11:26</var> CET Investigating - There is currently an issue with the integration to Infobric, meaning it is currently not possible to fetch trips or see any vehicle from the Expense platform due to a login issue. We are currently investigating this.

Infobric - Not possible to fetch trips and see any vehicles

Nov <var data-var='date'>25</var>, <var data-var='time'>09:51</var> CET Resolved - This incident has been resolved. Nov <var data-var='date'>25</var>, <var data-var='time'>09:50</var> CET Update - We are continuing to monitor for any further issues. Nov <var data-var='date'>18</var>, <var data-var='time'>11:39</var> CET Monitoring - All duplicates have now been deleted, meaning the users should be able to sent their transaction just as normal. A very few numbers of transactions are yet to reach the platform. We are still investigating this with OpenCard, but for the majority of the users using Nordea First Card Real Time, things should be operational by now. Nov <var data-var='date'>12</var>, <var data-var='time'>08:25</var> CET Identified - The issue has been identified and our developers are currently working to solve this. Nov <var data-var='date'>11</var>, <var data-var='time'>11:51</var> CET Investigating - Users who have had their transactions from Nordea First Card invoiced are reporting that the invoiced transactions present themselves as duplicates. Meaning both transactions with an attached image along with a duplicate without an attached image is visible. We are currently investigating this and will update the status page once more information is available.

Duplicates of transactions (Nordea First Card)

Nov <var data-var='date'>11</var>, <var data-var='time'>06:53</var> CET Resolved - This incident has been resolved. Nov <var data-var='date'> 5</var>, <var data-var='time'>09:16</var> CET Monitoring - We will update once the system is up and running as normal again.

Due to an issue at the Nordea there is a delay in the delivery of cleared and invoiced transactions.

Oct <var data-var='date'>30</var>, <var data-var='time'>06:54</var> CET Resolved - This incident has been resolved. Oct <var data-var='date'>24</var>, <var data-var='time'>14:30</var> CEST Investigating - We are aware that some users are experiencing issues with SSO login in the latest version of our iOS app. Our team is investigating and working on a fix. In the meantime, we refer affected users to the web-version since this is isolated to the iOS app. Thank you for your patience.

SSO Login Issues in Latest iOS App

Oct <var data-var='date'>24</var>, <var data-var='time'>07:25</var> CEST Resolved - The issue was resolved around 16:00 CET yesterday. Oct <var data-var='date'>23</var>, <var data-var='time'>14:41</var> CEST Update - Work is still ongoing and the new estimated time until this is resolved is 16:00 CET. After that things are expected to go back to normal. Oct <var data-var='date'>23</var>, <var data-var='time'>09:47</var> CEST Identified - We are currently experiencing issues with our network equipment, which may cause minor disruptions for some users. Our team is actively working to resolve the problem, and we expect to have everything back to normal by 14:30 CET.

Network Equipment Issues - Ongoing Maintenance

Sep <var data-var='date'>20</var>, <var data-var='time'>10:10</var> CEST Resolved - This incident has been resolved. Sep <var data-var='date'>20</var>, <var data-var='time'>09:43</var> CEST Update - We are continuing to investigate this issue. Sep <var data-var='date'>20</var>, <var data-var='time'>09:42</var> CEST Investigating - We are currently experiencing an issue where users of Findity and Handelsbanken Expense are unable to sign in to the app-version. Our team is actively investigating the situation and will provide updates as soon as more information becomes available. Please note, this issue is limited to users of Findity's expense solution and Handelsbanken Expense only. In the meanwhile, we urge users to sign in to our web version if need be.

Problem signing in to the app (Findity + Handelsbanken Expense)

Jul <var data-var='date'> 4</var>, <var data-var='time'>11:05</var> CEST Resolved - This incident has been resolved. Jul <var data-var='date'> 4</var>, <var data-var='time'>10:42</var> CEST Investigating - Currently, there seem to be issues contacting Findity by phone. We are investigating this together with our provider Telenor. In the meantime, please contact us via support@findity.com. This status will be updated once more information is available.

Issues calling Findity

Apr <var data-var='date'>16</var>, <var data-var='time'>09:39</var> CEST Resolved - This incident has been resolved. Apr <var data-var='date'>16</var>, <var data-var='time'>08:43</var> CEST Identified - Currently there is a issue with analyzing receipts on new expenses. Users can still create new expenses and fill in the information manually. Findity will update this status once more information is available.

Problems analyzing receipts

Apr <var data-var='date'>10</var>, <var data-var='time'>10:07</var> CEST Resolved - This incident has been resolved. Apr <var data-var='date'>10</var>, <var data-var='time'>07:43</var> CEST Investigating - Users are currently experiencing problems connecting to the login page, which users are affected depends on which internet provider they use, affected internet providers are Telia and Bahnhof etc.

Problems connecting to the login page

Apr <var data-var='date'> 4</var>, <var data-var='time'>07:59</var> CEST Resolved - This incident has been resolved. Apr <var data-var='date'> 3</var>, <var data-var='time'>10:23</var> CEST Monitoring - Fortnox have some issues with their services and you can follow the issue here : status.fortnox.se . This might cause some problems with sending reports to Fortnox Bokföring and Fortnox Lön. We will update this status when we know more.

Is Findity down?

Findity status is UP

Lastest published events

Service outage

Network Outage

Urgent Network Switch Optimization

Findity Services, Components and Regions

Recent Findity events

Service outage

Network Outage

Urgent Network Switch Optimization

Temporary internal network disruption

Delayed invoice files from Danske Bank

Swish payments issue