Continue
Operational Dev toolOpen-source AI code assistant — JetBrains + VS Code, custom models.
API endpoint reachable · 5h ago
Response time · 24h
Measured by Prismix probes — not the vendor's status feed.
1555ms
p50
- min
- 1536ms
- p50
- 1555ms
- p95
- 1907ms
- p99
- 1907ms
Embed this live badge
Updates ~30s · append ?theme=dark for dark READMEs
Light
Dark
Copy snippet ↓
Markdown · light
[](https://prismix.dev/service/continue-dev) Markdown · dark
[](https://prismix.dev/service/continue-dev) HTML
<a href="https://prismix.dev/service/continue-dev"><img src="https://prismix.dev/api/badge/continue-dev.svg" alt="Continue status"></a> No public status API
Continue doesn't publish a machine-readable status feed. We track it by probing its main endpoint every minute — reachable = operational, unreachable = major outage. Incident timeline and component breakdown aren't available for this provider until they (or a community status mirror) publishes a feed.
Common questions about Continue
Is Continue down right now?
Continue is currently reporting operational. We last checked under 5 minutes ago.
Where does this status data come from?
We probe Continue's public endpoint every 5 minutes and record reachability + latency. No login or API key required.
Can I get email or webhook alerts when Continue breaks?
Yes — sign in, star Continue on the status dashboard, then add an email or Discord/Slack webhook on /alerts. Free tier gets 1 destination per channel; Pro gets 5.
What does "Operational" mean?
All systems operating normally. No active incidents reported.
Related dev tools
Get notified when Continue changes state
One-click email alerts for Continue only. No account. No Pro tier. Unsubscribe in every email.
Want to subscribe to multiple services + control severity threshold + add quiet hours? Create a free account instead.
Last refreshed 59m ago · cached · data from https://continue.dev