User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
vectorize.io · 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 32 min ago. Last stored result reached it in 103 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 04 | 0 | 0.0 | 93 ms | 0 |
| Mon 06 | 0 | 0.0 | 99 ms | 0 |
| Mon 08 | 0 | 0.0 | 236 ms | 0 |
| Mon 10 | 0 | 0.0 | 196 ms | 0 |
| Mon 12 | 0 | 0.0 | 66 ms | 0 |
| Mon 14 | 0 | 0.0 | 121 ms | 0 |
| Mon 17 | 0 | 0.0 | 165 ms | 0 |
| Mon 19 | 0 | 0.0 | 167 ms | 0 |
| Mon 21 | 0 | 0.0 | 84 ms | 0 |
| Mon 23 | 0 | 0.0 | 206 ms | 0 |
| Tue 01 | 0 | 0.0 | 315 ms | 0 |
| Tue 03 | 0 | 0.0 | 78 ms | 0 |
| Tue 05 | 0 | 0.0 | 80 ms | 0 |
| Tue 07 | 0 | 0.0 | 66 ms | 0 |
| Tue 10 | 0 | 0.0 | 111 ms | 0 |
| Tue 12 | 0 | 0.0 | 113 ms | 0 |
| Tue 14 | 0 | 0.0 | 116 ms | 0 |
| Tue 16 | 0 | 0.0 | 57 ms | 0 |
| Tue 18 | 0 | 0.0 | 217 ms | 0 |
| Tue 21 | 0 | 0.0 | 95 ms | 0 |
| Tue 23 | 0 | 0.0 | 191 ms | 0 |
| Wed 01 | 0 | 0.0 | 117 ms | 0 |
| Wed 03 | 0 | 0.0 | 149 ms | 0 |
| Wed 06 | 0 | 0.0 | 59 ms | 0 |
| Wed 08 | 0 | 0.0 | 38 ms | 0 |
| Wed 10 | 0 | 0.0 | 86 ms | 0 |
| Wed 12 | 0 | 0.0 | 68 ms | 0 |
| Wed 15 | 0 | 0.0 | 98 ms | 0 |
| Wed 17 | 0 | 0.0 | 71 ms | 0 |
| Wed 19 | 0 | 0.0 | 209 ms | 0 |
| Wed 21 | 0 | 0.0 | 100 ms | 0 |
| Wed 23 | 0 | 0.0 | 85 ms | 0 |
| Thu 02 | 0 | 0.0 | 115 ms | 0 |
| Thu 04 | 0 | 0.0 | 189 ms | 0 |
| Thu 06 | 0 | 0.0 | 78 ms | 0 |
| Thu 08 | 0 | 0.0 | 76 ms | 0 |
| Thu 10 | 0 | 0.0 | 479 ms | 0 |
| Thu 12 | 0 | 0.0 | 198 ms | 0 |
| Thu 14 | 0 | 0.0 | 168 ms | 0 |
| Thu 16 | 0 | 0.0 | 99 ms | 0 |
| Thu 18 | 0 | 0.0 | 54 ms | 0 |
| Thu 20 | 0 | 0.0 | 201 ms | 0 |
| Thu 21 | 0 | 0.0 | 222 ms | 0 |
| Thu 23 | 0 | 0.0 | 139 ms | 0 |
| Fri 02 | 0 | 0.0 | 127 ms | 0 |
| Fri 04 | 0 | 0.0 | 92 ms | 0 |
| Fri 06 | 0 | 0.0 | 86 ms | 0 |
| Fri 08 | 0 | 0.0 | 103 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 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Vectorize 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 Vectorize goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Vectorize alerts to Slack, Discord or a webhook — free.
Vectorize, at vectorize.io, is one of the Cloud & developer services we monitor. Open source agent memory. Your agents learn from mistakes and get better over time. 94.6% on LongMemEval-S. MIT licensed.
Vectorize publishes an official status page at status.vectorize.io; when we can read it, its incident level is folded into the status shown here.
Common problems for cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
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: 164 ms average, 54–479 ms range across 12 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Vectorize incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
164 ms on average over the last 24 hours (54–479 ms).
Yes, at https://status.vectorize.io.
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 Vectorize here at once, the problem is on Vectorize'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 Vectorize. 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.