User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / 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 80 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 20 | 0 | 0.0 | 254 ms | 0 |
| Tue 23 | 0 | 0.0 | 133 ms | 0 |
| Wed 01 | 0 | 0.0 | 207 ms | 0 |
| Wed 03 | 0 | 0.0 | 379 ms | 0 |
| Wed 05 | 0 | 0.0 | 115 ms | 0 |
| Wed 08 | 0 | 0.0 | 23 ms | 0 |
| Wed 10 | 0 | 0.0 | 73 ms | 0 |
| Wed 12 | 0 | 0.0 | 143 ms | 0 |
| Wed 14 | 0 | 0.0 | 91 ms | 0 |
| Wed 16 | 0 | 0.0 | 91 ms | 0 |
| Wed 18 | 0 | 0.0 | 279 ms | 0 |
| Wed 21 | 0 | 0.0 | 189 ms | 0 |
| Wed 23 | 0 | 0.0 | 99 ms | 0 |
| Thu 01 | 0 | 0.0 | 483 ms | 0 |
| Thu 03 | 0 | 0.0 | 331 ms | 0 |
| Thu 05 | 0 | 0.0 | 295 ms | 0 |
| Thu 07 | 0 | 0.0 | 290 ms | 0 |
| Thu 09 | 0 | 0.0 | 182 ms | 0 |
| Thu 11 | 0 | 0.0 | 23 ms | 0 |
| Thu 13 | 0 | 0.0 | 425 ms | 0 |
| Thu 15 | 0 | 0.0 | 64 ms | 0 |
| Thu 18 | 0 | 0.0 | 115 ms | 0 |
| Thu 20 | 0 | 0.0 | 44 ms | 0 |
| Thu 22 | 0 | 0.0 | 53 ms | 0 |
| Fri 00 | 0 | 0.0 | 195 ms | 0 |
| Fri 02 | 0 | 0.0 | 317 ms | 0 |
| Fri 04 | 0 | 0.0 | 72 ms | 0 |
| Fri 05 | 0 | 0.0 | 190 ms | 0 |
| Fri 07 | 0 | 0.0 | 32 ms | 0 |
| Fri 09 | 0 | 0.0 | 52 ms | 0 |
| Fri 11 | 0 | 0.0 | 68 ms | 0 |
| Fri 13 | 0 | 0.0 | 323 ms | 0 |
| Fri 15 | 0 | 0.0 | 85 ms | 0 |
| Fri 17 | 0 | 0.0 | 101 ms | 0 |
| Fri 18 | 0 | 0.0 | 120 ms | 0 |
| Fri 19 | 0 | 0.0 | 436 ms | 0 |
| Fri 20 | 0 | 0.0 | 51 ms | 0 |
| Fri 22 | 0 | 0.0 | 96 ms | 0 |
| Fri 23 | 0 | 0.0 | 53 ms | 0 |
| Sat 01 | 0 | 0.0 | 279 ms | 0 |
| Sat 03 | 0 | 0.0 | 188 ms | 0 |
| Sat 05 | 0 | 0.0 | 67 ms | 0 |
| Sat 07 | 0 | 0.0 | 50 ms | 0 |
| Sat 09 | 0 | 0.0 | 30 ms | 0 |
| Sat 11 | 0 | 0.0 | 270 ms | 0 |
| Sat 14 | 0 | 0.0 | 92 ms | 0 |
| Sat 16 | 0 | 0.0 | 337 ms | 0 |
| Sat 18 | 0 | 0.0 | 80 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 ID06 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 ID06 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.
ID06 is listed in our Cloud & developer category and checked at id06.se. ID06 ger företag kontroll på arbetsplatsen med säkra ID06-kort, digital närvarokontroll och verifiering av leverantörer.
ID06 publishes an official status page at status.id06.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: 140 ms average, 30–337 ms range across 11 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public ID06 incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
140 ms on average over the last 24 hours (30–337 ms).
Yes, at https://status.id06.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 ID06 here at once, the problem is on ID06'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 ID06. 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.