User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Social
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 43 min ago. Last stored result reached it in 18 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Wed 06 | 0 | 0.0 | 124 ms | 0 |
| Wed 08 | 0 | 0.0 | 77 ms | 0 |
| Wed 10 | 0 | 0.0 | 129 ms | 0 |
| Wed 13 | 0 | 0.0 | 150 ms | 0 |
| Wed 15 | 0 | 0.0 | 137 ms | 0 |
| Wed 17 | 0 | 0.0 | 268 ms | 0 |
| Wed 19 | 0 | 0.0 | 125 ms | 0 |
| Wed 21 | 0 | 0.0 | 116 ms | 0 |
| Wed 23 | 0 | 0.0 | 111 ms | 0 |
| Thu 02 | 0 | 0.0 | 63 ms | 0 |
| Thu 04 | 0 | 0.0 | 153 ms | 0 |
| Thu 06 | 0 | 0.0 | 86 ms | 0 |
| Thu 08 | 0 | 0.0 | 119 ms | 0 |
| Thu 10 | 0 | 0.0 | 142 ms | 0 |
| Thu 12 | 0 | 0.0 | 284 ms | 0 |
| Thu 14 | 0 | 0.0 | 209 ms | 0 |
| Thu 16 | 0 | 0.0 | 167 ms | 0 |
| Thu 18 | 0 | 0.0 | 61 ms | 0 |
| Thu 20 | 0 | 0.0 | 108 ms | 0 |
| Thu 22 | 0 | 0.0 | 61 ms | 0 |
| Fri 00 | 0 | 0.0 | 67 ms | 0 |
| Fri 02 | 0 | 0.0 | 145 ms | 0 |
| Fri 04 | 0 | 0.0 | 119 ms | 0 |
| Fri 05 | 0 | 0.0 | 143 ms | 0 |
| Fri 07 | 0 | 0.0 | 150 ms | 0 |
| Fri 09 | 0 | 0.0 | 91 ms | 0 |
| Fri 11 | 0 | 0.0 | 65 ms | 0 |
| Fri 13 | 0 | 0.0 | 286 ms | 0 |
| Fri 15 | 0 | 0.0 | 181 ms | 0 |
| Fri 17 | 0 | 0.0 | 108 ms | 0 |
| Fri 19 | 0 | 0.0 | 174 ms | 0 |
| Fri 20 | 0 | 0.0 | 65 ms | 0 |
| Fri 21 | 0 | 0.0 | 162 ms | 0 |
| Fri 23 | 0 | 0.0 | 202 ms | 0 |
| Sat 01 | 0 | 0.0 | 174 ms | 0 |
| Sat 03 | 0 | 0.0 | 266 ms | 0 |
| Sat 04 | 0 | 0.0 | 107 ms | 0 |
| Sat 05 | 0 | 0.0 | 63 ms | 0 |
| Sat 07 | 0 | 0.0 | 151 ms | 0 |
| Sat 09 | 0 | 0.0 | 140 ms | 0 |
| Sat 11 | 0 | 0.0 | 225 ms | 0 |
| Sat 14 | 0 | 0.0 | 229 ms | 0 |
| Sat 16 | 0 | 0.0 | 303 ms | 0 |
| Sat 18 | 0 | 0.0 | 41 ms | 0 |
| Sat 21 | 0 | 0.0 | 178 ms | 0 |
| Sat 23 | 0 | 0.0 | 225 ms | 0 |
| Sun 01 | 0 | 0.0 | 73 ms | 0 |
| Sun 04 | 0 | 0.0 | 80 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 10 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Octadesk 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 Octadesk 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 Octadesk (octadesk.com) as part of the Social group. Da primeira mensagem ao helpdesk: centralize conversas, automatize com IA e resolva chamados em uma única plataforma. WhatsApp, chat e e-mail integrados.
Octadesk publishes an official status page at status.octadesk.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with social services: feeds not loading, posts or messages not sending, and login loops.
Measured uptime from our checks: 100% over 10 days of checks. No public incidents logged since monitoring began 10 days ago.
Response time over the last 24 hours: 141 ms average, 18–303 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Octadesk incident since monitoring began 10 days ago.
From our own checks: 100% over 10 days of checks.
141 ms on average over the last 24 hours (18–303 ms).
Yes, at https://status.octadesk.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For social services, watch for feeds not loading, posts or messages not sending, and login loops. If many people report Octadesk here at once, the problem is on Octadesk'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 Octadesk. 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.