Skeddly Outage History

Pingoru has recorded 50 incidents for Skeddly: 2 in the last 12 months and 1 in the last 90 days.

50incidents recorded

2last 12 months

1last 90 days

21 minutestypical duration

Incidents per month

Share of hours with an open incident, any severity

Pingoru began tracking Skeddly in April 2026, so earlier months are not shown. Hover a bar for its value.

Show as a table

Incidents, newest first

Notice September 1, 2026 System Outage 31m Action Infrastructure, Notification Infrastructure

Started Sep 01, 2026, 08:15 PM UTC· resolved Sep 01, 2026, 08:46 PM UTC

resolved Sep 01, 2026, 09:05 PM UTC

From 4:15pm EST to 4:46pm EST, we encountered a system outage which affected our back-end systems. This included notifications, action starts, and action executions. The cause of the outage was a bad deployment. The offending cause was reversed and the system recovered. All affected actions will be covered by our SLA.

Critical January 19, 2026 Actions not processing 11m Action Infrastructure

Started Jan 19, 2026, 09:03 PM UTC· resolved Jan 19, 2026, 09:14 PM UTC

identified Jan 19, 2026, 09:03 PM UTC

During a deployment, our service queues failed to deploy properly. We've nuked and they are now being re-created by Auto Scaling.
monitoring Jan 19, 2026, 09:07 PM UTC

The new service queues have come online and have starting distributing the work. Service modules are catching up. We are monitoring the situation.
resolved Jan 19, 2026, 09:14 PM UTC

Actions are processing correctly again. All affected actions will be covered under our SLA.

Critical October 20, 2025 Emails & Notifications Impacted 7h 27m Notification Infrastructure

Started Oct 20, 2025, 01:35 PM UTC· resolved Oct 20, 2025, 09:03 PM UTC

identified Oct 20, 2025, 01:35 PM UTC

Due to the ongoing AWS outage, emails and other notifications are impacted.
identified Oct 20, 2025, 04:51 PM UTC

In an effort to resolve their own issues, AWS has rate limited customers. This rate limit is preventing us from launching a fresh Notifier service. So we continue to wait.
monitoring Oct 20, 2025, 07:43 PM UTC

AWS has allowed us to launch our Notification service. So that's happened now and notifications are flowing again. We are monitoring the situation for issues.
resolved Oct 20, 2025, 09:03 PM UTC

Notifications appear to be flowing nicely now.

Major October 20, 2025 AWS Outage 1h 30m

Started Oct 20, 2025, 06:50 AM UTC· resolved Oct 20, 2025, 08:20 AM UTC

resolved Oct 20, 2025, 06:50 AM UTC

Between 06:50 UTC and 09:30 UTC, AWS experienced an outage in their us-east-1 (N. Virginia) region. This outage affects Skeddly's ability to start action executions. Already-running action executions were able to continue running. At 08:20 UTC, we were able to put measures in place to circumvent the issue Skeddly's starters were experiencing. This allowed us to start new action executions. All action executions that were delayed have already been covered by Skeddly's SLA (https://www.skeddly.com/sla/) Please note that while actions were able to execute during the AWS outage, if they interacted with the us-east-1 region during the AWS outage, they likely experienced errors and failures. Some downstream providers were also affected by the AWS outage. This affected functionality like email notifications, daily summeries, etc., which may have been delayed and/or never sent. To top it off, the service provider for our status page was also affected by the AWS outage, so we were not able to update our status page during the event. More information about the AWS outage can be found on their health dashboard: https://status.aws.amazon.com/#multipleservices-us-east-1_1760956537

Critical September 8, 2025 Web Application Issues 1h 44m Web Interface, API, SNS Endpoints

Started Sep 08, 2025, 10:45 PM UTC· resolved Sep 09, 2025, 12:29 AM UTC

investigating Sep 08, 2025, 10:45 PM UTC

We are currently investigating an issue where Skeddly's web application is not responding.
monitoring Sep 08, 2025, 11:08 PM UTC

A fix has been implemented and we are monitoring the results.
resolved Sep 09, 2025, 12:29 AM UTC

This incident has been resolved.

Notice January 16, 2025 Actions Not Starting 26m

Started Jan 16, 2025, 07:04 PM UTC· resolved Jan 16, 2025, 07:30 PM UTC

resolved Jan 16, 2025, 08:00 PM UTC

Between 7:04pm and 7:30pm UTC, actions did not start on schedule. This was caused by an issue during deployment. The issue has been resolved. All affected actions executed around 7:30pm UTC. All affected actions will be subject to our Service Level Agreement.