Is SashiDo down?

Last checked 2m ago
Current status
SashiDo is up

No incidents right now.

  • Official status page: status.sashido.io
  • Checked every 5 minutes
  • 53 components tracked

SashiDo is operational right now. Last checked 2m ago; the most recent incident resolved 7d ago.

Real-time SashiDo status, recent outages, and incident history: pulled directly from SashiDo's official status page at status.sashido.io every 5 minutes. Pingoru tracks 53 SashiDo services and has captured 2 incidents in the last 90 days (99.98% uptime). Get email, Slack, Discord, or webhook alerts the moment SashiDo reports a new incident, free for 3 monitors, no credit card.

Users who monitor SashiDo also follow these Development services: Bitbucket OpenAI Datadog US1 Sentry NPM Travis CI Postman Pusher Pendo Rollbar View all 8,000+ providers
SashiDo uptime 99.98% uptime · past 90 days
Mon Wed Fri
AugSepOct
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 3h 32m
    Started Oct 24, 2026, 02:08 PM UTC · Resolved Oct 24, 2026, 05:40 PM UTC
    Timeline · 3 updates
    • investigating · Oct 24, 2026, 02:08 PM UTC

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

    • monitoring · Oct 24, 2026, 05:10 PM UTC

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

    • resolved · Oct 24, 2026, 05:40 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.

    Latest: 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 t…

  2. Resolved 16d 22h
    Started Sep 28, 2026, 03:55 PM UTC · Resolved Oct 15, 2026, 02:30 PM UTC
    Europe
    Timeline · 6 updates
    • 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.

    Latest: This incident has been resolved.

Incident record

Since April 2026 · Statuspage by Atlassian · 53 components checked every 5 minutes
52incidents recorded
16last 12 months
2last 90 days
2 daystypical duration, 12 months

The longest incident in the last year, Parse Server Transactional Email Delivery Disruption on September 28, 2026, ran for 17 days. 2 maintenance windows announced in the same period.

Most affected components, last 12 months

  • Europe3
  • API1
  • Automated Database Backups Service1
  • Builds and Deployments1
  • Dashboard1

Latest incidents

Outage history

Past 90 days · 2 incidents View full outage history →