User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
graebert.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 18 min ago. Last stored result reached it in 990 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 09 | 0 | 0.0 | 942 ms | 0 |
| Tue 11 | 0 | 0.0 | 1306 ms | 0 |
| Tue 14 | 0 | 0.0 | 220 ms | 0 |
| Tue 16 | 0 | 0.0 | 1372 ms | 0 |
| Tue 18 | 0 | 0.0 | 1442 ms | 0 |
| Tue 20 | 0 | 0.0 | 651 ms | 0 |
| Tue 23 | 0 | 0.0 | 978 ms | 0 |
| Wed 01 | 0 | 0.0 | 881 ms | 0 |
| Wed 03 | 0 | 0.0 | 453 ms | 0 |
| Wed 05 | 0 | 0.0 | 327 ms | 0 |
| Wed 08 | 0 | 0.0 | 1245 ms | 0 |
| Wed 10 | 0 | 0.0 | 888 ms | 0 |
| Wed 12 | 0 | 0.0 | 257 ms | 0 |
| Wed 14 | 0 | 0.0 | 911 ms | 0 |
| Wed 16 | 0 | 0.0 | 240 ms | 0 |
| Wed 18 | 0 | 0.0 | 741 ms | 0 |
| Wed 21 | 0 | 0.0 | 327 ms | 0 |
| Wed 23 | 0 | 0.0 | 895 ms | 0 |
| Thu 01 | 0 | 0.0 | 190 ms | 0 |
| Thu 03 | 0 | 0.0 | 728 ms | 0 |
| Thu 05 | 0 | 0.0 | 900 ms | 0 |
| Thu 07 | 0 | 0.0 | 232 ms | 0 |
| Thu 09 | 0 | 0.0 | 584 ms | 0 |
| Thu 11 | 0 | 0.0 | 867 ms | 0 |
| Thu 13 | 0 | 0.0 | 1131 ms | 0 |
| Thu 15 | 0 | 0.0 | 230 ms | 0 |
| Thu 17 | 0 | 0.0 | 816 ms | 0 |
| Thu 20 | 0 | 0.0 | 791 ms | 0 |
| Thu 22 | 0 | 0.0 | 898 ms | 0 |
| Fri 00 | 0 | 0.0 | 657 ms | 0 |
| Fri 02 | 0 | 0.0 | 871 ms | 0 |
| Fri 04 | 0 | 0.0 | 888 ms | 0 |
| Fri 06 | 0 | 0.0 | 803 ms | 0 |
| Fri 08 | 0 | 0.0 | 169 ms | 0 |
| Fri 09 | 0 | 0.0 | 245 ms | 0 |
| Fri 11 | 0 | 0.0 | 678 ms | 0 |
| Fri 13 | 0 | 0.0 | 925 ms | 0 |
| Fri 15 | 0 | 0.0 | 201 ms | 0 |
| Fri 17 | 0 | 0.0 | 805 ms | 0 |
| Fri 19 | 0 | 0.0 | 607 ms | 0 |
| Fri 21 | 0 | 0.0 | 1385 ms | 0 |
| Fri 23 | 0 | 0.0 | 775 ms | 0 |
| Sat 01 | 0 | 0.0 | 244 ms | 0 |
| Sat 03 | 0 | 0.0 | 1330 ms | 0 |
| Sat 04 | 0 | 0.0 | 796 ms | 0 |
| Sat 06 | 0 | 0.0 | 330 ms | 0 |
| Sat 07 | 0 | 0.0 | 840 ms | 0 |
| Sat 09 | 0 | 0.0 | 990 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 9 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Graebert GmbH 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 Graebert GmbH goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Graebert GmbH alerts to Slack, Discord or a webhook — free.
We track Graebert GmbH (graebert.com) as part of the Cloud & developer group. Graebert specializes in 2D/3D CAD software to create and modify DWG drawings on Desktop, Mobile and Cloud as well as surveying software and services.
Graebert GmbH publishes an official status page at status.graebert.com; 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 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 723 ms average, 201–1385 ms range across 16 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Graebert GmbH incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
723 ms on average over the last 24 hours (201–1385 ms).
Yes, at https://status.graebert.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 Graebert GmbH here at once, the problem is on Graebert GmbH'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 Graebert GmbH. 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.