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 15 min ago. Last stored result reached it in 373 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 22 | 0 | 0.0 | 761 ms | 0 |
| Tue 00 | 0 | 0.0 | 535 ms | 0 |
| Tue 02 | 0 | 0.0 | 471 ms | 0 |
| Tue 04 | 0 | 0.0 | 232 ms | 0 |
| Tue 06 | 0 | 0.0 | 436 ms | 0 |
| Tue 08 | 0 | 0.0 | 239 ms | 0 |
| Tue 10 | 0 | 0.0 | 386 ms | 0 |
| Tue 12 | 0 | 0.0 | 461 ms | 0 |
| Tue 13 | 0 | 0.0 | 13 ms | 0 |
| Tue 15 | 0 | 0.0 | 534 ms | 0 |
| Tue 17 | 0 | 0.0 | 260 ms | 0 |
| Tue 19 | 0 | 0.0 | 660 ms | 0 |
| Tue 22 | 0 | 0.0 | 968 ms | 0 |
| Wed 00 | 0 | 0.0 | 408 ms | 0 |
| Wed 02 | 0 | 0.0 | 352 ms | 0 |
| Wed 04 | 0 | 0.0 | 443 ms | 0 |
| Wed 06 | 0 | 0.0 | 385 ms | 0 |
| Wed 09 | 0 | 0.0 | 360 ms | 0 |
| Wed 11 | 0 | 0.0 | 90 ms | 0 |
| Wed 13 | 0 | 0.0 | 249 ms | 0 |
| Wed 15 | 0 | 0.0 | 600 ms | 0 |
| Wed 17 | 0 | 0.0 | 426 ms | 0 |
| Wed 20 | 0 | 0.0 | 1386 ms | 0 |
| Wed 22 | 0 | 0.0 | 493 ms | 0 |
| Thu 00 | 0 | 0.0 | 96 ms | 0 |
| Thu 02 | 0 | 0.0 | 351 ms | 0 |
| Thu 04 | 0 | 0.0 | 345 ms | 0 |
| Thu 06 | 0 | 0.0 | 288 ms | 0 |
| Thu 08 | 0 | 0.0 | 402 ms | 0 |
| Thu 10 | 0 | 0.0 | 419 ms | 0 |
| Thu 12 | 0 | 0.0 | 303 ms | 0 |
| Thu 13 | 0 | 0.0 | 483 ms | 0 |
| Thu 16 | 0 | 0.0 | 372 ms | 0 |
| Thu 18 | 0 | 0.0 | 615 ms | 0 |
| Thu 20 | 0 | 0.0 | 401 ms | 0 |
| Thu 22 | 0 | 0.0 | 1652 ms | 0 |
| Fri 00 | 0 | 0.0 | 483 ms | 0 |
| Fri 02 | 0 | 0.0 | 333 ms | 0 |
| Fri 04 | 0 | 0.0 | 751 ms | 0 |
| Fri 06 | 0 | 0.0 | 235 ms | 0 |
| Fri 08 | 0 | 0.0 | 291 ms | 0 |
| Fri 10 | 0 | 0.0 | 418 ms | 0 |
| Fri 12 | 0 | 0.0 | 356 ms | 0 |
| Fri 14 | 0 | 0.0 | 471 ms | 0 |
| Fri 16 | 0 | 0.0 | 541 ms | 0 |
| Fri 18 | 0 | 0.0 | 1095 ms | 0 |
| Fri 19 | 0 | 0.0 | 409 ms | 0 |
| Fri 21 | 0 | 0.0 | 373 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 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Skmtc 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 Skmtc goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Skmtc alerts to Slack, Discord or a webhook — free.
Skmtc is listed in our Productivity category and checked at skmtc.dev. Browse 17,200 OpenAPI schemas, generate production-grade clients, servers, forms and docs. When an API changes, get a pull request, not a changelog.
Skmtc publishes an official status page at status.skmtc.dev; 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 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 599 ms average, 54–1810 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 Skmtc incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
599 ms on average over the last 24 hours (54–1810 ms).
Yes, at https://status.skmtc.dev.
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 Skmtc here at once, the problem is on Skmtc'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 Skmtc. 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.