Parasail reported "Partial outage" on its status page at 2026-10-31 22:06 UTC. Parasail reports a partial outage of Qwen3-VL 8B. Parasail says the problem is resolved. The outage lasted 6 minutes.

Parasail lists these components: Qwen3-VL 8B.

When did the incident start and end?

It started at 2026-10-31 22:06 UTC and ended at 2026-10-31 22:12 UTC. It lasted 6 min.

How do I get alerts for Parasail?

Subscribe to the Parasail 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 Parasail. outages.live reads it every few minutes and keeps every update. A language model writes the summary from those updates.

ParasailIncident · 2026-10-31 22:06 UTC

Partial outage

ResolvedOfficial update

Parasail reports a partial outage of Qwen3-VL 8B. Parasail says the problem is resolved. The outage lasted 6 minutes.

A language model wrote this summary from the updates of Parasail.

State

Resolved

Started

6 h ago

2026-10-31 22:06 UTC

Lasted

6 min

until 2026-10-31 22:12 UTC

Worst impact

Partial outage

Timeline

2 updates

22:0622:0722:0922:1022:12

Partial outageUpdate postedTimes in UTC

Components degraded

6 min 100%

Updates

Times in UTC

As posted by Parasail

Resolved2026-10-31 22:12 UTC

Components degraded2026-10-31 22:06 UTC

Affected components

Qwen3-VL 8B

Parasail in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

5 min

This incident

1.3× the median

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

5 h 51 min

median 5 min

90 days agoToday

Other Parasail incidents

All incidents

Parasail·Partial outage

Parasail reports a partial outage that affects Qwen3-VL 8B. Parasail reports a degraded service state for that component. The incident started at 22:18 UTC and continues.

Partial outageupdated 3 h ago

Parasail·Partial outage

Parasail reports that the Kimi K2.6 component does not work. The incident is resolved. It lasted 3 minutes.

Resolvedresolved 6 h ago

Follow Parasail

Your coding agent knows when Parasail is down, and tells you when a failure is theirs, not yours. You can also get Parasail 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 "parasail" and tell me if Parasail 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=parasail

Slack

/feed subscribe https://outages.cc/feed.xml?providers=parasail

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane