User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
dooray.com · 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 min ago. Last stored result reached it in 666 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 23 | 0 | 0.0 | 482 ms | 0 |
| Tue 01 | 0 | 0.0 | 757 ms | 0 |
| Tue 03 | 0 | 0.0 | 649 ms | 0 |
| Tue 05 | 0 | 0.0 | 582 ms | 0 |
| Tue 07 | 0 | 0.0 | 629 ms | 0 |
| Tue 09 | 0 | 0.0 | 639 ms | 0 |
| Tue 11 | 0 | 0.0 | 592 ms | 0 |
| Tue 13 | 0 | 0.0 | 456 ms | 0 |
| Tue 16 | 0 | 0.0 | 638 ms | 0 |
| Tue 18 | 0 | 0.0 | 603 ms | 0 |
| Tue 20 | 0 | 0.0 | 684 ms | 0 |
| Tue 22 | 0 | 0.0 | 542 ms | 0 |
| Wed 01 | 0 | 0.0 | 630 ms | 0 |
| Wed 03 | 0 | 0.0 | 506 ms | 0 |
| Wed 05 | 0 | 0.0 | 607 ms | 0 |
| Wed 07 | 0 | 0.0 | 691 ms | 0 |
| Wed 10 | 0 | 0.0 | 699 ms | 0 |
| Wed 12 | 0 | 0.0 | 608 ms | 0 |
| Wed 14 | 0 | 0.0 | 544 ms | 0 |
| Wed 16 | 0 | 0.0 | 599 ms | 0 |
| Wed 18 | 0 | 0.0 | 583 ms | 0 |
| Wed 20 | 0 | 0.0 | 618 ms | 0 |
| Wed 23 | 0 | 0.0 | 648 ms | 0 |
| Thu 01 | 0 | 0.0 | 663 ms | 0 |
| Thu 03 | 0 | 0.0 | 621 ms | 0 |
| Thu 05 | 0 | 0.0 | 736 ms | 0 |
| Thu 07 | 0 | 0.0 | 635 ms | 0 |
| Thu 09 | 0 | 0.0 | 634 ms | 0 |
| Thu 11 | 0 | 0.0 | 622 ms | 0 |
| Thu 13 | 0 | 0.0 | 724 ms | 0 |
| Thu 15 | 0 | 0.0 | 669 ms | 0 |
| Thu 17 | 0 | 0.0 | 703 ms | 0 |
| Thu 19 | 0 | 0.0 | 644 ms | 0 |
| Thu 21 | 0 | 0.0 | 631 ms | 0 |
| Thu 23 | 0 | 0.0 | 625 ms | 0 |
| Fri 00 | 0 | 0.0 | 605 ms | 0 |
| Fri 02 | 0 | 0.0 | 590 ms | 0 |
| Fri 05 | 0 | 0.0 | 497 ms | 0 |
| Fri 07 | 0 | 0.0 | 638 ms | 0 |
| Fri 09 | 0 | 0.0 | 695 ms | 0 |
| Fri 11 | 0 | 0.0 | 604 ms | 0 |
| Fri 13 | 0 | 0.0 | 550 ms | 0 |
| Fri 15 | 0 | 0.0 | 793 ms | 0 |
| Fri 17 | 0 | 0.0 | 772 ms | 0 |
| Fri 19 | 0 | 0.0 | 624 ms | 0 |
| Fri 20 | 0 | 0.0 | 561 ms | 0 |
| Fri 21 | 0 | 0.0 | 757 ms | 0 |
| Fri 23 | 0 | 0.0 | 666 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 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Dooray! 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 Dooray! goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Dooray! alerts to Slack, Discord or a webhook — free.
Dooray!, at dooray.com, is one of the Cloud & developer services we monitor. NHN 두레이는 프로젝트 협업을 기반으로 메신저, 메일, 전자결재까지 기업에 필요한 모든 협업을 올인원으로 제공합니다.
Dooray! publishes an official status page at status.dooray.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
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: 641 ms average, 497–793 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 Dooray! incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
641 ms on average over the last 24 hours (497–793 ms).
Yes, at https://status.dooray.com.
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 Dooray! here at once, the problem is on Dooray!'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 Dooray!. 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.