Back to overview
Resolved

Copilot degraded performance

Nov 3, 2026 at 12:00pm UTC

Resolved
Nov 8, 2026 at 9:32am UTC

Copilot is discontinued. Copilot blocks access for logged-out sessions, and this did not change, so we stopped the Copilot endpoint.

Requests to /v1/monitor/copilot, and batch tasks with taskType: "COPILOT", continue to return HTTP 400 with error code MODEL_UNAVAILABLE. We do not queue or charge these requests.

For Copilot Search answers, use Bing AI Mode (POST /v1/monitor/bing/aimode): https://cloro.dev/docs/api-reference/endpoint/monitor-bing-aimode.

We are closing this incident and removing Copilot from this status page.

Updated
Nov 4, 2026 at 11:43am UTC

Copilot requests are refused at once with HTTP 400 and error code MODEL_UNAVAILABLE, instead of failing with a 5xx error after retries. Copilot now gates access for logged-out sessions, and we’re working on a way to restore it. Refused requests are not queued or charged, and all other engines work as normal. We’ll post here when Copilot is back.

Updated
Nov 3, 2026 at 12:40pm UTC

Copilot has deteriorated into a major outage (success rate around 3% over the past hour). We're actively working to restore service.

Created
Nov 3, 2026 at 12:00pm UTC

We're seeing an elevated error rate on Copilot (success rate around 69% over the past hour). Our team is investigating — please retry any 5xx responses in the meantime. We'll keep you posted.