Oneflow Outage History

Oneflow is up right now

Pingoru has recorded 90 incidents for Oneflow: 70 in the last 12 months and 7 in the last 90 days.

Source: status.oneflow.com

90incidents recorded
70last 12 months
7last 90 days
under a minutetypical duration
Incidents per month
02040AprMayJunJulAugSepOctNov0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOctNov0%
Pingoru began tracking Oneflow in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202630 of 720 (0%)
May 2026370 of 744 (0%)
June 2026100 of 720 (0%)
July 202630 of 744 (0%)
August 202670 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 744 (0%)
November 202600 of 8 (0%)

Incidents, newest first

Minor October 25, 2025 Website recovered –

Started Oct 25, 2025, 04:28 AM UTC· resolved Oct 25, 2025, 04:28 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor October 21, 2025 Temporary performance issues 8m section-195029 (Platform (Application))

Started Oct 21, 2025, 01:12 PM UTC· resolved Oct 21, 2025, 01:20 PM UTC

  1. investigating Oct 21, 2025, 01:12 PM UTC

    We've identified degraded performance and elevated error rates for some users due to underlying cloud provider issues

  2. resolved Oct 21, 2025, 01:20 PM UTC

    Performance issues solved. Apologies for the inconvenience

Read the full incident report →

Minor October 21, 2025 Help center recovered 10m

Started Oct 21, 2025, 12:31 PM UTC· resolved Oct 21, 2025, 12:41 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor October 14, 2025 Website recovered –

Started Oct 14, 2025, 02:39 PM UTC· resolved Oct 14, 2025, 02:39 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor September 4, 2025 Temporary issues with publishing (sending) documents 18m section-195029 (Platform (Application))

Started Sep 04, 2025, 02:50 PM UTC· resolved Sep 04, 2025, 03:08 PM UTC

  1. investigating Sep 04, 2025, 02:50 PM UTC

    A small amount of users may currently be unable to publish documents at this time. We’ve identified the issue and our engineering team is actively working on a resolution. We’ll provide updates here as soon as more information is available.

  2. resolved Sep 04, 2025, 03:08 PM UTC

    We have identified the root cause and the issue is now resolved! Thank you for your patience.

Read the full incident report →

Minor May 19, 2025 Temporary performance issues (counterpart view) 21m section-195029 (Platform (Application))

Started May 19, 2025, 11:42 AM UTC· resolved May 19, 2025, 12:03 PM UTC

  1. investigating May 19, 2025, 11:42 AM UTC

    Currently we are experiencing some performance issues that are affecting the document view for counterparts. Our engineers are investigating the matter with highest priority.

  2. resolved May 19, 2025, 12:03 PM UTC

    The issue is resolved and performance is back to normal. Thank you for your patience.

Read the full incident report →

Minor May 19, 2025 Sporadic performance issues 20m section-195029 (Platform (Application))

Started May 19, 2025, 08:47 AM UTC· resolved May 19, 2025, 09:07 AM UTC

  1. investigating May 19, 2025, 08:47 AM UTC

    Currently we are experiencing some sporadic performance issues. Our engineers are investigating the matter with highest priority.

  2. resolved May 19, 2025, 09:07 AM UTC

    Our technical team has resolved the platform issue and we are back at full functionality. Thank you for your patience.

Read the full incident report →

Minor May 15, 2025 Connectivity issues 15m section-195029 (Website)

Started May 15, 2025, 09:45 AM UTC· resolved May 15, 2025, 10:00 AM UTC

  1. investigating May 15, 2025, 09:45 AM UTC

    Some users are currently experiencing issues reaching our website. You can still login to the application at https://app.oneflow.com. We are working to recover the website.

  2. resolved May 15, 2025, 10:00 AM UTC

    All services are restored.

Read the full incident report →

Minor May 5, 2025 Sporadic network issues 8m section-195029 (Platform (API)), section-195029 (Platform (Application))

Started May 05, 2025, 07:15 PM UTC· resolved May 05, 2025, 07:23 PM UTC

  1. investigating May 05, 2025, 07:15 PM UTC

    Some users are facing difficulties reaching Oneflow sporadically. We are investigating.

  2. resolved May 05, 2025, 07:23 PM UTC

    Underlying network issues have been resolved.

Read the full incident report →

Minor April 23, 2025 Swedish bankID Experiencing Issues 11h 35m section-195029 (Platform (Application))

Started Apr 23, 2025, 07:08 PM UTC· resolved Apr 24, 2025, 06:43 AM UTC

  1. investigating Apr 23, 2025, 07:08 PM UTC

    Swedish BankID is currently experiencing some issues affecting the functionality. We're monitoring to find a solution with highest priority.

  2. resolved Apr 24, 2025, 06:43 AM UTC

    Swedish bankID functionality has been stabilised and we are marking the issue as resolved. We thank you for your patience.

Read the full incident report →

Minor April 15, 2025 Experiencing issues with Swedish bankID 1h 21m section-195029 (Platform (Application))

Started Apr 15, 2025, 11:42 AM UTC· resolved Apr 15, 2025, 01:03 PM UTC

  1. investigating Apr 15, 2025, 11:42 AM UTC

    Currently we are experiencing some issues affecting Swedish bankID. Monitoring to find a solution as soon as possible

  2. resolved Apr 15, 2025, 01:03 PM UTC

    Swedish bankID is now stable and the issue is resolved. We thank you for your patience.

Read the full incident report →

Minor April 14, 2025 Temporary performance issues 9m section-195029 (Platform (Application))

Started Apr 14, 2025, 06:20 AM UTC· resolved Apr 14, 2025, 06:29 AM UTC

  1. investigating Apr 14, 2025, 06:20 AM UTC

    Currently we are experiencing some performance issues due to network issues. Our engineers are investigating the matter with highest priority.

  2. resolved Apr 14, 2025, 06:29 AM UTC

    All Oneflow services are stable again and the issue is resolved. We thank you for your patience.

Read the full incident report →