SashiDo Outage History
SashiDo is up right nowPingoru has recorded 51 incidents for SashiDo: 17 in the last 12 months and 1 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 2 | 18 of 720 (2%) |
| May 2026 | 2 | 4 of 744 (1%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 0 | 0 of 744 (0%) |
| September 2026 | 1 | 56 of 720 (8%) |
| October 2026 | 0 | 280 of 523 (54%) |
Incidents, newest first
Notice September 28, 2026 Parse Server Transactional Email Delivery Disruption 16d 22h Europe
Started Sep 28, 2026, 03:55 PM UTC· resolved Oct 15, 2026, 02:30 PM UTC
- investigating Sep 28, 2026, 03:55 PM UTC
We are currently experiencing an issue affecting outbound transactional emails of the Parse Servers in the EU Region. Our email delivery provider, Amazon SES, has temporarily paused sending from one of our production regions while they review unusual sending activity. As a result, some emails such as account notifications, verification emails, password resets, and other transactional messages may be delayed or not delivered. Our systems remain operational, and there is currently no indication that customer data has been affected. We are actively investigating the issue with AWS and reviewing our email infrastructure. Restoring normal email delivery is our highest priority. We will provide another update as soon as we have more information.
- investigating Oct 04, 2026, 08:32 AM UTC
We continue to actively work on resolving the transactional email delivery disruption affecting Parse Servers in the EU Region. Together with Amazon AWS, we are investigating the source of the unusual sending activity that caused Amazon SES to temporarily pause email delivery from the affected production region. Our current focus is not only on restoring normal service, but also on identifying the root cause and ensuring the issue cannot recur. The investigation is taking longer than we initially expected, and we understand that transactional email delivery, including account verification, password resets, notifications, and other application emails, may be critical to some of our customers' businesses. If this incident is having a significant impact on your production application or business operations, please contact our Customer Success Team at [email protected] We will work with you directly to evaluate and, where possible, provide an alternative email delivery solution while the investigation with AWS continues. Our Parse Server infrastructure and applications remain operational, and we currently have no indication that customer data has been affected. We apologise for the extended disruption and appreciate your patience while we work with AWS to fully resolve the issue. We will provide another update as soon as we have meaningful progress to share.
- identified Oct 04, 2026, 12:43 PM UTC
We have identified the source of the unusual sending activity that caused Amazon SES to pause outbound email delivery from the affected production region. Our team has already started implementing the required fixes and security improvements. Once these changes are completed, we will validate the affected systems to ensure the issue has been fully addressed and that normal sending can safely resume. Following this validation, we will coordinate with Amazon AWS to complete their review and restore outbound transactional email delivery. The investigation and remediation process has taken longer than we originally expected, and we understand that transactional emails — including account verification, password resets, notifications, and other application emails, may be critical to some customers' businesses. If this incident is significantly affecting your production application or business operations, please contact our Support team. We will work with you directly to evaluate and, where possible, provide an alternative email delivery solution while the final remediation and AWS review are being completed. Our Parse Server infrastructure and applications remain operational, and we currently have no indication that customer data has been affected. We appreciate your patience and will provide another update as soon as the remediation and validation process progresses further.
- monitoring Oct 05, 2026, 07:15 AM UTC
Аmazon AWS has restored sending access for the affected SES account, and transactional email delivery is now operational again. We have verified that emails are being sent successfully and will continue to closely monitor the infrastructure and sending activity to ensure the service remains stable. At this point, we consider the immediate service disruption resolved, while monitoring will continue as an additional precaution. Thank you for your patience and understanding throughout this incident.
- monitoring Oct 06, 2026, 08:47 AM UTC
Transactional email delivery remains operational, and we continue to closely monitor the infrastructure following the recent remediation work. As part of the additional security measures we have introduced, we are currently seeing a small number of false positives affecting some legitimate customer application activity. We are reviewing these cases continuously and deploying adjustments as quickly as possible to minimize any impact and ensure customer applications continue operating normally. We would like to thank all customers who have reported unexpected behavior, your reports are extremely helpful in allowing us to identify and address these cases quickly. We also appreciate your patience and understanding while we continue strengthening the protection of our infrastructure. In some situations, our safeguards may temporarily be more restrictive than necessary, but our priority is to protect the platform and, ultimately, the applications and businesses of our customers running on it. We will continue monitoring the situation closely and making adjustments where necessary.
- resolved Oct 15, 2026, 02:30 PM UTC
This incident has been resolved.
Minor May 22, 2026 [EU/APPS] - Elevated applications errors 2h 14m Europe
Started May 22, 2026, 09:11 AM UTC· resolved May 22, 2026, 11:25 AM UTC
- investigating May 22, 2026, 09:11 AM UTC
We're experiencing an increased rate of unhealthy applications. Currently we are looking into the issue.
- 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
- monitoring May 22, 2026, 10:53 AM UTC
A fix has been implemented and we are monitoring the results.
- 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.
Minor May 12, 2026 [NA/APPS] - Increased rate of unhealthy applications 1h 40m
Started May 12, 2026, 01:18 PM UTC· resolved May 12, 2026, 02:59 PM UTC
- investigating May 12, 2026, 01:18 PM UTC
We're experiencing an increased rate of applications health errors currently looking into the issue.
- 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.
- 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.
Minor April 23, 2026 [NA/APPS] - Increased rate of applications health errors 1h 31m
Started Apr 23, 2026, 04:47 PM UTC· resolved Apr 23, 2026, 06:18 PM UTC
- investigating Apr 23, 2026, 04:47 PM UTC
Our team is currently investigating the root cause of the issue.
- identified Apr 23, 2026, 04:55 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Apr 23, 2026, 05:48 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Apr 23, 2026, 06:18 PM UTC
Issue is resolved and for more than 1 hour there are no reports for unhealthy applications.
Notice March 25, 2026 [Builds and Deployments] - Dashboard Synchronization Issues 4d 22h Dashboard, Builds and Deployments
Started Mar 25, 2026, 12:54 PM UTC· resolved Mar 30, 2026, 11:49 AM UTC
- 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.
- monitoring Mar 25, 2026, 11:16 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Mar 30, 2026, 11:49 AM UTC
This incident has been resolved.
Minor March 2, 2026 [NA/APPS] - Elevated applications errors 1h 34m
Started Mar 02, 2026, 04:16 PM UTC· resolved Mar 02, 2026, 05:50 PM UTC
- investigating Mar 02, 2026, 04:16 PM UTC
We're experiencing an increased rate of applications health errors currently looking into the issue.
- 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.
- 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.
Minor March 10, 2025 [EU/APPS] - Increased rate of unhealthy applications 1h 40m
Started Mar 10, 2025, 04:25 PM UTC· resolved Mar 10, 2025, 06:05 PM UTC
- investigating Mar 10, 2025, 04:25 PM UTC
We're experiencing an increased rate of applications health errors currently looking into the issue.
- monitoring Mar 10, 2025, 05:35 PM UTC
A fix has been implemented and we are monitoring the results.
- 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.
Minor January 13, 2025 [EU/APPS] - Increased rate of applications health errors 4h 56m
Started Jan 13, 2025, 03:55 PM UTC· resolved Jan 13, 2025, 08:51 PM UTC
- investigating Jan 13, 2025, 03:55 PM UTC
We're experiencing an increased rate of unhealthy applications. Currently we are looking into the issue.
- monitoring Jan 13, 2025, 05:39 PM UTC
A fix has been implemented and we are monitoring the results.
- 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.
- 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.
Major December 8, 2024 [Global] - Builds stucking 13h 4m Builds and Deployments
Started Dec 08, 2024, 10:01 AM UTC· resolved Dec 08, 2024, 11:05 PM UTC
- investigating Dec 08, 2024, 10:01 AM UTC
We are currently investigating this issue.
- 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.
- monitoring Dec 08, 2024, 04:33 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Dec 08, 2024, 11:05 PM UTC
This incident has been resolved.