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 6 min ago. Last stored result reached it in 158 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 17 | 0 | 0.0 | 217 ms | 0 |
| Tue 19 | 0 | 0.0 | 240 ms | 0 |
| Tue 21 | 0 | 0.0 | 171 ms | 0 |
| Wed 00 | 0 | 0.0 | 410 ms | 0 |
| Wed 02 | 0 | 0.0 | 196 ms | 0 |
| Wed 04 | 0 | 0.0 | 114 ms | 0 |
| Wed 06 | 0 | 0.0 | 224 ms | 0 |
| Wed 08 | 0 | 0.0 | 228 ms | 0 |
| Wed 11 | 0 | 0.0 | 188 ms | 0 |
| Wed 13 | 0 | 0.0 | 264 ms | 0 |
| Wed 15 | 0 | 0.0 | 265 ms | 0 |
| Wed 17 | 0 | 0.0 | 101 ms | 0 |
| Wed 19 | 0 | 0.0 | 95 ms | 0 |
| Wed 21 | 0 | 0.0 | 107 ms | 0 |
| Thu 00 | 0 | 0.0 | 252 ms | 0 |
| Thu 02 | 0 | 0.0 | 150 ms | 0 |
| Thu 04 | 0 | 0.0 | 108 ms | 0 |
| Thu 06 | 0 | 0.0 | 210 ms | 0 |
| Thu 08 | 0 | 0.0 | 280 ms | 0 |
| Thu 10 | 0 | 0.0 | 189 ms | 0 |
| Thu 12 | 0 | 0.0 | 130 ms | 0 |
| Thu 14 | 0 | 0.0 | 199 ms | 0 |
| Thu 16 | 0 | 0.0 | 329 ms | 0 |
| Thu 19 | 0 | 0.0 | 213 ms | 0 |
| Thu 21 | 0 | 0.0 | 188 ms | 0 |
| Thu 22 | 0 | 0.0 | 116 ms | 0 |
| Fri 01 | 0 | 0.0 | 82 ms | 0 |
| Fri 03 | 0 | 0.0 | 256 ms | 0 |
| Fri 05 | 0 | 0.0 | 107 ms | 0 |
| Fri 07 | 0 | 0.0 | 224 ms | 0 |
| Fri 09 | 0 | 0.0 | 274 ms | 0 |
| Fri 11 | 0 | 0.0 | 180 ms | 0 |
| Fri 12 | 0 | 0.0 | 72 ms | 0 |
| Fri 14 | 0 | 0.0 | 90 ms | 0 |
| Fri 16 | 0 | 0.0 | 108 ms | 0 |
| Fri 18 | 0 | 0.0 | 244 ms | 0 |
| Fri 20 | 0 | 0.0 | 111 ms | 0 |
| Fri 21 | 0 | 0.0 | 111 ms | 0 |
| Fri 23 | 0 | 0.0 | 123 ms | 0 |
| Sat 01 | 0 | 0.0 | 136 ms | 0 |
| Sat 02 | 0 | 0.0 | 101 ms | 0 |
| Sat 04 | 0 | 0.0 | 93 ms | 0 |
| Sat 05 | 0 | 0.0 | 178 ms | 0 |
| Sat 06 | 0 | 0.0 | 189 ms | 0 |
| Sat 08 | 0 | 0.0 | 92 ms | 0 |
| Sat 10 | 0 | 0.0 | 250 ms | 0 |
| Sat 12 | 0 | 0.0 | 181 ms | 0 |
| Sat 15 | 0 | 0.0 | 158 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 Chili Piper 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 Chili Piper goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Chili Piper alerts to Slack, Discord or a webhook — free.
We track Chili Piper (chilipiper.com) as part of the Productivity group. Agents that recognize every visitor, answer their questions, route them to the right rep, book the meeting and follow up if they leave.
Chili Piper publishes an official status page at status.chilipiper.com; 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 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 151 ms average, 92–328 ms range across 17 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Chili Piper incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
151 ms on average over the last 24 hours (92–328 ms).
Yes, at https://status.chilipiper.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 Chili Piper here at once, the problem is on Chili Piper'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 Chili Piper. 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.