Scriptly Outage History

Scriptly is up right now

Pingoru has recorded 4 incidents for Scriptly: 4 in the last 12 months and 4 in the last 90 days.

Source: scriptly.instatus.com

4incidents recorded
4last 12 months
4last 90 days
3 hourstypical duration

Incidents, newest first

Minor October 25, 2026 Premium TTS Voice Availability 11h Text-to-speech

Started Oct 25, 2026, 01:59 AM UTC· resolved Oct 25, 2026, 01:00 PM UTC

  1. investigating Oct 25, 2026, 01:59 AM UTC

    We are currently investigating this incident.

  2. monitoring Oct 25, 2026, 12:46 PM UTC

    A fix is rolling out and should be deployed within \~15 minutes from now. Thank you for your patience.

  3. resolved Oct 25, 2026, 01:00 PM UTC

    This incident has been resolved.

Read the full incident report →

Major October 17, 2026 Widespread Outage 21m Scriptly Discord Bot (Cluster 0), Scriptly Discord Bot (Cluster 1), Scriptly Discord Bot (Cluster 2), Scriptly Discord Bot (Cluster 3) and 8 more

Started Oct 17, 2026, 10:21 PM UTC· resolved Oct 17, 2026, 10:42 PM UTC

  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 →

Major October 17, 2026 Some servers are unable to use Scriptly 22m Scriptly Discord Bot (Cluster 5), Scriptly Discord Bot (Cluster 9)

Started Oct 17, 2026, 05:15 AM UTC· resolved Oct 17, 2026, 05:37 AM UTC

  1. investigating Oct 17, 2026, 05:15 AM UTC

    3 of 12 clusters are currently down, so Scriptly may be unresponsive in some servers. Other servers are unaffected. We are investigating and affected clusters restart automatically.

  2. investigating Oct 17, 2026, 05:15 AM UTC

    Cluster 1, Cluster 2, Cluster 4, Cluster 5, Cluster 7, Cluster 8, Cluster 9 and Cluster 10 are also affected. 11 of 12 clusters are currently down, so Scriptly may be unresponsive in some servers. Other servers are unaffected. We are investigating and affected clusters restart automatically.

  3. investigating Oct 17, 2026, 05:21 AM UTC

    Cluster 4 has recovered. 10 of 12 clusters are currently down, so Scriptly may be unresponsive in some servers. Other servers are unaffected. We are investigating and affected clusters restart automatically.

  4. investigating Oct 17, 2026, 05:22 AM UTC

    Cluster 7 has recovered. 9 of 12 clusters are currently down, so Scriptly may be unresponsive in some servers. Other servers are unaffected. We are investigating and affected clusters restart automatically.

  5. investigating Oct 17, 2026, 05:27 AM UTC

    Cluster 4 and Cluster 7 are also affected. 11 of 12 clusters are currently down, so Scriptly may be unresponsive in some servers. Other servers are unaffected. We are investigating and affected clusters restart automatically.

  6. investigating Oct 17, 2026, 05:32 AM UTC

    Cluster 8 has recovered. 10 of 12 clusters are currently down, so Scriptly may be unresponsive in some servers. Other servers are unaffected. We are investigating and affected clusters restart automatically.

  7. investigating Oct 17, 2026, 05:33 AM UTC

    Cluster 7 has recovered. 9 of 12 clusters are currently down, so Scriptly may be unresponsive in some servers. Other servers are unaffected. We are investigating and affected clusters restart automatically.

  8. investigating Oct 17, 2026, 05:34 AM UTC

    Cluster 6 has recovered. 8 of 12 clusters are currently down, so Scriptly may be unresponsive in some servers. Other servers are unaffected. We are investigating and affected clusters restart automatically.

  9. investigating Oct 17, 2026, 05:34 AM UTC

    Cluster 4 has recovered. 7 of 12 clusters are currently down, so Scriptly may be unresponsive in some servers. Other servers are unaffected. We are investigating and affected clusters restart automatically.

  10. investigating Oct 17, 2026, 05:35 AM UTC

    Cluster 2 has recovered. 6 of 12 clusters are currently down, so Scriptly may be unresponsive in some servers. Other servers are unaffected. We are investigating and affected clusters restart automatically.

  11. investigating Oct 17, 2026, 05:35 AM UTC

    Cluster 10 has recovered. 5 of 12 clusters are currently down, so Scriptly may be unresponsive in some servers. Other servers are unaffected. We are investigating and affected clusters restart automatically.

  12. investigating Oct 17, 2026, 05:36 AM UTC

    Cluster 0 and Cluster 3 have recovered. 3 of 12 clusters are currently down, so Scriptly may be unresponsive in some servers. Other servers are unaffected. We are investigating and affected clusters restart automatically.

  13. investigating Oct 17, 2026, 05:36 AM UTC

    Cluster 1 has recovered. 2 of 12 clusters are currently down, so Scriptly may be unresponsive in some servers. Other servers are unaffected. We are investigating and affected clusters restart automatically.

  14. investigating Oct 17, 2026, 05:36 AM UTC

    Cluster 1 has recovered. 2 of 12 clusters are currently down, so Scriptly may be unresponsive in some servers. Other servers are unaffected. We are investigating and affected clusters restart automatically.

  15. resolved Oct 17, 2026, 05:37 AM UTC

    All clusters have been restored and Scriptly is fully operational again.

Read the full incident report →

Minor October 16, 2026 Premium TTS Voices 12m Text-to-speech

Started Oct 16, 2026, 12:13 AM UTC· resolved Oct 16, 2026, 12:26 AM UTC

  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 →