User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
vivacrm.ru · 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 2 hr ago. Last stored result reached it in 1242 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Wed 04 | 0 | 0.0 | 1794 ms | 0 |
| Wed 06 | 0 | 0.0 | 3168 ms | 0 |
| Wed 09 | 0 | 0.0 | 1897 ms | 0 |
| Wed 11 | 0 | 0.0 | 1690 ms | 0 |
| Wed 13 | 0 | 0.0 | 2100 ms | 0 |
| Wed 15 | 0 | 0.0 | 1463 ms | 0 |
| Wed 17 | 0 | 0.0 | 1773 ms | 0 |
| Wed 19 | 0 | 0.0 | 2670 ms | 0 |
| Wed 22 | 0 | 0.0 | — | 1 |
| Thu 00 | 0 | 0.0 | — | 2 |
| Thu 02 | 0 | 0.0 | — | 2 |
| Thu 04 | 0 | 0.0 | 2467 ms | 0 |
| Thu 06 | 0 | 0.0 | 1873 ms | 0 |
| Thu 08 | 0 | 0.0 | 2175 ms | 0 |
| Thu 10 | 0 | 0.0 | 1786 ms | 0 |
| Thu 12 | 0 | 0.0 | 2119 ms | 0 |
| Thu 15 | 0 | 0.0 | 2525 ms | 0 |
| Thu 17 | 0 | 0.0 | 1551 ms | 0 |
| Thu 19 | 0 | 0.0 | 1806 ms | 0 |
| Thu 21 | 0 | 0.0 | 2183 ms | 0 |
| Thu 23 | 0 | 0.0 | 1789 ms | 0 |
| Fri 01 | 0 | 0.0 | 2598 ms | 0 |
| Fri 03 | 0 | 0.0 | 925 ms | 0 |
| Fri 05 | 0 | 0.0 | 1433 ms | 0 |
| Fri 07 | 0 | 0.0 | 1561 ms | 0 |
| Fri 08 | 0 | 0.0 | 2426 ms | 0 |
| Fri 10 | 0 | 0.0 | 1715 ms | 0 |
| Fri 11 | 0 | 0.0 | 1773 ms | 0 |
| Fri 12 | 0 | 0.0 | 1909 ms | 0 |
| Fri 14 | 0 | 0.0 | 1839 ms | 0 |
| Fri 16 | 0 | 0.0 | 2757 ms | 0 |
| Fri 17 | 0 | 0.0 | 1909 ms | 0 |
| Fri 18 | 0 | 0.0 | 1918 ms | 0 |
| Fri 19 | 0 | 0.0 | 3427 ms | 0 |
| Fri 20 | 0 | 0.0 | 2470 ms | 0 |
| Fri 22 | 0 | 0.0 | 294 ms | 0 |
| Sat 00 | 0 | 0.0 | 1616 ms | 0 |
| Sat 02 | 0 | 0.0 | 1721 ms | 0 |
| Sat 04 | 0 | 0.0 | 1687 ms | 0 |
| Sat 07 | 0 | 0.0 | 1320 ms | 0 |
| Sat 09 | 0 | 0.0 | 1889 ms | 0 |
| Sat 11 | 0 | 0.0 | 1297 ms | 0 |
| Sat 13 | 0 | 0.0 | 1986 ms | 0 |
| Sat 16 | 0 | 0.0 | 2853 ms | 0 |
| Sat 18 | 0 | 0.0 | 1624 ms | 0 |
| Sat 20 | 0 | 0.0 | 908 ms | 0 |
| Sat 23 | 0 | 0.0 | 2038 ms | 0 |
| Sun 01 | 0 | 0.0 | 1242 ms | 0 |
94.90% 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.
One report per service every 10 minutes from this network. No account.
Get an email when vivaCRM goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send confirmed down and recovery alerts to Slack, Discord or a webhook — free. Early warnings are part of Owner Alerts.
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.90% over 9 days of checks. We logged 1 public incident since monitoring began 9 days ago.
Response time over the last 24 hours: 1614 ms average, 180–2853 ms range across 11 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
The most recent public incident we recorded started 2026-11-12 and lasted 4 h 22 min. 1 incident since monitoring began 9 days ago.
From our own checks: 94.90% over 9 days of checks.
1614 ms on average over the last 24 hours (180–2853 ms).
Yes, at https://status.vivacrm.ru.
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.