User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Social
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 4 min ago. Last stored result reached it in 258 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 177 ms | 0 |
| Nov 7 | 0 | 0.0 | 182 ms | 0 |
| Nov 7 | 0 | 0.0 | 310 ms | 0 |
| Nov 7 | 0 | 0.0 | 199 ms | 0 |
| Nov 7 | 0 | 0.0 | 365 ms | 0 |
| Nov 8 | 0 | 0.0 | 228 ms | 0 |
| Nov 8 | 0 | 0.0 | 189 ms | 0 |
| Nov 8 | 0 | 0.0 | 242 ms | 0 |
| Nov 8 | 0 | 0.0 | 184 ms | 0 |
| Nov 9 | 0 | 0.0 | 228 ms | 0 |
| Nov 9 | 0 | 0.0 | 192 ms | 0 |
| Nov 9 | 0 | 0.0 | 280 ms | 0 |
| Nov 9 | 0 | 0.0 | 233 ms | 0 |
| Nov 10 | 0 | 0.0 | 255 ms | 0 |
| Nov 10 | 0 | 0.0 | 290 ms | 0 |
| Nov 10 | 0 | 0.0 | 180 ms | 0 |
| Nov 10 | 0 | 0.0 | 414 ms | 0 |
| Nov 11 | 0 | 0.0 | 242 ms | 0 |
| Nov 11 | 0 | 0.0 | 246 ms | 0 |
| Nov 11 | 0 | 0.0 | 300 ms | 0 |
| Nov 11 | 0 | 0.0 | 325 ms | 0 |
| Nov 12 | 0 | 0.0 | 346 ms | 0 |
| Nov 12 | 0 | 0.0 | 243 ms | 0 |
| Nov 12 | 0 | 0.0 | 295 ms | 0 |
| Nov 12 | 0 | 0.0 | 330 ms | 0 |
| Nov 13 | 0 | 0.0 | 283 ms | 0 |
| Nov 13 | 0 | 0.0 | 272 ms | 0 |
| Nov 13 | 0 | 0.0 | 269 ms | 0 |
| Nov 13 | 0 | 0.0 | 245 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 Quip 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 Quip goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Quip alerts to Slack, Discord or a webhook — free.
Quip, at quip.com, is one of the Social services we monitor. Quip is real-time collaborative documents, spreadsheets, and chat embedded inside Salesforce to transform any business process.
Quip publishes an official status page at status.quip.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with social services: feeds not loading, posts or messages not sending, and login loops.
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: 271 ms average, 178–391 ms range across 19 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Quip incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
271 ms on average over the last 24 hours (178–391 ms).
Yes, at https://status.quip.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For social services, watch for feeds not loading, posts or messages not sending, and login loops. If many people report Quip here at once, the problem is on Quip'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 Quip. 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.