User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
Up, with a certificate warning. This site's security certificate is for a different name (server.advago.se), not midpoint.se. Most browsers still show a warning or refuse, and apps and strict clients will fail to connect.
midpoint.se · Cloud & developer
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Pågående driftstörning hos Microsoft 365 / Ongoing Microsoft 365 service disruption
Source: the vendor's status page · We are not affiliated with Midpoint.
Estimated fix: Not enough Midpoint history yet; similar Cloud & developer outages lasted 2 h (median, typically 48 min–10 h; 81 outages).
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.
Reachable from all 4 regions we check from.
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 36 min ago. Last stored result reached it in 1056 ms.
The server answered, but its security certificate has a problem (see the note above).
Minor incident
Pågående driftstörning hos Microsoft 365 / Ongoing Microsoft 365 service disruption Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 15 | 0 | 0.0 | 939 ms | 0 |
| Mon 17 | 0 | 0.0 | — | 2 |
| Mon 19 | 0 | 0.0 | 935 ms | 0 |
| Mon 21 | 0 | 0.0 | 828 ms | 0 |
| Mon 23 | 0 | 0.0 | 1003 ms | 0 |
| Tue 01 | 0 | 0.0 | 810 ms | 0 |
| Tue 03 | 0 | 0.0 | 1046 ms | 0 |
| Tue 05 | 0 | 0.0 | 950 ms | 0 |
| Tue 08 | 0 | 0.0 | 990 ms | 0 |
| Tue 10 | 0 | 0.0 | 1052 ms | 0 |
| Tue 12 | 0 | 0.0 | 918 ms | 0 |
| Tue 14 | 0 | 0.0 | 1057 ms | 0 |
| Tue 16 | 0 | 0.0 | 868 ms | 0 |
| Tue 18 | 0 | 0.0 | 1153 ms | 0 |
| Tue 21 | 0 | 0.0 | 870 ms | 0 |
| Tue 23 | 0 | 0.0 | 1050 ms | 0 |
| Wed 01 | 0 | 0.0 | 905 ms | 0 |
| Wed 03 | 0 | 0.0 | 788 ms | 0 |
| Wed 06 | 0 | 0.0 | 1033 ms | 0 |
| Wed 08 | 0 | 0.0 | 881 ms | 0 |
| Wed 10 | 0 | 0.0 | 817 ms | 0 |
| Wed 12 | 0 | 0.0 | 997 ms | 0 |
| Wed 14 | 0 | 0.0 | 827 ms | 0 |
| Wed 17 | 0 | 0.0 | 1056 ms | 0 |
| Wed 19 | 0 | 0.0 | 938 ms | 0 |
| Wed 21 | 0 | 0.0 | 990 ms | 0 |
| Wed 23 | 0 | 0.0 | 831 ms | 0 |
| Thu 01 | 0 | 0.0 | 1000 ms | 0 |
| Thu 03 | 0 | 0.0 | 1088 ms | 0 |
| Thu 05 | 0 | 0.0 | 809 ms | 0 |
| Thu 07 | 0 | 0.0 | 893 ms | 0 |
| Thu 09 | 0 | 0.0 | 963 ms | 0 |
| Thu 11 | 0 | 0.0 | 904 ms | 0 |
| Thu 13 | 0 | 0.0 | 980 ms | 0 |
| Thu 15 | 0 | 0.0 | 741 ms | 0 |
| Thu 17 | 0 | 0.0 | 887 ms | 0 |
| Thu 19 | 0 | 0.0 | 1021 ms | 0 |
| Thu 21 | 0 | 0.0 | 1457 ms | 0 |
| Thu 23 | 0 | 0.0 | 927 ms | 0 |
| Fri 01 | 0 | 0.0 | 1179 ms | 0 |
| Fri 03 | 0 | 0.0 | 797 ms | 0 |
| Fri 05 | 0 | 0.0 | 945 ms | 0 |
| Fri 08 | 0 | 0.0 | 1059 ms | 0 |
| Fri 10 | 0 | 0.0 | 929 ms | 0 |
| Fri 11 | 0 | 0.0 | 895 ms | 0 |
| Fri 12 | 0 | 0.0 | 956 ms | 0 |
| Fri 14 | 0 | 0.0 | 1145 ms | 0 |
| Fri 16 | 0 | 0.0 | 1056 ms | 0 |
97.18% 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.
One report per service every 10 minutes from this network. No account.
Get an email when Midpoint goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Midpoint alerts to Slack, Discord or a webhook — free.
We track Midpoint (midpoint.se) as part of the Cloud & developer group. Vi är en trygg IT-leverantör för företag med tydlig rådgivning och IT-tjänster som håller över tid – IT-partner som faktiskt avlastar er vardag.
Midpoint publishes an official status page at status.midpoint.se; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 97.18% over 7 days of checks. We logged 1 public incident since monitoring began 7 days ago.
Response time over the last 24 hours: 1008 ms average, 797–1457 ms range across 16 successful checks.
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Pågående driftstörning hos Microsoft 365 / Ongoing Microsoft 365 service disruption
The most recent public incident we recorded started 2026-11-09 and lasted 2 h 7 min. 1 incident since monitoring began 7 days ago.
From our own checks: 97.18% over 7 days of checks.
1008 ms on average over the last 24 hours (797–1457 ms). Latest regional checks: US East 898 ms, US West 798 ms, Europe 224 ms, Asia-Pacific 1509 ms.
Yes, at https://status.midpoint.se.
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 Midpoint here at once, the problem is on Midpoint'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 Midpoint. 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.