Splashtop status history
Current state: operational — “All Systems Operational” per http://status.splashtop.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Splashtop incidents last?
From 4 incidents with a vendor-posted start and resolve time. Longest on record: (Global & EU stack) Our servers are currently experiencing an issue. You might not be able to log in Splashtop apps or my.splashtop.com. Our engineers are working to resolve it as soon as possible. We apologize for the inconvenience. — 54 min (2026-02-26 10:57 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.
Incidents on record (4)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-04-15 08:01 UTC | Unable to reach Splashtop Servers (EU stack) | resolved | major | 44 min |
| 2026-02-26 10:57 UTC | (Global & EU stack) Our servers are currently experiencing an issue. You might not be able to log in Splashtop apps or my.splashtop.com. Our engineers are working to resolve it as soon as possible. We apologize for the inconvenience. | resolved | critical | 54 min |
| 2026-01-05 07:02 UTC | Unable to reach Splashtop Servers (Global stack) | resolved | critical | 30 min |
| 2025-11-26 01:42 UTC | Intermittently unable to log in Splashtop app | resolved | minor | 23 min |
Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).
Watch Splashtop with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"splashtop"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}