Is Descript down?
Check Descript availability, incident history, downtime reports, and website performance.
https://www.descript.com/ ↗Mapped components are operational in the latest status update; individual experiences can vary.
Service disruption activity for Descript
Last 24 hoursObserved disruption signals combine available incidents, recorded reports, website checks, and emerging problem patterns. A low score does not guarantee that every feature is working.
Latest observation: 2026-11-11 04:04:50 UTC. Refreshes automatically while this page is visible.
No user-submitted outage reports in the last 24 hours.
Descript outage history
2025–2026Daily history over the past 12 months. Select a day for its evidence.
Select a square for daily details. Scroll sideways to explore earlier months.
How to read this calendar
Dates use New York time (America/New_York). Green means no issues observed with sufficient monitoring coverage; it does not guarantee uninterrupted uptime. Pink includes official incidents, repeated website failures, or corroborated user reports. Gray days are unknown. Activity estimates alone do not turn a day pink. Today’s result can change.
Descript website uptime and response time
Website responded successfully HTTP 200. Last checked 2026-11-11 04:04:50 UTC.
Checked address: https://www.descript.com/
DNS lookup: 31 ms · TCP connection: 5 ms · TLS handshake: 7 ms. Certificate expires 2026-12-30; trusted connection: yes.
100%
Successful website checks (24h)
186 successful / 186 measurable checks
302 ms
Median response time
759 ms
95th percentile response time
0 failed checks; 0 restricted checks. Restricted checks are excluded from the success rate. Lines connect recorded samples across gaps; availability between checks is unknown. Response time measures receipt of HTTP headers, not full page load. Checks run from one US monitoring server and do not verify sign-in, API, or app features. These sampled results are separate from down reports and estimated activity.
Evidence behind the status
Provider reports operational. Mapped components are operational in the latest status update; individual experiences can vary.
Website checks and estimated activity have independent update times. Refer to each section for its latest observation.
These measurements describe different things. A reachable homepage can coexist with login or API failures. Missing evidence stays unknown.
Official component status
Descript official status · fetched 2026-11-11 03:56:43 UTC
25 mapped components · 0 reporting problems
| Component | Provider status |
|---|---|
| Desktop App | operational |
| Web App | operational |
| Editing | operational |
| Live Collaboration/Project Sync | operational |
| Media Playback | operational |
| File upload/sync | operational |
| Transcription | operational |
| Generated speech | operational |
| Cleanup | operational |
| Studio sound | operational |
| Roomtone extraction | operational |
| Automatic multicam | operational |
| Avatars | operational |
| Center active speaker | operational |
| Eye contact | operational |
| Green screen | operational |
| Image generation | operational |
| Video Regenerate | operational |
| Layouts | operational |
| Create clips and reels | operational |
| Translate | operational |
| Suggestions | operational |
| Agent | operational |
| Rooms | operational |
| Recorder | operational |
Official incident timeline
Avatar Outage · resolved · 2026-11-03T00:04:28Z
Product match: unmapped.
Read the provider’s incident report
- · resolved
This issue is now resolved.
- · monitoring
Functionality is fully restored and we are monitoring to ensure the system continues to be operational.
- · identified
We have identified a downstream issue with models used for the Avatars feature, causing them to be unavailable. We'll provide an update as soon as functionality is restored.
Increased latency for agent API jobs · resolved · 2026-10-31T02:24:20Z
Product match: unmapped.
Read the provider’s incident report
- · resolved
This issue is now resolved.
- · monitoring
Functionality is restored and we are monitoring to ensure the system continues to be operational.
- · investigating
We are still investigating the root cause of this issue, and are working on a fix
- · monitoring
Functionality is fully restored and we are monitoring to ensure the system continues to be operational.
- · investigating
We’re seeing increased latency for jobs initiated via the agent API, and are currently investigating the underlying issue.
Generate Layout is down · resolved · 2026-10-26T13:50:08Z
Product match: unmapped.
Read the provider’s incident report
- · resolved
This issue is now resolved.
- · identified
We have identified the underlying issue and are working to restore functionality.
Transcription jobs failing · resolved · 2026-09-29T21:43:58Z
Product match: unmapped.
Read the provider’s incident report
- · resolved
This issue is now resolved.
- · monitoring
Functionality is fully restored and we are monitoring to ensure the system continues to be operational.
- · identified
We have identified the underlying issue and are working to restore functionality.
- · resolved
This issue is now resolved.
- · monitoring
Functionality is fully restored and we are monitoring to ensure the system continues to be operational.
- · investigating
We have detected a problem with our transcription pipeline, and we are currently investigating. Currently, transcription jobs may be stuck or failing.
Issues with Project Sync · resolved · 2026-09-15T18:18:02Z
Product match: unmapped.
Read the provider’s incident report
- · resolved
This issue is now resolved.
- · monitoring
Functionality is fully restored and we are monitoring to ensure the system continues to be operational.
- · identified
A recent change to our sync engine has made it possible for edits to be reverted, which can cause inadvertent loss of work(often visible as "merge error" messages in the Version History). We've identified the problem and have a fix we're actively working to test and deploy. We will follow up at 10 AM PT with an update on progress. For a workaround in the meantime, check for the lost edits in the Version History, specifically by clicking the **Fix** button for the version that has the error mess
- · identified
A recent change to our sync engine has made it possible for edits to be reverted, which can cause inadvertent loss of work(often visible as "merge error" messages in the Version History). We've identified the problem and have a fix we're actively working to test and deploy. We will follow up at 10 AM PT with an update on progress. For a workaround in the meantime, check for the lost edits in the Version History, specifically by clicking the **Fix** button for the version that has the error mess
Rooms Recording Outage · resolved · 2026-09-14T13:45:19Z
Product match: unmapped.
Read the provider’s incident report
- · resolved
This issue is now resolved.
- · monitoring
Functionality is fully restored and we are monitoring to ensure the system continues to be operational.
- · investigating
We have detected a problem and are investigating the underlying issue.
Underlord · resolved · 2026-09-11T15:22:51Z
Product match: unmapped.
Read the provider’s incident report
- · resolved
This issue is now resolved.
- · monitoring
Some users were receiving an “HTTP 500 Internal server error” when trying to use Underlord. Functionality is fully restored and we are monitoring to ensure the system continues to be operational. If the issue continues occurring, please change the Underlord model from Auto (App Settings > General), and retry the same prompt.
Backend Workflow Outage · resolved · 2026-09-10T23:54:49Z
Product match: unmapped.
Read the provider’s incident report
- · resolved
This issue is now resolved.
- · monitoring
Functionality is fully restored and we are monitoring to ensure the system continues to be operational.
- · investigating
We have detected a problem with some of our backend workflows like transcription and we are investigating the underlying issue.
Recovery tracker
No recent recovery can be established from available evidence.
6 consecutive successful checks within the last 30 minutes. These checks measure the public website; they cannot establish recovery of every feature.
Slowdown detection
No sustained slowdown has been established against the earlier baseline.
Recent median: 288 ms · Earlier median: 305 ms. Flags require at least 3 recent and 5 earlier checks, more than twice the baseline, and at least 500 ms extra latency. Slowness alone does not identify server load as the cause.
Emerging down-report signals
- is descript down
Query “is descript” · observed 2026-11-11 03:55:34 UTC · 0 newly observed problem phrases.
Query “descript” · observed 2026-11-11 03:53:30 UTC · 0 newly observed problem phrases.
Emerging problem patterns can persist after an incident and do not measure report counts or prove an outage.
Is it down in your region?
Run one public website check from a community probe. Results describe that probe, not every user in a country.
Results are reused for 15 minutes. Shared free allowance: up to 60 tests per hour. A successful website check does not verify authenticated app or API functions.
Infrastructure incident context
Check whether broader platform incidents coincide with the problem you are seeing. These providers are context, not verified dependencies of Descript.
No active incidents recorded.
- Changes to Cloudflare Workers are not producing Event Subscription events · investigating
- Fedramp Customers have Delayed Purges · identified
About Descript status on Iszdown
Check Descript availability, incident history, downtime reports, and website performance.
This page combines the available Descript report activity, official product status, public website measurements, and daily history. Each measurement has its own observation time. A search spike alone does not confirm downtime, and a reachable website does not establish that sign-in or every product feature works.
25 product-matched official components are listed above. Latest public website measurement: 2026-11-11T04:04:50.000Z.
Visit the official Descript website · Official provider status · How it works
What to check when Descript is not working
These are troubleshooting suggestions, not a list of currently reported problems.
Descript will not open
Compare your usual browser or app with a private browser window, then try another network if available. Save unsent work first. A difference between networks can help separate a local connection problem from a wider disruption.
Descript is slow or only one feature fails
Record the affected action, exact error, and time. Compare the website response measurements with any official component incidents; loading a homepage does not test every feature.
Website troubleshooting guide · Sign-in problems · API errors and timeouts
Include the time, affected feature, and error message when contacting official support. Keep passwords, payment information, session cookies, and access tokens private.
Recent Descript outage history
Latest available product-matched official incidents in the calendar’s archive. Times below use UTC. Duration is the provider’s recorded incident window, not a measurement of impact on every user.
| Incident | Started (UTC) | Recorded duration | Last collected status |
|---|---|---|---|
| Avatar Outage | 337 min | resolved | |
| Increased latency for agent API jobs | 1997 min | resolved | |
| Generate Layout is down | 140 min | resolved | |
| Transcription jobs failing | 54 min | resolved | |
| Issues with Project Sync | 181 min | resolved | |
| Rooms Recording Outage | 36 min | resolved | |
| Underlord | 967 min | resolved | |
| Backend Workflow Outage | 156 min | resolved |
Frequently asked questions about Descript
Is Descript down right now?
Provider reports operational. Mapped components are operational in the latest status update; individual experiences can vary. This page was assembled at 2026-11-11T04:08:33.000Z.
How many Descript outage reports are there today?
The displayed rolling 24-hour window contains 0 recorded reports, from 2026-11-10T04:00:00.000Z to 2026-11-11T04:00:00.000Z. This is not a calendar-day total or a count of affected people. Estimated activity is shown separately as an estimate.
Why does Descript show operational when it is not working for me?
An official operational status can coexist with a local network issue, account problem, or feature-specific incident. Compare the mapped components, recent incident updates, and regional diagnostic on this page. Automated website checks test public access, not your signed-in session or every Descript feature.
When was Descript status last updated?
The latest status observation was 2026-11-11T03:56:43.000Z. Only matched product components and incidents are shown. The assessment is recent.
Has Descript had outages before?
The daily calendar links available incident evidence and retains daily monitoring summaries. Pink marks service issues, green requires sufficient observations with no issues observed, and gray means insufficient coverage. The collected history is incomplete and is not a lifetime outage count or a guarantee of uninterrupted uptime.
How do I follow Descript or report a problem?
Use “Watch this service” to save Descript in this browser’s watchlist, then return to compare its status with other saved services. Optional browser notifications can flag status changes while the watchlist page stays open and visible; background alerts are not sent. Use the problem-report button for an outage report; contact the provider through its official website for account, billing, or private support issues. Iszdown is independent and cannot resolve provider support tickets.
Related services to Descript
Check a related product separately; its status can differ from Descript.