outages.live
Live
FactoryIncident · 2026-08-19 07:37 UTC

DeepSeek V4 Flash Degraded

ResolvedOfficial update

Response times have recovered to baseline levels.

The latest update from Factory.

State

Resolved

Started

75 d ago

2026-08-19 07:37 UTC

Lasted

28 min

until 2026-08-19 08:05 UTC

Worst impact

Partial outage

Timeline

2 updates
07:3707:4407:5107:5808:05
Partial outageUpdate postedTimes in UTC

Identified

28 min 100%

Updates

Times in UTC

As posted by Factory

Resolved2026-08-19 08:05 UTC

Response times have recovered to baseline levels.

Identified2026-08-19 07:37 UTC

We're monitoring an issue with our DeepSeek V4 Flash deployment that is causing slow response times. We will provide an update once this has been resolved.

Affected components

2
DeepSeekModels - DeepSeek

Factory in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

5

Days with an incident

5

Median duration

28 min

This incident

About the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

5 h 2 min
median 28 min
90 days agoToday

Other Factory incidents

All incidents

Factory·Service Disruption: User Authentication

The incident affecting our authentication provider, WorkOS, has been resolved. For full details regarding the resolution, please visit the WorkOS Status Page at https://status.workos.com/incidents/phs2prf38d75

Resolvedresolved 44 d ago

Factory·GLM 5.2 unavailable in our EU deployment

GLM 5.2 is available again in EU.

Resolvedresolved 68 d ago

Factory·Degraded Minimax M3 availability

Minimax M3 serving is fully restored.

Resolvedresolved 82 d ago

Factory·OpenAI Models Returning 431 Errors

We deployed a backend fix for the errors affecting OpenAI models and have confirmed that error rates returned to normal. Users can resume normal usage; no Factory CLI or Desktop update or other action is required.

Resolvedresolved 86 d ago

Follow Factory

Your coding agent knows when Factory is down, and tells you when a failure is theirs, not yours. You can also get Factory incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "factory" and tell me if Factory has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=factory
Slack
/feed subscribe https://outages.live/feed.xml?providers=factory

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane