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 1 hr ago. Last stored result reached it in 85 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 02 | 0 | 0.0 | 164 ms | 0 |
| Tue 04 | 0 | 0.0 | 202 ms | 0 |
| Tue 06 | 0 | 0.0 | 51 ms | 0 |
| Tue 08 | 0 | 0.0 | 32 ms | 0 |
| Tue 10 | 0 | 0.0 | 138 ms | 0 |
| Tue 12 | 0 | 0.0 | 29 ms | 0 |
| Tue 15 | 0 | 0.0 | 215 ms | 0 |
| Tue 17 | 0 | 0.0 | 314 ms | 0 |
| Tue 19 | 0 | 0.0 | 165 ms | 0 |
| Tue 21 | 0 | 0.0 | 138 ms | 0 |
| Wed 00 | 0 | 0.0 | 160 ms | 0 |
| Wed 02 | 0 | 0.0 | 66 ms | 0 |
| Wed 04 | 0 | 0.0 | 214 ms | 0 |
| Wed 06 | 0 | 0.0 | 311 ms | 0 |
| Wed 09 | 0 | 0.0 | 190 ms | 0 |
| Wed 11 | 0 | 0.0 | 59 ms | 0 |
| Wed 13 | 0 | 0.0 | 40 ms | 0 |
| Wed 15 | 0 | 0.0 | 29 ms | 0 |
| Wed 17 | 0 | 0.0 | 54 ms | 0 |
| Wed 20 | 0 | 0.0 | 84 ms | 0 |
| Wed 22 | 0 | 0.0 | 230 ms | 0 |
| Thu 00 | 0 | 0.0 | 63 ms | 0 |
| Thu 02 | 0 | 0.0 | 80 ms | 0 |
| Thu 04 | 0 | 0.0 | 203 ms | 0 |
| Thu 06 | 0 | 0.0 | 172 ms | 0 |
| Thu 08 | 0 | 0.0 | 297 ms | 0 |
| Thu 10 | 0 | 0.0 | 59 ms | 0 |
| Thu 12 | 0 | 0.0 | 222 ms | 0 |
| Thu 14 | 0 | 0.0 | 44 ms | 0 |
| Thu 17 | 0 | 0.0 | 66 ms | 0 |
| Thu 19 | 0 | 0.0 | 67 ms | 0 |
| Thu 21 | 0 | 0.0 | 51 ms | 0 |
| Thu 23 | 0 | 0.0 | 957 ms | 0 |
| Fri 01 | 0 | 0.0 | 203 ms | 0 |
| Fri 03 | 0 | 0.0 | 232 ms | 0 |
| Fri 05 | 0 | 0.0 | 35 ms | 0 |
| Fri 07 | 0 | 0.0 | 332 ms | 0 |
| Fri 08 | 0 | 0.0 | 246 ms | 0 |
| Fri 10 | 0 | 0.0 | 39 ms | 0 |
| Fri 11 | 0 | 0.0 | 214 ms | 0 |
| Fri 13 | 0 | 0.0 | 49 ms | 0 |
| Fri 15 | 0 | 0.0 | 108 ms | 0 |
| Fri 17 | 0 | 0.0 | 116 ms | 0 |
| Fri 19 | 0 | 0.0 | 51 ms | 0 |
| Fri 20 | 0 | 0.0 | 70 ms | 0 |
| Fri 22 | 0 | 0.0 | 200 ms | 0 |
| Fri 23 | 0 | 0.0 | 30 ms | 0 |
| Sat 00 | 0 | 0.0 | 67 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 9 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Wayke 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 Wayke goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Wayke alerts to Slack, Discord or a webhook — free.
Wayke is listed in our Cloud & developer category and checked at wayke.se. Vi vill att det ska vara lika härligt att köpa bil som att drömma om den. Wayke – en bättre marknadsplats för bilar.
Wayke publishes an official status page at status.wayke.se; 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 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 123 ms average, 30–332 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 Wayke incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
123 ms on average over the last 24 hours (30–332 ms).
Yes, at https://status.wayke.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 Wayke here at once, the problem is on Wayke'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 Wayke. 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.