User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
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.
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.
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.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 52 min ago. Last stored result reached it in 150 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 19 | 0 | 0.0 | 113 ms | 0 |
| Mon 22 | 0 | 0.0 | 174 ms | 0 |
| Tue 00 | 0 | 0.0 | 113 ms | 0 |
| Tue 02 | 0 | 0.0 | 112 ms | 0 |
| Tue 04 | 0 | 0.0 | 253 ms | 0 |
| Tue 06 | 0 | 0.0 | 157 ms | 0 |
| Tue 08 | 0 | 0.0 | 231 ms | 0 |
| Tue 10 | 0 | 0.0 | 121 ms | 0 |
| Tue 12 | 0 | 0.0 | 123 ms | 0 |
| Tue 15 | 0 | 0.0 | 123 ms | 0 |
| Tue 17 | 0 | 0.0 | 120 ms | 0 |
| Tue 19 | 0 | 0.0 | 150 ms | 0 |
| Tue 21 | 0 | 0.0 | 167 ms | 0 |
| Wed 00 | 0 | 0.0 | 160 ms | 0 |
| Wed 02 | 0 | 0.0 | 124 ms | 0 |
| Wed 04 | 0 | 0.0 | 116 ms | 0 |
| Wed 06 | 0 | 0.0 | 101 ms | 0 |
| Wed 09 | 0 | 0.0 | 179 ms | 0 |
| Wed 11 | 0 | 0.0 | 81 ms | 0 |
| Wed 13 | 0 | 0.0 | 204 ms | 0 |
| Wed 15 | 0 | 0.0 | 144 ms | 0 |
| Wed 17 | 0 | 0.0 | 131 ms | 0 |
| Wed 19 | 0 | 0.0 | 151 ms | 0 |
| Wed 22 | 0 | 0.0 | 99 ms | 0 |
| Thu 00 | 0 | 0.0 | 152 ms | 0 |
| Thu 02 | 0 | 0.0 | 124 ms | 0 |
| Thu 04 | 0 | 0.0 | 172 ms | 0 |
| Thu 06 | 0 | 0.0 | 115 ms | 0 |
| Thu 08 | 0 | 0.0 | 170 ms | 0 |
| Thu 10 | 0 | 0.0 | 152 ms | 0 |
| Thu 12 | 0 | 0.0 | 105 ms | 0 |
| Thu 14 | 0 | 0.0 | 119 ms | 0 |
| Thu 16 | 0 | 0.0 | 180 ms | 0 |
| Thu 19 | 0 | 0.0 | 129 ms | 0 |
| Thu 21 | 0 | 0.0 | 139 ms | 0 |
| Thu 23 | 0 | 0.0 | 156 ms | 0 |
| Fri 01 | 0 | 0.0 | 138 ms | 0 |
| Fri 03 | 0 | 0.0 | 267 ms | 0 |
| Fri 06 | 0 | 0.0 | 149 ms | 0 |
| Fri 08 | 0 | 0.0 | 131 ms | 0 |
| Fri 10 | 0 | 0.0 | 189 ms | 0 |
| Fri 12 | 0 | 0.0 | 145 ms | 0 |
| Fri 14 | 0 | 0.0 | 265 ms | 0 |
| Fri 16 | 0 | 0.0 | 195 ms | 0 |
| Fri 18 | 0 | 0.0 | 132 ms | 0 |
| Fri 19 | 0 | 0.0 | 132 ms | 0 |
| Fri 21 | 0 | 0.0 | 158 ms | 0 |
| Fri 23 | 0 | 0.0 | 169 ms | 0 |
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 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Vellum yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Vellum goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Vellum alerts to Slack, Discord or a webhook — free.
Vellum, at vellum.ai, is one of the Cloud & developer services we monitor. An assistant that knows you deeply, evolves alongside you, and belongs to no one else. Powered by memory that remembers the way you do.
Vellum publishes an official status page at status.vellum.ai; when we can read it, its incident level is folded into the status shown here.
Typical issues with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 169 ms average, 121–267 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Vellum incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
169 ms on average over the last 24 hours (121–267 ms).
Yes, at https://status.vellum.ai.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report Vellum here at once, the problem is on Vellum'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 Vellum. 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.