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 328 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 16 | 0 | 0.0 | 226 ms | 0 |
| Mon 18 | 0 | 0.0 | 267 ms | 0 |
| Mon 20 | 0 | 0.0 | 292 ms | 0 |
| Mon 22 | 0 | 0.0 | 182 ms | 0 |
| Tue 00 | 0 | 0.0 | 242 ms | 0 |
| Tue 02 | 0 | 0.0 | 285 ms | 0 |
| Tue 05 | 0 | 0.0 | 369 ms | 0 |
| Tue 07 | 0 | 0.0 | 194 ms | 0 |
| Tue 09 | 0 | 0.0 | 138 ms | 0 |
| Tue 11 | 0 | 0.0 | 166 ms | 0 |
| Tue 13 | 0 | 0.0 | 141 ms | 0 |
| Tue 15 | 0 | 0.0 | 210 ms | 0 |
| Tue 18 | 0 | 0.0 | 136 ms | 0 |
| Tue 20 | 0 | 0.0 | 153 ms | 0 |
| Tue 22 | 0 | 0.0 | 139 ms | 0 |
| Wed 00 | 0 | 0.0 | 182 ms | 0 |
| Wed 03 | 0 | 0.0 | 149 ms | 0 |
| Wed 05 | 0 | 0.0 | 212 ms | 0 |
| Wed 07 | 0 | 0.0 | 162 ms | 0 |
| Wed 09 | 0 | 0.0 | 167 ms | 0 |
| Wed 12 | 0 | 0.0 | 117 ms | 0 |
| Wed 14 | 0 | 0.0 | 232 ms | 0 |
| Wed 16 | 0 | 0.0 | 139 ms | 0 |
| Wed 18 | 0 | 0.0 | 436 ms | 0 |
| Wed 20 | 0 | 0.0 | 306 ms | 0 |
| Wed 22 | 0 | 0.0 | 161 ms | 0 |
| Thu 00 | 0 | 0.0 | 171 ms | 0 |
| Thu 02 | 0 | 0.0 | 196 ms | 0 |
| Thu 04 | 0 | 0.0 | 185 ms | 0 |
| Thu 06 | 0 | 0.0 | 171 ms | 0 |
| Thu 08 | 0 | 0.0 | 313 ms | 0 |
| Thu 10 | 0 | 0.0 | 458 ms | 0 |
| Thu 12 | 0 | 0.0 | 402 ms | 0 |
| Thu 14 | 0 | 0.0 | 352 ms | 0 |
| Thu 16 | 0 | 0.0 | 155 ms | 0 |
| Thu 18 | 0 | 0.0 | 377 ms | 0 |
| Thu 20 | 0 | 0.0 | 179 ms | 0 |
| Thu 22 | 0 | 0.0 | 147 ms | 0 |
| Fri 00 | 0 | 0.0 | 325 ms | 0 |
| Fri 02 | 0 | 0.0 | 317 ms | 0 |
| Fri 05 | 0 | 0.0 | 170 ms | 0 |
| Fri 07 | 0 | 0.0 | 173 ms | 0 |
| Fri 09 | 0 | 0.0 | 133 ms | 0 |
| Fri 10 | 0 | 0.0 | 211 ms | 0 |
| Fri 12 | 0 | 0.0 | 110 ms | 0 |
| Fri 13 | 0 | 0.0 | 187 ms | 0 |
| Fri 14 | 0 | 0.0 | 142 ms | 0 |
| Fri 16 | 0 | 0.0 | 328 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.
Scheduled maintenance
We will be undergoing scheduled maintenance during this time.
Planned maintenance is not an outage. Times and wording are the vendor’s own. Outage Weather →
No outages on record for MarkUp 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 MarkUp goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send MarkUp alerts to Slack, Discord or a webhook — free.
We track MarkUp (markup.io) as part of the Productivity group. MarkUp is the design collaboration tool that streamlines visual feedback. Annotate screenshots, PDFs, and designs in real-time with your team. Start free.
MarkUp publishes an official status page at status.markup.io; 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: 215 ms average, 110–377 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 MarkUp incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
215 ms on average over the last 24 hours (110–377 ms).
Yes, at https://status.markup.io.
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 MarkUp here at once, the problem is on MarkUp'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 MarkUp. 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.