Partial outage
ResolvedOfficial update
0
DeepInfra reports a partial outage on Ling-3.1-flash. DeepInfra resolved the outage. It lasted 60 minutes.
State
Resolved
Started
1 h ago
2026-11-02 20:39 UTC
Lasted
1 h
until 2026-11-02 21:39 UTC
Worst impact
Partial outage
Timeline
2 updates20:3920:5421:0921:2421:39
Partial outageUpdate postedTimes in UTC
Components degraded
1 h 100%
Updates
Times in UTCAs posted by DeepInfra
Resolved2026-11-02 21:39 UTC
Components degraded2026-11-02 20:39 UTC
Affected components
1Ling-3.1-flash
DeepInfra in the last 90 days
Full history90 days agoToday
Incidents in 90 days
2
Days with an incident
1
Median duration
59 min
This incident
About the median
Other DeepInfra incidents
All incidentsFollow 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=deepinfraSlack
/feed subscribe https://outages.live/feed.xml?providers=deepinfraFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane