Scriptly Outage History

Scriptly is up right now

Scriptly had 3 outages in the last 2 years totaling 56m of downtime, averaging 0.1 incidents per month.

There were 3 Scriptly outages since October 16, 2026 totaling 56m of downtime. Each is summarised below. Incident details, duration, and resolution information.

Source: scriptly.instatus.com

Major October 17, 2026

Widespread Outage

Detected by Pingoru
Oct 17, 2026, 10:21 PM UTC
Resolved
Oct 17, 2026, 10:42 PM UTC
Duration
21m
Affected: Scriptly Discord Bot (Cluster 0)Scriptly Discord Bot (Cluster 1)Scriptly Discord Bot (Cluster 2)Scriptly Discord Bot (Cluster 3)Scriptly Discord Bot (Cluster 4)Scriptly Discord Bot (Cluster 5)Scriptly Discord Bot (Cluster 6)Scriptly Discord Bot (Cluster 7)Scriptly Discord Bot (Cluster 8)Scriptly Discord Bot (Cluster 9)Scriptly Discord Bot (Cluster 10)Scriptly Discord Bot (Cluster 11)
Timeline · 3 updates
  1. investigating Oct 17, 2026, 10:21 PM UTC

    We are currently investigating this incident.

  2. monitoring Oct 17, 2026, 10:26 PM UTC

    We have identified the issue as being caused by our hosting provider. The bot is starting back up and should be back online for everyone in roughly 15 minutes. Thank you for your patience.

  3. resolved Oct 17, 2026, 10:42 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 16, 2026

Premium TTS Voices

Detected by Pingoru
Oct 16, 2026, 12:13 AM UTC
Resolved
Oct 16, 2026, 12:26 AM UTC
Duration
12m
Affected: Text-to-speech
Timeline · 3 updates
  1. investigating Oct 16, 2026, 12:13 AM UTC

    We have received reports and are observing that some premium TTS voices appear to be unavailable. We are investigating the problem. Thank you for your patience.

  2. identified Oct 16, 2026, 12:19 AM UTC

    We are continuing to work on a fix for this incident.

  3. resolved Oct 16, 2026, 12:26 AM UTC

    A fix has been deployed and is rolling out to all communities. We expect this to be rolled out to everyone in roughly 15 minutes. Thank you for your patience.

Read the full incident report →