Live

Degraded Performance

Service has recovered

The latest update from Novita AI.

State

Resolved

Started

Lasted

27 min

Worst impact

Degraded

Timeline

2 updates
11:3211:3911:4611:5312:00
DegradedUpdate postedTimes in UTC

Degraded

27 min 100%

Updates

Times in UTC

As posted by Novita AI

Resolved

Service has recovered

Degraded

sandbox event success rate check: status=degraded success=27 fail=36 total=63 rate=0.4286 window=180s

Affected components

1
Sandbox Usage

Novita AI in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

3

Days with an incident

3

Median duration

21 min

This incident

1.3× the median

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

7 h
median 21 min
90 days agoToday

Other Novita AI incidents

All incidents

Follow Novita AI

Your coding agent knows when Novita AI is down, and tells you when a failure is theirs, not yours. You can also get Novita AI 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 "novita" and tell me if Novita AI 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=novita
Slack
/feed subscribe https://outages.live/feed.xml?providers=novita

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane