outages.live
Live
DeepInfraIncident ·

Degraded performance

ResolvedOfficial update
0

DeepInfra reports degraded performance on the Qwen3-VL-235B-A22B-Instruct model. DeepInfra resolved the incident. The outage lasted 27 minutes.

State

Resolved

Started

Lasted

27 min

Worst impact

Degraded

Timeline

2 updates
11:3611:4311:4911:5612:03
DegradedUpdate postedTimes in UTC

Components degraded

27 min 100%

Updates

Times in UTC

As posted by DeepInfra

Resolved
Components degraded

Affected components

1
Qwen3-VL-235B-A22B-Instruct

DeepInfra in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

5

Days with an incident

2

Median duration

54 min

This incident

50% shorter than the median

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

1 h
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. DeepInfra resolved the outage after 54 minutes.

Resolved

DeepInfra·Degraded performance

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

Resolved

DeepInfra·Partial outage

DeepInfra reports a partial outage on Ling-3.1-flash. DeepInfra resolved the outage. It lasted 60 minutes.

Resolved

DeepInfra·Degraded performance

DeepInfra reported degraded performance on the Qwen3-Next-80B-A3B-Instruct component. DeepInfra reports that the incident is resolved. The incident lasted 57 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