User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
sanday.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 hr ago. Last stored result reached it in 702 ms.
All clear
All systems operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 01 | 0 | 0.0 | 1776 ms | 0 |
| Tue 04 | 0 | 0.0 | 606 ms | 0 |
| Tue 06 | 0 | 0.0 | 586 ms | 0 |
| Tue 08 | 0 | 0.0 | 645 ms | 0 |
| Tue 10 | 0 | 0.0 | 645 ms | 0 |
| Tue 12 | 0 | 0.0 | 664 ms | 0 |
| Tue 14 | 0 | 0.0 | 632 ms | 0 |
| Tue 17 | 0 | 0.0 | 525 ms | 0 |
| Tue 19 | 0 | 0.0 | 639 ms | 0 |
| Tue 21 | 0 | 0.0 | 666 ms | 0 |
| Tue 23 | 0 | 0.0 | 657 ms | 0 |
| Wed 02 | 0 | 0.0 | 825 ms | 0 |
| Wed 04 | 0 | 0.0 | 619 ms | 0 |
| Wed 06 | 0 | 0.0 | 602 ms | 0 |
| Wed 08 | 0 | 0.0 | 587 ms | 0 |
| Wed 11 | 0 | 0.0 | 716 ms | 0 |
| Wed 13 | 0 | 0.0 | 643 ms | 0 |
| Wed 15 | 0 | 0.0 | 645 ms | 0 |
| Wed 17 | 0 | 0.0 | 563 ms | 0 |
| Wed 19 | 0 | 0.0 | 688 ms | 0 |
| Wed 21 | 0 | 0.0 | 710 ms | 0 |
| Wed 23 | 0 | 0.0 | 731 ms | 0 |
| Thu 02 | 0 | 0.0 | 615 ms | 0 |
| Thu 04 | 0 | 0.0 | 564 ms | 0 |
| Thu 06 | 0 | 0.0 | 636 ms | 0 |
| Thu 08 | 0 | 0.0 | 634 ms | 0 |
| Thu 10 | 0 | 0.0 | 644 ms | 0 |
| Thu 12 | 0 | 0.0 | 624 ms | 0 |
| Thu 14 | 0 | 0.0 | 615 ms | 0 |
| Thu 16 | 0 | 0.0 | 579 ms | 0 |
| Thu 18 | 0 | 0.0 | 631 ms | 0 |
| Thu 20 | 0 | 0.0 | 654 ms | 0 |
| Thu 22 | 0 | 0.0 | 638 ms | 0 |
| Fri 00 | 0 | 0.0 | 766 ms | 0 |
| Fri 02 | 0 | 0.0 | 573 ms | 0 |
| Fri 05 | 0 | 0.0 | 622 ms | 0 |
| Fri 07 | 0 | 0.0 | 599 ms | 0 |
| Fri 09 | 0 | 0.0 | 625 ms | 0 |
| Fri 11 | 0 | 0.0 | 689 ms | 0 |
| Fri 12 | 0 | 0.0 | 559 ms | 0 |
| Fri 14 | 0 | 0.0 | 625 ms | 0 |
| Fri 15 | 0 | 0.0 | 619 ms | 0 |
| Fri 17 | 0 | 0.0 | 657 ms | 0 |
| Fri 18 | 0 | 0.0 | 646 ms | 0 |
| Fri 19 | 0 | 0.0 | 631 ms | 0 |
| Fri 20 | 0 | 0.0 | 642 ms | 0 |
| Fri 22 | 0 | 0.0 | 647 ms | 0 |
| Fri 23 | 0 | 0.0 | 702 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.
Onderhoud aan Sanday Apotheek
Op dit moment voeren we onderhoud uit aan Sanday Apotheek. Hierdoor kun je even niet met Sanday werken.
Planned maintenance is not an outage. Times and wording are the vendor’s own. Outage Weather →
No outages on record for Sanday 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 Sanday goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Sanday alerts to Slack, Discord or a webhook — free.
Sanday is listed in our Cloud & developer category and checked at sanday.com. Sanday bouwt software voor de eerstelijnszorg. Zonder ruis, zonder knelpunten. We noemen onszelf niet voor niets de digitale zorgverbinders!
Sanday publishes an official status page at status.sanday.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, 559–766 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 Sanday 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 (559–766 ms).
Yes, at https://status.sanday.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 Sanday here at once, the problem is on Sanday'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 Sanday. 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.