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 55 min ago. Last stored result reached it in 1381 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 8 | 0 | 0.0 | 1538 ms | 0 |
| Nov 8 | 0 | 0.0 | 1228 ms | 0 |
| Nov 8 | 0 | 0.0 | 1539 ms | 0 |
| Nov 8 | 0 | 0.0 | 1281 ms | 0 |
| Nov 9 | 0 | 0.0 | 1356 ms | 0 |
| Nov 9 | 0 | 0.0 | 1284 ms | 0 |
| Nov 9 | 0 | 0.0 | 1546 ms | 0 |
| Nov 9 | 0 | 0.0 | 1352 ms | 0 |
| Nov 10 | 0 | 0.0 | 1490 ms | 0 |
| Nov 10 | 0 | 0.0 | 1268 ms | 0 |
| Nov 10 | 0 | 0.0 | 1316 ms | 0 |
| Nov 10 | 0 | 0.0 | 1481 ms | 0 |
| Nov 11 | 0 | 0.0 | 1475 ms | 0 |
| Nov 11 | 0 | 0.0 | 1586 ms | 0 |
| Nov 11 | 0 | 0.0 | 2030 ms | 0 |
| Nov 11 | 0 | 0.0 | 1355 ms | 0 |
| Nov 12 | 0 | 0.0 | 1582 ms | 0 |
| Nov 12 | 0 | 0.0 | 1855 ms | 0 |
| Nov 12 | 0 | 0.0 | 1435 ms | 0 |
| Nov 12 | 0 | 0.0 | 1463 ms | 0 |
| Nov 13 | 0 | 0.0 | 1422 ms | 0 |
| Nov 13 | 0 | 0.0 | 2030 ms | 0 |
| Nov 13 | 0 | 0.0 | 1979 ms | 0 |
| Nov 13 | 0 | 0.0 | 1381 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 6 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Shtab 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 Shtab goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Shtab alerts to Slack, Discord or a webhook — free.
Shtab, at shtab.app, is one of the Cloud & developer services we monitor. Российская платформа совместной работы: проекты и задачи, канбан и Ганта, OKR, база знаний, ИИ-ассистент. Бесплатно без лимита людей, облако или свой сервер.
Shtab publishes an official status page at status.shtab.app; 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 6 days of checks. No public incidents logged since monitoring began 6 days ago.
Response time over the last 24 hours: 1457 ms average, 191–2172 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 Shtab incident since monitoring began 6 days ago.
From our own checks: 100% over 6 days of checks.
1457 ms on average over the last 24 hours (191–2172 ms).
Yes, at https://status.shtab.app.
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 Shtab here at once, the problem is on Shtab'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 Shtab. 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.