User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Productivity
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 21 | 0 | 0.0 | 67 ms | 0 |
| Tue 23 | 0 | 0.0 | 53 ms | 0 |
| Wed 01 | 0 | 0.0 | 87 ms | 0 |
| Wed 03 | 0 | 0.0 | 216 ms | 0 |
| Wed 06 | 0 | 0.0 | 111 ms | 0 |
| Wed 08 | 0 | 0.0 | 98 ms | 0 |
| Wed 10 | 0 | 0.0 | 69 ms | 0 |
| Wed 12 | 0 | 0.0 | 59 ms | 0 |
| Wed 14 | 0 | 0.0 | 83 ms | 0 |
| Wed 16 | 0 | 0.0 | 131 ms | 0 |
| Wed 19 | 0 | 0.0 | 60 ms | 0 |
| Wed 21 | 0 | 0.0 | 107 ms | 0 |
| Wed 23 | 0 | 0.0 | 86 ms | 0 |
| Thu 01 | 0 | 0.0 | 378 ms | 0 |
| Thu 03 | 0 | 0.0 | 263 ms | 0 |
| Thu 05 | 0 | 0.0 | 93 ms | 0 |
| Thu 07 | 0 | 0.0 | 87 ms | 0 |
| Thu 09 | 0 | 0.0 | 43 ms | 0 |
| Thu 11 | 0 | 0.0 | 64 ms | 0 |
| Thu 14 | 0 | 0.0 | 118 ms | 0 |
| Thu 16 | 0 | 0.0 | 84 ms | 0 |
| Thu 18 | 0 | 0.0 | 71 ms | 0 |
| Thu 20 | 0 | 0.0 | 138 ms | 0 |
| Thu 22 | 0 | 0.0 | 257 ms | 0 |
| Fri 00 | 0 | 0.0 | 104 ms | 0 |
| Fri 01 | 0 | 0.0 | 72 ms | 0 |
| Fri 03 | 0 | 0.0 | 223 ms | 0 |
| Fri 06 | 0 | 0.0 | 86 ms | 0 |
| Fri 08 | 0 | 0.0 | 70 ms | 0 |
| Fri 10 | 0 | 0.0 | 67 ms | 0 |
| Fri 11 | 0 | 0.0 | 74 ms | 0 |
| Fri 12 | 0 | 0.0 | 83 ms | 0 |
| Fri 14 | 0 | 0.0 | 79 ms | 0 |
| Fri 16 | 0 | 0.0 | 87 ms | 0 |
| Fri 18 | 0 | 0.0 | 79 ms | 0 |
| Fri 20 | 0 | 0.0 | 182 ms | 0 |
| Fri 22 | 0 | 0.0 | 558 ms | 0 |
| Sat 00 | 0 | 0.0 | 65 ms | 0 |
| Sat 02 | 0 | 0.0 | 83 ms | 0 |
| Sat 04 | 0 | 0.0 | 86 ms | 0 |
| Sat 06 | 0 | 0.0 | 65 ms | 0 |
| Sat 07 | 0 | 0.0 | 87 ms | 0 |
| Sat 09 | 0 | 0.0 | 63 ms | 0 |
| Sat 11 | 0 | 0.0 | 200 ms | 0 |
| Sat 13 | 0 | 0.0 | 65 ms | 0 |
| Sat 16 | 0 | 0.0 | 264 ms | 0 |
| Sat 17 | 0 | 0.0 | 75 ms | 0 |
| Sat 19 | 0 | 0.0 | 85 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 Linkster GmbH 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 Linkster GmbH 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.
We track Linkster GmbH (linkster.co) as part of the Productivity group. Linkster is the performance-focused influencer marketing platform that lets you track every click, conversion and euro in real time. Run global campaigns, automate workflows, and discover influencers to scale influencer marketing into a predictable revenue channel.
Linkster GmbH publishes an official status page at status.linkster.co; when we can read it, its incident level is folded into the status shown here.
Common problems for productivity services: files not syncing, editors not loading, and sign-in problems.
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: 141 ms average, 63–558 ms range across 12 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Linkster GmbH incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
141 ms on average over the last 24 hours (63–558 ms).
Yes, at https://status.linkster.co.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For productivity services, watch for files not syncing, editors not loading, and sign-in problems. If many people report Linkster GmbH here at once, the problem is on Linkster GmbH'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 Linkster GmbH. 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.