User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
vivacrm.ru · Cloud & developer
Is vivaCRM 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 → vivacrm.ru—
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 43 min ago. Last stored result reached it in 1986 ms.
Official status
All clear
No active incidents in the official feed Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 14:45 | 0 | 0.0 | 1839 ms | 0 |
| 16:45 | 0 | 0.0 | 2757 ms | 0 |
| 17:30 | 0 | 0.0 | 1909 ms | 0 |
| 18:15 | 0 | 0.0 | 1918 ms | 0 |
| 19:45 | 0 | 0.0 | 3427 ms | 0 |
| 20:45 | 0 | 0.0 | 2470 ms | 0 |
| 22:45 | 0 | 0.0 | 294 ms | 0 |
| 00:30 | 0 | 0.0 | 1616 ms | 0 |
| 02:45 | 0 | 0.0 | 1721 ms | 0 |
| 04:45 | 0 | 0.0 | 1687 ms | 0 |
| 07:00 | 0 | 0.0 | 1320 ms | 0 |
| 09:00 | 0 | 0.0 | 1889 ms | 0 |
| 11:15 | 0 | 0.0 | 1297 ms | 0 |
| 13:45 | 0 | 0.0 | 1986 ms | 0 |
Reliability
94.57% 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.
Embed this status: free live vivaCRM 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
Having trouble with vivaCRM?
One report per service every 10 minutes from this network. No account.
Follow vivaCRM
Get an email when vivaCRM goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send vivaCRM alerts to Slack, Discord or a webhook — free.
About vivaCRM
We track vivaCRM (vivacrm.ru) as part of the Cloud & developer group. Онлайн-запись, расписание, клиенты, финансы, зарплаты и аналитика в одной системе — для студий, клиник, клубов и фитнеса. Подключим за 3 дня и перенесём данные.
vivaCRM publishes an official status page at status.vivacrm.ru; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 94.57% over 8 days of checks. We logged 1 public incident since monitoring began 8 days ago.
Response time over the last 24 hours: 1866 ms average, 294–3427 ms range across 14 successful checks.
Questions
Is vivaCRM down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was vivaCRM last down?
The most recent public incident we recorded started 2026-11-12 and lasted 4 h 22 min. 1 incident since monitoring began 8 days ago.
What is vivaCRM's uptime?
From our own checks: 94.57% over 8 days of checks.
How fast does vivaCRM respond?
1866 ms on average over the last 24 hours (294–3427 ms).
Does vivaCRM have an official status page?
Yes, at https://status.vivacrm.ru.
vivaCRM 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 cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report vivaCRM here at once, the problem is on vivaCRM'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 vivaCRM. 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.