SashiDo Outage History

SashiDo is up right now

SashiDo had 9 outages in the last 2 years totaling 146h 35m of downtime — averaging 0.4 incidents per month.

There were 9 SashiDo outages since June 21, 2024 totaling 146h 35m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.sashido.io

Minor May 22, 2026

[EU/APPS] - Elevated applications errors

Detected by Pingoru
May 22, 2026, 09:11 AM UTC
Resolved
May 22, 2026, 11:25 AM UTC
Duration
2h 14m
Affected: Europe
Timeline · 4 updates
  1. investigating May 22, 2026, 09:11 AM UTC

    We're experiencing an increased rate of unhealthy applications. Currently we are looking into the issue.

  2. identified May 22, 2026, 10:01 AM UTC

    We are currently experiencing connectivity issues affecting part of our infrastructure hosted in the FR-PAR datacenter region. Our datacenter provider, Scaleway, has confirmed an ongoing network incident in the same region. According to their latest update, the issue is related to a power problem inside the datacenter, and most services have already recovered while their teams continue working on the remaining affected systems. Some users may experience intermittent connectivity issues, increased latency, or temporary service interruptions. Our team is actively monitoring the situation and will continue to follow Scaleway’s recovery progress closely. We will provide another update as soon as we have more information or once the situation is fully stabilized. Provider incident: https://status.scaleway.com/incidents/qkj49g6g3ykp

  3. monitoring May 22, 2026, 10:53 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved May 22, 2026, 11:25 AM UTC

    Good news! Things should be back to normal again across the board. Please let us know if there is any further trouble. Thank you so much for your patience while we worked to sort this out.

Read the full incident report →

Minor May 12, 2026

[NA/APPS] - Increased rate of unhealthy applications

Detected by Pingoru
May 12, 2026, 01:18 PM UTC
Resolved
May 12, 2026, 02:59 PM UTC
Duration
1h 40m
Timeline · 3 updates
  1. investigating May 12, 2026, 01:18 PM UTC

    We're experiencing an increased rate of applications health errors currently looking into the issue.

  2. monitoring May 12, 2026, 02:29 PM UTC

    Our monitoring system report all of the failing applications are healthy. We we will continue monitoring proactively.

  3. resolved May 12, 2026, 02:59 PM UTC

    The incident is resolved. Apologies for this connection blip. Thank you as always for sticking with us, we really appreciate it.

Read the full incident report →

Minor April 23, 2026

[NA/APPS] - Increased rate of applications health errors

Detected by Pingoru
Apr 23, 2026, 04:47 PM UTC
Resolved
Apr 23, 2026, 06:18 PM UTC
Duration
1h 31m
Timeline · 4 updates
  1. investigating Apr 23, 2026, 04:47 PM UTC

    Our team is currently investigating the root cause of the issue.

  2. identified Apr 23, 2026, 04:55 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Apr 23, 2026, 05:48 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Apr 23, 2026, 06:18 PM UTC

    Issue is resolved and for more than 1 hour there are no reports for unhealthy applications.

Read the full incident report →

Notice March 25, 2026

[Builds and Deployments] - Dashboard Synchronization Issues

Detected by Pingoru
Mar 25, 2026, 12:54 PM UTC
Resolved
Mar 30, 2026, 11:49 AM UTC
Duration
4d 22h
Affected: DashboardBuilds and Deployments
Timeline · 3 updates
  1. investigating Mar 25, 2026, 12:54 PM UTC

    We are currently experiencing an issue where builds and deployments are completing successfully at the infrastructure level, but are not being correctly reflected in the Dashboard for some applications. This appears to be a synchronization issue affecting the Dashboard visibility layer only. There is no impact on the actual build or deployment processes. Our team is actively investigating the root cause.

  2. monitoring Mar 25, 2026, 11:16 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Mar 30, 2026, 11:49 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 2, 2026

[NA/APPS] - Elevated applications errors

Detected by Pingoru
Mar 02, 2026, 04:16 PM UTC
Resolved
Mar 02, 2026, 05:50 PM UTC
Duration
1h 34m
Timeline · 3 updates
  1. investigating Mar 02, 2026, 04:16 PM UTC

    We're experiencing an increased rate of applications health errors currently looking into the issue.

  2. monitoring Mar 02, 2026, 05:20 PM UTC

    We have implemented a fix for this issue and are currently monitoring the results. We will update once we have confirmed it is resolved.

  3. resolved Mar 02, 2026, 05:50 PM UTC

    Good news! Things should be back to normal again across the board. Please let us know if there is any further trouble. Thank you so much for your patience while we worked to sort this out.

Read the full incident report →

Minor March 10, 2025

[EU/APPS] - Increased rate of unhealthy applications

Detected by Pingoru
Mar 10, 2025, 04:25 PM UTC
Resolved
Mar 10, 2025, 06:05 PM UTC
Duration
1h 40m
Timeline · 3 updates
  1. investigating Mar 10, 2025, 04:25 PM UTC

    We're experiencing an increased rate of applications health errors currently looking into the issue.

  2. monitoring Mar 10, 2025, 05:35 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Mar 10, 2025, 06:05 PM UTC

    We have some good news to share! Everything is now looking clear from our side and all users should be able to work with their applications without any interruptions. Please let us know at [email protected] if you are still experiencing problems. We apologize for disrupting your day and thank you for your patience.

Read the full incident report →

Minor January 13, 2025

[EU/APPS] - Increased rate of applications health errors

Detected by Pingoru
Jan 13, 2025, 03:55 PM UTC
Resolved
Jan 13, 2025, 08:51 PM UTC
Duration
4h 56m
Timeline · 4 updates
  1. investigating Jan 13, 2025, 03:55 PM UTC

    We're experiencing an increased rate of unhealthy applications. Currently we are looking into the issue.

  2. monitoring Jan 13, 2025, 05:39 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. monitoring Jan 13, 2025, 08:19 PM UTC

    We have implemented a fix for this issue and are currently monitoring the results. We will update once we have confirmed it is resolved.

  4. resolved Jan 13, 2025, 08:51 PM UTC

    Good news! Things should be back to normal again across the board. Please let us know if there is any further trouble. Thank you so much for your patience while we worked to sort this out.

Read the full incident report →

Major December 8, 2024

[Global] - Builds stucking

Detected by Pingoru
Dec 08, 2024, 10:01 AM UTC
Resolved
Dec 08, 2024, 11:05 PM UTC
Duration
13h 4m
Affected: Builds and Deployments
Timeline · 4 updates
  1. investigating Dec 08, 2024, 10:01 AM UTC

    We are currently investigating this issue.

  2. identified Dec 08, 2024, 10:48 AM UTC

    We’ve identified the issue and are performing Docker changes and required restarts. Short application outages may occur during this process. We’re working to resolve this as quickly as possible. Thank you for your patience.

  3. monitoring Dec 08, 2024, 04:33 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Dec 08, 2024, 11:05 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 21, 2024

[EU] - Deployments failing

Detected by Pingoru
Jun 21, 2024, 12:37 PM UTC
Resolved
Jun 21, 2024, 01:37 PM UTC
Duration
59m
Affected: EuropeDashboardEuropeBuilds and Deployments
Timeline · 4 updates
  1. investigating Jun 21, 2024, 12:37 PM UTC

    We are currently investigating this issue.

  2. identified Jun 21, 2024, 01:14 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Jun 21, 2024, 01:26 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Jun 21, 2024, 01:37 PM UTC

    This incident has been resolved.

Read the full incident report →