User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
erikolsson.se · 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 40 min ago. Last stored result reached it in 1073 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 7 | 0 | 0.0 | 1065 ms | 0 |
| Nov 7 | 0 | 0.0 | 922 ms | 0 |
| Nov 8 | 0 | 0.0 | 1052 ms | 0 |
| Nov 8 | 0 | 0.0 | 960 ms | 0 |
| Nov 8 | 0 | 0.0 | 1043 ms | 0 |
| Nov 8 | 0 | 0.0 | 1139 ms | 0 |
| Nov 9 | 0 | 0.0 | 1118 ms | 0 |
| Nov 9 | 0 | 0.0 | 1044 ms | 0 |
| Nov 9 | 0 | 0.0 | 960 ms | 0 |
| Nov 9 | 0 | 0.0 | 802 ms | 0 |
| Nov 10 | 0 | 0.0 | 1109 ms | 0 |
| Nov 10 | 0 | 0.0 | 1034 ms | 0 |
| Nov 10 | 0 | 0.0 | 1204 ms | 0 |
| Nov 10 | 0 | 0.0 | 1113 ms | 0 |
| Nov 11 | 0 | 0.0 | 982 ms | 0 |
| Nov 11 | 0 | 0.0 | 978 ms | 0 |
| Nov 11 | 0 | 0.0 | 1008 ms | 0 |
| Nov 11 | 0 | 0.0 | 927 ms | 0 |
| Nov 12 | 0 | 0.0 | 1025 ms | 0 |
| Nov 12 | 0 | 0.0 | 1061 ms | 0 |
| Nov 12 | 0 | 0.0 | 1113 ms | 0 |
| Nov 12 | 0 | 0.0 | 1001 ms | 0 |
| Nov 13 | 0 | 0.0 | 841 ms | 0 |
| Nov 13 | 0 | 0.0 | 1151 ms | 0 |
| Nov 13 | 0 | 0.0 | 911 ms | 0 |
| Nov 13 | 0 | 0.0 | 1078 ms | 0 |
| Nov 14 | 0 | 0.0 | 950 ms | 0 |
| Nov 14 | 0 | 0.0 | 1120 ms | 0 |
| Nov 14 | 0 | 0.0 | 931 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 Erik Olsson 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 Erik Olsson goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send confirmed down and recovery alerts to Slack, Discord or a webhook — free. Early warnings are part of Owner Alerts.
Erik Olsson is listed in our Cloud & developer category and checked at erikolsson.se. Erik Olsson har mäklare i bland annat Stockholm, Göteborg och Malmö. Våra mäklare hjälper dig som ska köpa eller sälja bostad till en trygg bostadsaffär. Välkommen!
Erik Olsson publishes an official status page at status.erikolsson.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: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 1045 ms average, 799–1317 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 Erik Olsson incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
1045 ms on average over the last 24 hours (799–1317 ms).
Yes, at https://status.erikolsson.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 Erik Olsson here at once, the problem is on Erik Olsson'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 Erik Olsson. 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.