BlueDolphin Outage History

BlueDolphin is up right now

BlueDolphin had 7 outages in the last 2 years totaling 45h 45m of downtime, averaging 0.3 incidents per month.

There were 7 BlueDolphin outages since March 17, 2025 totaling 45h 45m of downtime. Each is summarised below. Incident details, duration, and resolution information.

Source: status.bluedolphin.app

Minor October 29, 2025

BD Performance Issues

Detected by Pingoru
Oct 29, 2025, 04:14 PM UTC
Resolved
Oct 30, 2025, 08:56 AM UTC
Duration
16h 41m
Affected: BlueDolphin FrontEnd ServicesBlueDolphin BackEnd Services
Timeline · 4 updates
  1. investigating Oct 29, 2025, 04:14 PM UTC

    Dear BlueDolphin user, Starting at 16:45, a portion of customers experienced an authentication issue. There is an ongoing issue with our cloud provider. We will keep you posted.

  2. identified Oct 29, 2025, 04:47 PM UTC

    Starting at approximately 16:00 UTC, Azure began experiencing DNS issues, resulting in the availability degradation of some services. BlueDophin is dependent on the Azure CDN service which is currently inaccessible.

  3. monitoring Oct 29, 2025, 07:25 PM UTC

    Workaround is applied. BlueDolphin is healthy. Performances are not as expected. We are waiting for Azure to resolve the issue with DNS services so that we can roll back our changes. We will continue to monitor.

  4. resolved Oct 30, 2025, 08:56 AM UTC

    This incident has been resolved.

Read the full incident report →

Major October 20, 2025

Login Issues On BlueDolphin

Detected by Pingoru
Oct 20, 2025, 07:44 AM UTC
Resolved
Oct 20, 2025, 10:58 AM UTC
Duration
3h 14m
Affected: BlueDolphin FrontEnd Services
Timeline · 3 updates
  1. investigating Oct 20, 2025, 07:44 AM UTC

    We are currently investigating this issue.

  2. monitoring Oct 20, 2025, 08:58 AM UTC

    What happened? Around 8:50 AM CET an issue with login to the tenants was encountered. What went wrong and why? We identified that the login flow we use rely on AWS services which are currently experiencing service degradation. How did we respond? As a fix we have removed the dependency on AWS services, after which we can see login flow is back to normal. 8:50 CET on 20-10-2025 – Customer impact began 9:00 CET on 20-10-2025 – Investigation commenced by our DevOps and Back-End team. 9:30 CET on 20-10-2025 – Issue identified. 10:00 CET on 20-10-2025 – Change implementation commenced to resolve issue. 10:40 CET on 20-10-2025 – Login flow is back to normal. How are we making incidents like this less likely or less impactful? We will review our dependencies with third party tools/applications to avoid single point of failures.

  3. resolved Oct 20, 2025, 10:58 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice October 17, 2025

Authentication Issues - SAML SSO Users - US Customers

Detected by Pingoru
Oct 17, 2025, 02:00 PM UTC
Resolved
Oct 17, 2025, 03:00 PM UTC
Duration
1h
Timeline · 1 update
  1. resolved Oct 17, 2025, 03:25 PM UTC

    What happened? Between 15:00 and 17:00 CET, a portion of customers experienced an authentication issue. There was a problem with SAML endpoint and its certificate. Users were unable to obtain a new access token. What went wrong and why? Automatic renewal jobs were not correctly set. How did we respond? The error was corrected by manual intervention of the infra team. 15:20 CET on 17-10-2025 – Customer impact began, triggered by the issue described above. 15:30 CET on 17-10-2025 – Investigation started, issue detected on US for SAML users. 15:40 CET on 17-10-2025 – Issue mittigation started. 16:00 CET on 17-10-2025 - Fix applied. Propagation takes up to 2h How are we making incidents like this less likely or less impactful? We will implement proper automatic certificate renewal and validation jobs, including monitoring and alerting in case of failures.

Read the full incident report →

Minor April 30, 2025

Couple of Reports not working

Detected by Pingoru
Apr 30, 2025, 07:42 AM UTC
Resolved
May 01, 2025, 07:25 AM UTC
Duration
23h 43m
Affected: BlueDolphin FrontEnd Services
Timeline · 4 updates
  1. investigating Apr 30, 2025, 07:42 AM UTC

    We are currently investigating an incident that is impacting a few reports that are not visible on BlueDolphin. We apologize for any inconvenience this may cause and are working to resolve the issue as quickly as possible. At this time, we do not have any further details on the cause of the incident or an estimated time for resolution. We will provide updates as we have them, and appreciate your patience while we work to resolve the issue.

  2. identified Apr 30, 2025, 09:06 AM UTC

    We have identified the cause of the incident on reports missing and are implementing a solution. We apologize for any inconvenience and will keep you informed as we have more information. Thank you for your understanding as we work to fix the problem.

  3. monitoring Apr 30, 2025, 11:00 AM UTC

    We fixed the cause of the incident and are closely monitoring the situation to ensure the issue is fully resolved. We apologize for any inconvenience and will keep you informed as we have more information. Thank you for your understanding as we work to fix the problem.

  4. resolved May 01, 2025, 07:25 AM UTC

    We are pleased to inform you that the issue has been resolved.

Read the full incident report →

Notice April 11, 2025

Reporting Service Affected

Detected by Pingoru
Apr 11, 2025, 08:54 AM UTC
Resolved
Apr 11, 2025, 09:11 AM UTC
Duration
17m
Affected: BlueDolphin FrontEnd Services
Timeline · 2 updates
  1. monitoring Apr 11, 2025, 08:54 AM UTC

    Reporting service went down during routine operations of exporting report. We were working resolving an issue related to reporting which led to high Memory and CPU usage causing Reporting service to crash. Reporting service is up and currently running. We are monitoring.

  2. resolved Apr 11, 2025, 09:11 AM UTC

    Issue has been resolved.

Read the full incident report →

Notice March 17, 2025

BlueDolphin Error

Detected by Pingoru
Mar 17, 2025, 02:55 PM UTC
Resolved
Mar 17, 2025, 03:10 PM UTC
Duration
15m
Timeline · 1 update
  1. resolved Mar 17, 2025, 04:08 PM UTC

    What happened? Between 15:55 and 16:09 CET on 17 March 2025, EU and US customers experienced issues when accessing BlueDolphin What went wrong and why? Due to the technical (security release) access to keyvault certificates from our application gateways was blocked. Application gateways and Firewalls stopped providing services to Frontend and Backend. How did we respond? 15:55 CET – Customer impact began 15:56 CET – Alerts fired first for US region and then for EU. 15:57 CET – BlueDolphin Support Team raised the issue. 15:57 CET - Our engineers isolated issue and rolled back changes. 16:09 CET - Services responded as Healthy 16:10 CET - Traffic comes back as normal

Read the full incident report →