DeepInfra lists these components: Qwen3.5-35B-A3B.

When did the incident start and end?

It started at 2026-11-03 07:06 UTC and ended at 2026-11-03 08:00 UTC. It lasted 54 min.

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 · 2026-11-03 07:06 UTC

Partial outage

Q: What happened?

DeepInfra reported "Partial outage" on its status page at 2026-11-03 07:06 UTC. DeepInfra reports a partial outage for the Qwen3.5-35B-A3B component. DeepInfra reports that the issue is resolved. The outage lasted 54 minutes.

ResolvedOfficial update

DeepInfra reports a partial outage for the Qwen3.5-35B-A3B component. DeepInfra reports that the issue is resolved. The outage lasted 54 minutes.

State

Resolved

Started

2 h ago

2026-11-03 07:06 UTC

Lasted

54 min

until 2026-11-03 08:00 UTC

Worst impact

Partial outage

Timeline

2 updates

07:0607:1907:3307:4608:00

Partial outageUpdate postedTimes in UTC

Components degraded

54 min 100%

Updates

Times in UTC

As posted by DeepInfra

Resolved2026-11-03 08:00 UTC

Components degraded2026-11-03 07:06 UTC

Affected components

Qwen3.5-35B-A3B

DeepInfra in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

56 min

This incident

About the median

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

1 h

median 56 min

90 days agoToday

Other DeepInfra incidents

All incidents

DeepInfra·Degraded performance

DeepInfra reports degraded performance for the Qwen3.5-35B-A3B component. DeepInfra resolved the problem. The outage lasted 18 minutes.

Resolvedresolved 3 h ago

DeepInfra·Partial outage

The Ling-3.1-flash component does not work. The interruption is partial. DeepInfra reports that the problem is resolved. The outage lasted 60 minutes.

Resolvedresolved 11 h ago

DeepInfra·Degraded performance

DeepInfra reports degraded performance on the Qwen3-Next-80B-A3B-Instruct component. DeepInfra marked this incident as resolved. The incident lasted 57 minutes.

Resolvedresolved 1 d ago

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