DeepInfra lists these components: Qwen3.5-397B-A17B.

When did the incident start and end?

It started at 2026-11-15 20:45 UTC. This page shows the end time when DeepInfra marks it resolved.

How do I get alerts for DeepInfra?

Subscribe to the DeepInfra live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of DeepInfra. outages.live reads it every few minutes and keeps every update. A language model writes the summary from those updates.

DeepInfraIncident ·

Major outage

Q: What happened?

DeepInfra reported "Major outage" on its status page at 2026-11-15 20:45 UTC. DeepInfra reports a major outage of the Qwen3.5-397B-A17B component. DeepInfra has not given a latest state beyond degraded components. The outage started 18 minutes ago and is not resolved.

Major outageOfficial update

DeepInfra reports a major outage of the Qwen3.5-397B-A17B component. DeepInfra has not given a latest state beyond degraded components. The outage started 18 minutes ago and is not resolved.

State

Components degraded

Started

Ongoing for

1 h 2 min

Worst impact

Major outage

Timeline

3 updates

20:4521:0021:1621:3121:47

Major outagePartial outageDegradedUpdate postedTimes in UTC

Components degraded

1 h 2 min 100%

Updates

Times in UTC

As posted by DeepInfra

Components degraded

Affected components

Qwen3.5-397B-A17B

DeepInfra in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

57 min

This incident

About the median

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

3 h 27 min

median 57 min

90 days agoToday

Other DeepInfra incidents

All incidents

DeepInfra·Degraded performance

DeepInfra reports degraded performance on the Qwen3.5-397B-A17B model. DeepInfra resolved this incident. The degraded performance lasted 57 minutes.

Resolved

DeepInfra·Degraded performance

DeepInfra reports degraded performance for MiniMax-M3. DeepInfra resolved the incident. The outage lasted 57 minutes.

Resolved

DeepInfra·Degraded performance

DeepInfra reports degraded performance for Inkling-2-Small. DeepInfra resolved the incident. The outage lasted 63 minutes.

Resolved

DeepInfra·Partial outage

DeepInfra reports a partial outage of NVIDIA-Nemotron-3.5-Transcribe-30B-A4B. DeepInfra states that the incident is resolved. The outage lasted 60 minutes.

Resolved

DeepInfra·Partial outage

DeepInfra reported a major outage of Qwen3-Next-80B-A3B-Instruct. DeepInfra reports that the incident is resolved. The outage lasted 129 minutes.

Resolved

Follow DeepInfra

Your coding agent knows when DeepInfra is down, and tells you when a failure is theirs, not yours. You can also get DeepInfra 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 "deepinfra" and tell me if DeepInfra 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=deepinfra

Slack

/feed subscribe https://outages.live/feed.xml?providers=deepinfra

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane