Notice history

Jan 2025

Feb 2025

Mar 2025

Jan 2025

Feb 2025

Mar 2025

Jan 2025

Feb 2025

Mar 2025

Jan 2025

Feb 2025

Mar 2025

Update
March 10, 2025 at 1:40 AM
Update
March 10, 2025 at 1:40 AM
We are observing that higher quality transcriptions appear to be slow with this temporary solution. We are aware of the problem and are working on a more permanent fix.
Monitoring
March 10, 2025 at 1:23 AM
Monitoring
March 10, 2025 at 1:23 AM
We have deployed a temporary fix. This fix should resolve most transcription issues, although transcription will only be available in English at this time. We are working to find a more permanent fix to allow for previous multi-lingual transcription function.
Identified
March 06, 2025 at 4:36 AM
Identified
March 06, 2025 at 4:36 AM
We are currently observing a degradation in transcription quality most prominently effecting the Accuracy mode and are working on a fix. We recommend switching to the Balanced mode for the time being. Thank you for your patience during this time.

Resolved
February 24, 2025 at 2:42 AM
Resolved
February 24, 2025 at 2:42 AM
We believe that this issue has been resolved by our hosting provider. Thank you for your patience.
Update
February 22, 2025 at 7:27 AM
Update
February 22, 2025 at 7:27 AM
Our hosting provider has let us know that they are in contact with their internal providers to work on resolving the issue. We thank you for your patience during this time.
Identified
February 22, 2025 at 6:21 AM
Identified
February 22, 2025 at 6:21 AM
We are currently observing periods of increased latency which are causing errors on our backend. We believe this to be an issue with our hosting provider and have reached out to figure out what is going on. You may notice brief periods of unresponsiveness of lag during this time. We are investigating the issue.

Resolved
February 22, 2025 at 3:27 AM
Resolved
February 22, 2025 at 3:27 AM
Scriptly is back online in all communities and this issue has been resolved. Thank you for your patience.
Monitoring
February 22, 2025 at 3:16 AM
Monitoring
February 22, 2025 at 3:16 AM
We implemented a fix and are currently monitoring the result.
Investigating
February 22, 2025 at 3:05 AM
Investigating
February 22, 2025 at 3:05 AM
We are currently investigating this incident.

Completed
February 02, 2025 at 2:12 AM
Completed
February 02, 2025 at 2:12 AM
Scriptly is back online in all communities. Thank you for your patience. :)
In progress
February 02, 2025 at 2:04 AM
In progress
February 02, 2025 at 2:04 AM
Scriptly is undergoing a quick full-restart in order to deploy some updates. Thank you for your patience during this time.

Completed
January 06, 2025 at 5:03 AM
Completed
January 06, 2025 at 5:03 AM
Maintenance has completed successfully.
In progress
January 06, 2025 at 4:50 AM
In progress
January 06, 2025 at 4:50 AM
Maintenance is now in progress.
Planned
January 06, 2025 at 4:45 AM
Planned
January 06, 2025 at 4:45 AM
We are planning for a scheduled maintenance during that time. We will be upgrading Scriptly's backend systems in order to account for increased usage and improve performance. We are hopeful this will decrease the frequency of automatic restarts that disrupt service.

Resolved
January 03, 2025 at 4:30 PM
Resolved
January 03, 2025 at 4:30 PM
This incident has been resolved.
Identified
January 03, 2025 at 8:58 AM
Identified
January 03, 2025 at 8:58 AM
We have been made aware that a small subset of TTS voices are currently non-functional. We have identified the source of the problem, and are waiting on a third-party provider to resolve the issue. We recommend using other available text-to-speech voices at this time. Thank you for your patience.

Jan 2025 to Mar 2025

Scriptly - Notice history