User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Productivity
Is Doitb down?
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Some components degraded (no active incident posted)
Source: the vendor's status page · We are not affiliated with Doitb.
What to try while Doitb is having problems
Estimated fix: Not enough Doitb history yet; similar Productivity outages lasted 45 min (median, typically 14 min–4 h; 27 outages).
- Desktop and mobile apps often keep working offline on files you opened recently.
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 → doitb.com—
Your browser → us—
Our checksReaching it
Official · ReportsMinor incident · 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 16 min ago. Last stored result reached it in 244 ms.
Official status
Minor incident
Some components degraded (no active incident posted) Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 19 | 0 | 0.0 | 319 ms | 0 |
| Mon 21 | 0 | 0.0 | 301 ms | 0 |
| Mon 23 | 0 | 0.0 | 455 ms | 0 |
| Tue 01 | 0 | 0.0 | 314 ms | 0 |
| Tue 03 | 0 | 0.0 | 317 ms | 0 |
| Tue 05 | 0 | 0.0 | 263 ms | 0 |
| Tue 07 | 0 | 0.0 | 254 ms | 0 |
| Tue 10 | 0 | 0.0 | 339 ms | 0 |
| Tue 12 | 0 | 0.0 | 318 ms | 0 |
| Tue 14 | 0 | 0.0 | 292 ms | 0 |
| Tue 16 | 0 | 0.0 | 332 ms | 0 |
| Tue 18 | 0 | 0.0 | 259 ms | 0 |
| Tue 21 | 0 | 0.0 | 325 ms | 0 |
| Tue 23 | 0 | 0.0 | 253 ms | 0 |
| Wed 01 | 0 | 0.0 | 246 ms | 0 |
| Wed 03 | 0 | 0.0 | 320 ms | 0 |
| Wed 06 | 0 | 0.0 | 346 ms | 0 |
| Wed 08 | 0 | 0.0 | 247 ms | 0 |
| Wed 10 | 0 | 0.0 | 891 ms | 0 |
| Wed 12 | 0 | 0.0 | 294 ms | 0 |
| Wed 14 | 0 | 0.0 | 347 ms | 0 |
| Wed 16 | 0 | 0.0 | 279 ms | 0 |
| Wed 19 | 0 | 0.0 | 186 ms | 0 |
| Wed 21 | 0 | 0.0 | 238 ms | 0 |
| Wed 23 | 0 | 0.0 | 363 ms | 0 |
| Thu 01 | 0 | 0.0 | 268 ms | 0 |
| Thu 03 | 0 | 0.0 | 268 ms | 0 |
| Thu 05 | 0 | 0.0 | 188 ms | 0 |
| Thu 07 | 0 | 0.0 | 189 ms | 0 |
| Thu 09 | 0 | 0.0 | 182 ms | 0 |
| Thu 11 | 0 | 0.0 | 337 ms | 0 |
| Thu 13 | 0 | 0.0 | 288 ms | 0 |
| Thu 16 | 0 | 0.0 | 268 ms | 0 |
| Thu 17 | 0 | 0.0 | 247 ms | 0 |
| Thu 19 | 0 | 0.0 | 318 ms | 0 |
| Thu 21 | 0 | 0.0 | 260 ms | 0 |
| Thu 23 | 0 | 0.0 | 282 ms | 0 |
| Fri 01 | 0 | 0.0 | 459 ms | 0 |
| Fri 03 | 0 | 0.0 | 246 ms | 0 |
| Fri 05 | 0 | 0.0 | 307 ms | 0 |
| Fri 07 | 0 | 0.0 | 431 ms | 0 |
| Fri 09 | 0 | 0.0 | 323 ms | 0 |
| Fri 10 | 0 | 0.0 | 267 ms | 0 |
| Fri 11 | 0 | 0.0 | 253 ms | 0 |
| Fri 12 | 0 | 0.0 | 230 ms | 0 |
| Fri 14 | 0 | 0.0 | 304 ms | 0 |
| Fri 16 | 0 | 0.0 | 337 ms | 0 |
| Fri 18 | 0 | 0.0 | 244 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
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 7 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live Doitb 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
No outages on record for Doitb yet. Outages of 10 minutes or more get their own page here.
Having trouble with Doitb?
One report per service every 10 minutes from this network. No account.
Follow Doitb
Get an email when Doitb goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Doitb alerts to Slack, Discord or a webhook — free.
About Doitb
Doitb, at doitb.com, is one of the Productivity services we monitor. Increase the productivity of your team with Jira best Apps. Calendar for Jira. Timeline for Jira. eMatrix for Jira. Meetings for Jira.
Doitb publishes an official status page at status.doitb.com; when we can read it, its incident level is folded into the status shown here.
Common problems for productivity services: files not syncing, editors not loading, and sign-in problems.
Measured uptime from our checks: 100% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 300 ms average, 122–459 ms range across 15 successful checks.
Questions
Is Doitb down right now?
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Some components degraded (no active incident posted)
When was Doitb last down?
We have not recorded a public Doitb incident since monitoring began 7 days ago.
What is Doitb's uptime?
From our own checks: 100% over 7 days of checks.
How fast does Doitb respond?
300 ms on average over the last 24 hours (122–459 ms).
Does Doitb have an official status page?
Yes, at https://status.doitb.com.
Doitb 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 productivity services, watch for files not syncing, editors not loading, and sign-in problems. If many people report Doitb here at once, the problem is on Doitb'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 Doitb. 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.