Scriptly - Notice history

All systems operational

100% - uptime

Cluster 0 - Operational

100% - uptime
Jan 2025 · 100.0%Feb · 100.0%Mar · 100.0%

Previous page

Next page

Jan 2025
Feb 2025
Mar 2025

Cluster 1 - Operational

100% - uptime
Jan 2025 · 100.0%Feb · 100.0%Mar · 100.0%

Previous page

Next page

Jan 2025
Feb 2025
Mar 2025

Cluster 2 - Operational

100% - uptime
Jan 2025 · 100.0%Feb · 100.0%Mar · 100.0%

Previous page

Next page

Jan 2025
Feb 2025
Mar 2025

Cluster 3 - Operational

100% - uptime
Jan 2025 · 100.0%Feb · 100.0%Mar · 100.0%

Previous page

Next page

Jan 2025
Feb 2025
Mar 2025

Cluster 4 - Operational

100% - uptime
Jan 2025 · 100.0%Feb · 100.0%Mar · 100.0%

Previous page

Next page

Jan 2025
Feb 2025
Mar 2025

Cluster 5 - Operational

100% - uptime
Jan 2025 · 100.0%Feb · 100.0%Mar · 100.0%

Previous page

Next page

Jan 2025
Feb 2025
Mar 2025

Cluster 6 - Operational

100% - uptime
Jan 2025 · 100.0%Feb · 100.0%Mar · 100.0%

Previous page

Next page

Jan 2025
Feb 2025
Mar 2025

Cluster 7 - Operational

100% - uptime
Jan 2025 · 100.0%Feb · 100.0%Mar · 100.0%

Previous page

Next page

Jan 2025
Feb 2025
Mar 2025

Transcription - Operational

100% - uptime
Jan 2025 · 100.0%Feb · 100.0%Mar · 100.0%

Previous page

Next page

Jan 2025
Feb 2025
Mar 2025

Text-to-speech - Operational

100% - uptime
Jan 2025 · 100.0%Feb · 100.0%Mar · 100.0%

Previous page

Next page

Jan 2025
Feb 2025
Mar 2025

Scriptly's Website - Operational

100% - uptime
Jan 2025 · 100.0%Feb · 100.0%Mar · 100.0%

Previous page

Next page

Jan 2025
Feb 2025
Mar 2025

Notice history

Mar 2025

Scriptly Offline
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    Monitoring

    We have identified the source of the issue. It appears that Scriptly was made offline due to an interruption in service from our hosting provider. Unfortunately, it appears that Scriptly did not autorecover when the issue was fixed, leading to extended downtime. Scriptly is coming back online as we speak. Thanks again for your patience.

  • Identified
    Identified
    We are continuing to work on a fix for this incident.
  • Investigating
    Investigating
    We are currently investigating this incident.
Transcription Degradation
  • Resolved
    Resolved
    This incident has been resolved.
  • Investigating
    Investigating

    We have been made aware of other problems affecting Scriptly's voice channel transcription capabilities. We are aware of the problems and are investigating the issue.

  • Update
    Update

    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
    Monitoring

    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
    Identified

    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.

Feb 2025

Scriptly Increased Latency/Errors
  • Resolved
    Resolved

    We believe that this issue has been resolved by our hosting provider. Thank you for your patience.

  • Update
    Update

    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
    Identified

    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.

Scriptly Degraded Performance
  • Resolved
    Resolved

    Scriptly is back online in all communities and this issue has been resolved. Thank you for your patience.

  • Monitoring
    Monitoring
    We implemented a fix and are currently monitoring the result.
  • Investigating
    Investigating

    We are currently investigating this incident.

Deploying Updates
  • 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.

Jan 2025

Scriptly System Upgrades
  • 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.

Small Subset of TTS Voices Non-Functional
  • Resolved
    Resolved
    This incident has been resolved.
  • Identified
    Identified

    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

Next