DownForAI

Continue status: API, auth, latency & outage reports

Continue is operational right now. DownForAI checks Continue every ~75 minutes across 1 monitored surface, with 0 community reports in the last 24 hours.

Operational
Last probe 2h ago·1 surface
Probe-monitoredLow confidence
📚 Docs →
100.0%
24h Uptime
107ms
p50 Network Latencyⓘ
250ms
p95 Network Latencyⓘ
0
Incidents (30d)

DownForAI monitors Continue via a single endpoint — Continue Plugin. Current status: operational — all surfaces are responding normally. Measured uptime over the last 24 hours: 100.0%. Median response time (24 h): 107 ms; p95: 250 ms.

No incidents have been logged for Continue, and no community reports were received in the last 24 hours. Probes run continuously across the configured surfaces.

Data confidence: LowLast checked 2h 15m ago · 1 monitored surface · 1 with 24 h latency data

Current Status

✅
Operational
Everything works normally
✓Checked by our probes · 91ms
Verified 2h ago
✓No major incident reported
ⓘNo reports in the last 24h

Having issues?

Help other users by reporting if Continue is not working for you.

0reports in the last 24 hours

Surface Health

Continue PluginOperational
HTTP 200p50 107ms2h ago

Uptime — last 24h

100.0%

Network latency — last 20 probes

Loading…

What DownForAI can verify about Continue

No confirmed provider-side issue detected
DownForAI currently sees Continue as operational based on available monitoring signals.
Signal source: public surface check · Monitoring confidence: Low
Still having trouble?

The issue may be account-specific, regional, network-related, or related to authentication, billing, quota, or rate limits.

Incident history (30d)

✓No incidents recorded in the past 30 days.

Reported symptoms

No user reports for Continue in the last 24 hours.

Known error signatures

Common failure patterns and how to diagnose them

Provider details

Open-source AI coding assistant for VS Code and JetBrains. Connects to any model (local Ollama, Claude, GPT, etc.).

What we monitor
VS Code Extension — Continue VS Code extension
JetBrains Plugin — Continue JetBrains plugin
Model Routing Backend — Hosted features routing (if used)
Operator notes
  • Continue routes to user-configured models — most 'down' reports are provider-side (Ollama, OpenAI, etc.), not Continue itself.

Fallback alternatives

What to use if this service is down

Continue.dev extension is broken
Cursor, GitHub Copilot, or Codeium can reduce downtime for AI-assisted coding
Moderate effort

How we monitor

DownForAI checks monitored AI service surfaces on a rotating schedule, roughly every 75 minutes per surface, from a single centralized probe infrastructure. For services with an official machine-readable status page, we use that official status signal when available. For other services, we perform a basic public-surface check. Some services block datacenter probes; in those cases we mark them as “Monitoring limited” instead of treating a failed probe as a confirmed outage. Status is classified as Operational, Degraded, or Outage. Network latency (check response time) measures how long the monitored endpoint took to respond to our probe — it is not model inference speed, time-to-first-token, or tokens-per-second performance. We are independent of all providers listed and receive no compensation to report any particular status.

Continue statusEmbed this status badgeREADME · docs ▾
Markdown
[![Continue status](https://downforai.com/api/badge/continue-dev.svg)](https://downforai.com/continue-dev)
HTML
<a href="https://downforai.com/continue-dev"><img src="https://downforai.com/api/badge/continue-dev.svg" alt="Continue status" /></a>

Community Discussion

0/1000
No comments yet. Be the first to share your experience!

Still having issues with Continue?

Let the community know and help others experiencing the same problem.