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 2 hr ago. Last stored result reached it in 182 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 13 | 0 | 0.0 | 112 ms | 0 |
| Mon 15 | 0 | 0.0 | 139 ms | 0 |
| Mon 17 | 0 | 0.0 | 83 ms | 0 |
| Mon 19 | 0 | 0.0 | 140 ms | 0 |
| Mon 21 | 0 | 0.0 | 142 ms | 0 |
| Mon 23 | 0 | 0.0 | 119 ms | 0 |
| Tue 01 | 0 | 0.0 | 129 ms | 0 |
| Tue 03 | 0 | 0.0 | 100 ms | 0 |
| Tue 06 | 0 | 0.0 | 572 ms | 0 |
| Tue 08 | 0 | 0.0 | 252 ms | 0 |
| Tue 10 | 0 | 0.0 | 109 ms | 0 |
| Tue 12 | 0 | 0.0 | 226 ms | 0 |
| Tue 14 | 0 | 0.0 | 144 ms | 0 |
| Tue 16 | 0 | 0.0 | 180 ms | 0 |
| Tue 19 | 0 | 0.0 | 208 ms | 0 |
| Tue 21 | 0 | 0.0 | 103 ms | 0 |
| Tue 23 | 0 | 0.0 | 204 ms | 0 |
| Wed 01 | 0 | 0.0 | 100 ms | 0 |
| Wed 04 | 0 | 0.0 | 181 ms | 0 |
| Wed 06 | 0 | 0.0 | 165 ms | 0 |
| Wed 08 | 0 | 0.0 | 120 ms | 0 |
| Wed 10 | 0 | 0.0 | 49 ms | 0 |
| Wed 13 | 0 | 0.0 | 263 ms | 0 |
| Wed 15 | 0 | 0.0 | 235 ms | 0 |
| Wed 17 | 0 | 0.0 | 351 ms | 0 |
| Wed 19 | 0 | 0.0 | 189 ms | 0 |
| Wed 21 | 0 | 0.0 | 118 ms | 0 |
| Wed 23 | 0 | 0.0 | 421 ms | 0 |
| Thu 02 | 0 | 0.0 | 163 ms | 0 |
| Thu 04 | 0 | 0.0 | 484 ms | 0 |
| Thu 06 | 0 | 0.0 | 166 ms | 0 |
| Thu 08 | 0 | 0.0 | 474 ms | 0 |
| Thu 10 | 0 | 0.0 | 306 ms | 0 |
| Thu 12 | 0 | 0.0 | 326 ms | 0 |
| Thu 14 | 0 | 0.0 | 103 ms | 0 |
| Thu 16 | 0 | 0.0 | 198 ms | 0 |
| Thu 18 | 0 | 0.0 | 319 ms | 0 |
| Thu 20 | 0 | 0.0 | 294 ms | 0 |
| Thu 21 | 0 | 0.0 | 164 ms | 0 |
| Thu 23 | 0 | 0.0 | 300 ms | 0 |
| Fri 01 | 0 | 0.0 | 134 ms | 0 |
| Fri 03 | 0 | 0.0 | 246 ms | 0 |
| Fri 05 | 0 | 0.0 | 74 ms | 0 |
| Fri 07 | 0 | 0.0 | 226 ms | 0 |
| Fri 09 | 0 | 0.0 | 122 ms | 0 |
| Fri 11 | 0 | 0.0 | 165 ms | 0 |
| Fri 14 | 0 | 0.0 | 93 ms | 0 |
| Fri 16 | 0 | 0.0 | 182 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 Pylon 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 Pylon goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Pylon alerts to Slack, Discord or a webhook — free.
We track Pylon (getpylon.com) as part of the Productivity group. Design solar and battery systems in under two minutes. Hi-res imagery included, with no monthly fees. Join 3,500+ solar businesses.
Pylon publishes an official status page at status.getpylon.com; 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: 201 ms average, 74–359 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Pylon incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
201 ms on average over the last 24 hours (74–359 ms).
Yes, at https://status.getpylon.com.
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 Pylon here at once, the problem is on Pylon'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 Pylon. 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.