User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
Is Velt down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → velt.dev—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
Live outage map
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
What's broken
Recent reports
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
Our checks
Reaching it
Last checked 57 min ago. Last stored result reached it in 387 ms.
Official status
All clear
All Systems Operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 15 | 0 | 0.0 | 279 ms | 0 |
| Mon 17 | 0 | 0.0 | 400 ms | 0 |
| Mon 20 | 0 | 0.0 | 349 ms | 0 |
| Mon 22 | 0 | 0.0 | 457 ms | 0 |
| Tue 00 | 0 | 0.0 | 244 ms | 0 |
| Tue 02 | 0 | 0.0 | 405 ms | 0 |
| Tue 04 | 0 | 0.0 | 367 ms | 0 |
| Tue 06 | 0 | 0.0 | 586 ms | 0 |
| Tue 08 | 0 | 0.0 | 413 ms | 0 |
| Tue 10 | 0 | 0.0 | 332 ms | 0 |
| Tue 12 | 0 | 0.0 | 348 ms | 0 |
| Tue 15 | 0 | 0.0 | 473 ms | 0 |
| Tue 17 | 0 | 0.0 | 354 ms | 0 |
| Tue 19 | 0 | 0.0 | 354 ms | 0 |
| Tue 21 | 0 | 0.0 | 308 ms | 0 |
| Wed 00 | 0 | 0.0 | 317 ms | 0 |
| Wed 02 | 0 | 0.0 | 323 ms | 0 |
| Wed 04 | 0 | 0.0 | 485 ms | 0 |
| Wed 06 | 0 | 0.0 | 507 ms | 0 |
| Wed 09 | 0 | 0.0 | 282 ms | 0 |
| Wed 11 | 0 | 0.0 | 464 ms | 0 |
| Wed 13 | 0 | 0.0 | 379 ms | 0 |
| Wed 15 | 0 | 0.0 | 388 ms | 0 |
| Wed 17 | 0 | 0.0 | 394 ms | 0 |
| Wed 19 | 0 | 0.0 | 543 ms | 0 |
| Wed 22 | 0 | 0.0 | 286 ms | 0 |
| Thu 00 | 0 | 0.0 | 583 ms | 0 |
| Thu 02 | 0 | 0.0 | 524 ms | 0 |
| Thu 04 | 0 | 0.0 | 364 ms | 0 |
| Thu 06 | 0 | 0.0 | 377 ms | 0 |
| Thu 08 | 0 | 0.0 | 535 ms | 0 |
| Thu 10 | 0 | 0.0 | 365 ms | 0 |
| Thu 12 | 0 | 0.0 | 542 ms | 0 |
| Thu 14 | 0 | 0.0 | 436 ms | 0 |
| Thu 16 | 0 | 0.0 | 433 ms | 0 |
| Thu 19 | 0 | 0.0 | 195 ms | 0 |
| Thu 21 | 0 | 0.0 | 409 ms | 0 |
| Thu 23 | 0 | 0.0 | 195 ms | 0 |
| Fri 01 | 0 | 0.0 | 461 ms | 0 |
| Fri 03 | 0 | 0.0 | 708 ms | 0 |
| Fri 05 | 0 | 0.0 | 401 ms | 0 |
| Fri 07 | 0 | 0.0 | 499 ms | 0 |
| Fri 08 | 0 | 0.0 | 429 ms | 0 |
| Fri 09 | 0 | 0.0 | 360 ms | 0 |
| Fri 11 | 0 | 0.0 | 422 ms | 0 |
| Fri 13 | 0 | 0.0 | 192 ms | 0 |
| Fri 15 | 0 | 0.0 | 450 ms | 0 |
| Fri 17 | 0 | 0.0 | 387 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 7 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live Velt badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for Velt yet. Outages of 10 minutes or more get their own page here.
Having trouble with Velt?
One report per service every 10 minutes from this network. No account.
Follow Velt
Get an email when Velt goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Velt alerts to Slack, Discord or a webhook — free.
About Velt
We track Velt (velt.dev) as part of the AI group. Embeddable review and approval for AI-native apps. Comments, approval flows, review agents, memory, and audit trails in one SDK.
Velt publishes an official status page at status.velt.dev; when we can read it, its incident level is folded into the status shown here.
Common problems for AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 364 ms average, 30–708 ms range across 17 successful checks.
Questions
Is Velt down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Velt last down?
We have not recorded a public Velt incident since monitoring began 7 days ago.
What is Velt's uptime?
From our own checks: 100% over 7 days of checks.
How fast does Velt respond?
364 ms on average over the last 24 hours (30–708 ms).
Does Velt have an official status page?
Yes, at https://status.velt.dev.
Velt not working for me but the status is fine. What now?
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report Velt here at once, the problem is on Velt's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Velt. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.