Skeddly Outage History
Skeddly is up right nowPingoru has recorded 4 incidents for Skeddly: 2 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 | 0 | 0 of 720 (0%) |
| May 2026 | 0 | 0 of 744 (0%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 0 | 0 of 744 (0%) |
| September 2026 | 1 | 0 of 720 (0%) |
| October 2026 | 0 | 0 of 534 (0%) |
Incidents, newest first
Notice September 1, 2026 System Outage – Action Infrastructure, Notification Infrastructure
Started Sep 01, 2026, 09:05 PM UTC· resolved Sep 01, 2026, 09:05 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 –
Started Oct 20, 2025, 06:50 AM UTC· resolved Oct 20, 2025, 06:50 AM UTC
- resolved Oct 20, 2025, 11:25 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