outages.live
Live
DeepInfraIncident ·

Partial outage

Partial outageOfficial update
0

DeepInfra reports a major outage that affects the Qwen3.5-35B-A3B component. The component is degraded. The incident started 45 minutes ago and is not resolved.

State

Components degraded

Started

Ongoing for

1 h 12 min

Worst impact

Major outage

Timeline

3 updates
04:4805:0605:2305:4105:59
Major outagePartial outageUpdate postedTimes in UTC

Components degraded

1 h 12 min 100%

Updates

Times in UTC

As posted by DeepInfra

Components degraded
Components degraded
Components degraded

Affected components

1
Qwen3.5-35B-A3B

DeepInfra in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

18

Days with an incident

5

Median duration

54 min

This incident

1.3× the median

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

2 h 3 min
median 54 min
90 days agoToday

Other DeepInfra incidents

All incidents

DeepInfra·Partial outage

DeepInfra reports a partial outage on the Qwen3.5-35B-A3B component. The outage is resolved. It lasted 48 minutes.

Resolved

DeepInfra·Degraded performance

DeepInfra reports degraded performance on the Qwen3.5-35B-A3B component. DeepInfra resolved this incident. The incident lasted 54 minutes.

Resolved

DeepInfra·Partial outage

DeepInfra reports a partial outage on the Qwen3.5-35B-A3B component. The incident is resolved. It lasted 36 minutes.

Resolved

DeepInfra·Partial outage

DeepInfra reports a partial outage on the Qwen3.5-35B-A3B component. DeepInfra reports that the incident is resolved. The outage lasted 66 minutes.

Resolved

DeepInfra·Degraded performance

DeepInfra reports degraded performance for Qwen3-VL-30B-A3B-Instruct. DeepInfra marked this incident as resolved. The incident lasted 54 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.cc/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.cc/feed.xml?providers=deepinfra
Slack
/feed subscribe https://outages.cc/feed.xml?providers=deepinfra

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane