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 527 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 22 | 0 | 0.0 | 378 ms | 0 |
| Tue 00 | 0 | 0.0 | 544 ms | 0 |
| Tue 02 | 0 | 0.0 | 578 ms | 0 |
| Tue 04 | 0 | 0.0 | 574 ms | 0 |
| Tue 06 | 0 | 0.0 | 1016 ms | 0 |
| Tue 08 | 0 | 0.0 | 517 ms | 0 |
| Tue 10 | 0 | 0.0 | 668 ms | 0 |
| Tue 13 | 0 | 0.0 | 428 ms | 0 |
| Tue 15 | 0 | 0.0 | 533 ms | 0 |
| Tue 17 | 0 | 0.0 | 469 ms | 0 |
| Tue 19 | 0 | 0.0 | 633 ms | 0 |
| Tue 22 | 0 | 0.0 | 650 ms | 0 |
| Wed 00 | 0 | 0.0 | 588 ms | 0 |
| Wed 02 | 0 | 0.0 | 614 ms | 0 |
| Wed 04 | 0 | 0.0 | 544 ms | 0 |
| Wed 07 | 0 | 0.0 | 606 ms | 0 |
| Wed 09 | 0 | 0.0 | 196 ms | 0 |
| Wed 11 | 0 | 0.0 | 398 ms | 0 |
| Wed 13 | 0 | 0.0 | 335 ms | 0 |
| Wed 15 | 0 | 0.0 | 636 ms | 0 |
| Wed 17 | 0 | 0.0 | 528 ms | 0 |
| Wed 20 | 0 | 0.0 | 350 ms | 0 |
| Wed 22 | 0 | 0.0 | 522 ms | 0 |
| Thu 00 | 0 | 0.0 | 590 ms | 0 |
| Thu 02 | 0 | 0.0 | 379 ms | 0 |
| Thu 04 | 0 | 0.0 | 564 ms | 0 |
| Thu 06 | 0 | 0.0 | 571 ms | 0 |
| Thu 08 | 0 | 0.0 | 571 ms | 0 |
| Thu 10 | 0 | 0.0 | 524 ms | 0 |
| Thu 12 | 0 | 0.0 | 555 ms | 0 |
| Thu 15 | 0 | 0.0 | 481 ms | 0 |
| Thu 17 | 0 | 0.0 | 586 ms | 0 |
| Thu 19 | 0 | 0.0 | 579 ms | 0 |
| Thu 21 | 0 | 0.0 | 420 ms | 0 |
| Thu 23 | 0 | 0.0 | 517 ms | 0 |
| Fri 01 | 0 | 0.0 | 610 ms | 0 |
| Fri 03 | 0 | 0.0 | 387 ms | 0 |
| Fri 05 | 0 | 0.0 | 620 ms | 0 |
| Fri 07 | 0 | 0.0 | 527 ms | 0 |
| Fri 09 | 0 | 0.0 | 577 ms | 0 |
| Fri 11 | 0 | 0.0 | 487 ms | 0 |
| Fri 12 | 0 | 0.0 | 413 ms | 0 |
| Fri 14 | 0 | 0.0 | 529 ms | 0 |
| Fri 16 | 0 | 0.0 | 422 ms | 0 |
| Fri 18 | 0 | 0.0 | 578 ms | 0 |
| Fri 20 | 0 | 0.0 | 478 ms | 0 |
| Fri 22 | 0 | 0.0 | 515 ms | 0 |
| Sat 00 | 0 | 0.0 | 588 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 sproof sign 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 sproof sign goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send sproof sign alerts to Slack, Discord or a webhook — free.
sproof sign, at sproof.com, is one of the Productivity services we monitor. SPROOF - DIGITALE SIGNATUREN & IDENTS - EU Anbieter - Signaturprozesse - IT Integration - für Unternehmen und Private - DSGVO konform - 100% rechtssicher
sproof sign publishes an official status page at status.sproof.com; when we can read it, its incident level is folded into the status shown here.
Typical issues 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: 507 ms average, 175–664 ms range across 17 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public sproof sign incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
507 ms on average over the last 24 hours (175–664 ms).
Yes, at https://status.sproof.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 sproof sign here at once, the problem is on sproof sign'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 sproof sign. 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.