User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Productivity
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 1 hr ago. Last stored result reached it in 1070 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 13 | 0 | 0.0 | 993 ms | 0 |
| Tue 16 | 0 | 0.0 | 946 ms | 0 |
| Tue 18 | 0 | 0.0 | 942 ms | 0 |
| Tue 20 | 0 | 0.0 | 1027 ms | 0 |
| Tue 22 | 0 | 0.0 | 1026 ms | 0 |
| Wed 01 | 0 | 0.0 | 1061 ms | 0 |
| Wed 03 | 0 | 0.0 | 914 ms | 0 |
| Wed 05 | 0 | 0.0 | 1021 ms | 0 |
| Wed 07 | 0 | 0.0 | 1070 ms | 0 |
| Wed 10 | 0 | 0.0 | 2715 ms | 0 |
| Wed 12 | 0 | 0.0 | 918 ms | 0 |
| Wed 14 | 0 | 0.0 | 912 ms | 0 |
| Wed 16 | 0 | 0.0 | 1050 ms | 0 |
| Wed 18 | 0 | 0.0 | 1019 ms | 0 |
| Wed 20 | 0 | 0.0 | 996 ms | 0 |
| Wed 23 | 0 | 0.0 | 1050 ms | 0 |
| Thu 01 | 0 | 0.0 | 1034 ms | 0 |
| Thu 03 | 0 | 0.0 | 1067 ms | 0 |
| Thu 05 | 0 | 0.0 | 985 ms | 0 |
| Thu 07 | 0 | 0.0 | 842 ms | 0 |
| Thu 09 | 0 | 0.0 | 1112 ms | 0 |
| Thu 11 | 0 | 0.0 | 947 ms | 0 |
| Thu 13 | 0 | 0.0 | 1004 ms | 0 |
| Thu 15 | 0 | 0.0 | 982 ms | 0 |
| Thu 17 | 0 | 0.0 | 902 ms | 0 |
| Thu 19 | 0 | 0.0 | 1048 ms | 0 |
| Thu 21 | 0 | 0.0 | 944 ms | 0 |
| Thu 23 | 0 | 0.0 | 1081 ms | 0 |
| Fri 01 | 0 | 0.0 | 844 ms | 0 |
| Fri 04 | 0 | 0.0 | 1019 ms | 0 |
| Fri 06 | 0 | 0.0 | 954 ms | 0 |
| Fri 08 | 0 | 0.0 | 1009 ms | 0 |
| Fri 10 | 0 | 0.0 | 964 ms | 0 |
| Fri 11 | 0 | 0.0 | 970 ms | 0 |
| Fri 13 | 0 | 0.0 | 1019 ms | 0 |
| Fri 15 | 0 | 0.0 | 999 ms | 0 |
| Fri 17 | 0 | 0.0 | 946 ms | 0 |
| Fri 19 | 0 | 0.0 | 1031 ms | 0 |
| Fri 20 | 0 | 0.0 | 1045 ms | 0 |
| Fri 21 | 0 | 0.0 | 982 ms | 0 |
| Fri 22 | 0 | 0.0 | 942 ms | 0 |
| Sat 00 | 0 | 0.0 | 1043 ms | 0 |
| Sat 02 | 0 | 0.0 | 960 ms | 0 |
| Sat 04 | 0 | 0.0 | 907 ms | 0 |
| Sat 06 | 0 | 0.0 | 1020 ms | 0 |
| Sat 08 | 0 | 0.0 | 956 ms | 0 |
| Sat 10 | 0 | 0.0 | 925 ms | 0 |
| Sat 12 | 0 | 0.0 | 1070 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 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for DIAKRIT 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 DIAKRIT goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send DIAKRIT alerts to Slack, Discord or a webhook — free.
We track DIAKRIT (diakrit.com) as part of the Productivity group. The world’s best real estate experience starts here - Every day, leading real estate brands of the world use Diakrit’s property marketing innovations and …
DIAKRIT publishes an official status page at status.diakrit.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with productivity services: files not syncing, editors not loading, and sign-in problems.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 984 ms average, 907–1070 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 DIAKRIT incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
984 ms on average over the last 24 hours (907–1070 ms).
Yes, at https://status.diakrit.com.
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 DIAKRIT here at once, the problem is on DIAKRIT'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 DIAKRIT. 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.