User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
The site answers but blocks automated checks, so we rely on user reports and the official status. User reports are near the baseline.
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.
Our checks can't reach SiteVibes right now
SiteVibes is blocking or timing out our automated checks, so we can't test it directly. We still count user reports and watch the official status page.
Last checked 46 min ago. Last stored result reached it in 81 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 37 ms | 0 |
| Nov 7 | 0 | 0.0 | 162 ms | 0 |
| Nov 7 | 0 | 0.0 | 88 ms | 0 |
| Nov 7 | 0 | 0.0 | 160 ms | 0 |
| Nov 8 | 0 | 0.0 | 168 ms | 0 |
| Nov 8 | 0 | 0.0 | 119 ms | 0 |
| Nov 8 | 0 | 0.0 | 87 ms | 0 |
| Nov 8 | 0 | 0.0 | 107 ms | 0 |
| Nov 9 | 0 | 0.0 | 181 ms | 0 |
| Nov 9 | 0 | 0.0 | 133 ms | 0 |
| Nov 9 | 0 | 0.0 | 184 ms | 0 |
| Nov 9 | 0 | 0.0 | 197 ms | 0 |
| Nov 10 | 0 | 0.0 | 101 ms | 0 |
| Nov 10 | 0 | 0.0 | 162 ms | 0 |
| Nov 10 | 0 | 0.0 | 221 ms | 0 |
| Nov 10 | 0 | 0.0 | 252 ms | 0 |
| Nov 11 | 0 | 0.0 | 179 ms | 0 |
| Nov 11 | 0 | 0.0 | 134 ms | 0 |
| Nov 11 | 0 | 0.0 | 163 ms | 0 |
| Nov 11 | 0 | 0.0 | 167 ms | 0 |
| Nov 12 | 0 | 0.0 | 161 ms | 0 |
| Nov 12 | 0 | 0.0 | 108 ms | 0 |
| Nov 12 | 0 | 0.0 | 206 ms | 0 |
| Nov 12 | 0 | 0.0 | 193 ms | 0 |
| Nov 13 | 0 | 0.0 | 215 ms | 0 |
| Nov 13 | 0 | 0.0 | 128 ms | 0 |
| Nov 13 | 0 | 0.0 | 301 ms | 0 |
| Nov 13 | 0 | 0.0 | 127 ms | 0 |
| Nov 14 | 0 | 0.0 | 148 ms | 0 |
| Nov 14 | 0 | 0.0 | 137 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 9 days of data so far, so the 90-day numbers fill in over time.
No outages on record for SiteVibes 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 SiteVibes goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send SiteVibes alerts to Slack, Discord or a webhook — free.
SiteVibes is listed in our AI category and checked at sitevibes.com. Email, SMS, loyalty and reviews on one AI ecommerce retention platform. Replace your disconnected stack and grow repeat revenue with SiteVibes.
SiteVibes publishes an official status page at status.sitevibes.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 163 ms average, 40–374 ms range across 17 successful checks.
The site answers but blocks automated checks, so we rely on user reports and the official status. User reports are near the baseline.
We have not recorded a public SiteVibes incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
163 ms on average over the last 24 hours (40–374 ms).
Yes, at https://status.sitevibes.com.
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 SiteVibes here at once, the problem is on SiteVibes'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 SiteVibes. 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.