Skeddly had 4 outages in the last 2 years totaling 7h 39m of downtime — averaging 0.2 incidents per month.
There were 4 Skeddly outages since October 20, 2025 totaling 7h 39m of downtime. Each is summarised below — incident details, duration, and resolution information.
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.
During a deployment, our service queues failed to deploy properly. We've nuked and they are now being re-created by Auto Scaling.
The new service queues have come online and have starting distributing the work. Service modules are catching up. We are monitoring the situation.
Actions are processing correctly again. All affected actions will be covered under our SLA.
Due to the ongoing AWS outage, emails and other notifications are impacted.
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.
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.
Notifications appear to be flowing nicely now.