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 12 min ago. Last stored result reached it in 226 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 145 ms | 0 |
| Nov 7 | 0 | 0.0 | 343 ms | 0 |
| Nov 7 | 0 | 0.0 | 135 ms | 0 |
| Nov 7 | 0 | 0.0 | 223 ms | 0 |
| Nov 7 | 0 | 0.0 | 148 ms | 0 |
| Nov 8 | 0 | 0.0 | 168 ms | 0 |
| Nov 8 | 0 | 0.0 | 127 ms | 0 |
| Nov 8 | 0 | 0.0 | 131 ms | 0 |
| Nov 8 | 0 | 0.0 | 132 ms | 0 |
| Nov 9 | 0 | 0.0 | 194 ms | 0 |
| Nov 9 | 0 | 0.0 | 161 ms | 0 |
| Nov 9 | 0 | 0.0 | 158 ms | 0 |
| Nov 9 | 0 | 0.0 | 164 ms | 0 |
| Nov 10 | 0 | 0.0 | 159 ms | 0 |
| Nov 10 | 0 | 0.0 | 155 ms | 0 |
| Nov 10 | 0 | 0.0 | 212 ms | 0 |
| Nov 10 | 0 | 0.0 | 158 ms | 0 |
| Nov 11 | 0 | 0.0 | 196 ms | 0 |
| Nov 11 | 0 | 0.0 | 174 ms | 0 |
| Nov 11 | 0 | 0.0 | 161 ms | 0 |
| Nov 11 | 0 | 0.0 | 226 ms | 0 |
| Nov 12 | 0 | 0.0 | 150 ms | 0 |
| Nov 12 | 0 | 0.0 | 176 ms | 0 |
| Nov 12 | 0 | 0.0 | 842 ms | 0 |
| Nov 12 | 0 | 0.0 | 173 ms | 0 |
| Nov 13 | 0 | 0.0 | 210 ms | 0 |
| Nov 13 | 0 | 0.0 | 147 ms | 0 |
| Nov 13 | 0 | 0.0 | 170 ms | 0 |
| Nov 13 | 0 | 0.0 | 166 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 JSPM 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 JSPM goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send JSPM alerts to Slack, Discord or a webhook — free.
JSPM is listed in our Productivity category and checked at jspm.io. JSPM.IO - CDN Package Provider for the JSPM Project
JSPM publishes an official status page at status.jspm.io; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with productivity services: files not syncing, editors not loading, and sign-in problems.
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: 155 ms average, 7–274 ms range across 18 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public JSPM incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
155 ms on average over the last 24 hours (7–274 ms).
Yes, at https://status.jspm.io.
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 JSPM here at once, the problem is on JSPM'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 JSPM. 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.