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 39 min ago. Last stored result reached it in 438 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 20 | 0 | 0.0 | 447 ms | 0 |
| Mon 22 | 0 | 0.0 | 369 ms | 0 |
| Tue 00 | 0 | 0.0 | 468 ms | 0 |
| Tue 02 | 0 | 0.0 | 455 ms | 0 |
| Tue 04 | 0 | 0.0 | 418 ms | 0 |
| Tue 06 | 0 | 0.0 | 499 ms | 0 |
| Tue 08 | 0 | 0.0 | 455 ms | 0 |
| Tue 10 | 0 | 0.0 | 412 ms | 0 |
| Tue 13 | 0 | 0.0 | 333 ms | 0 |
| Tue 15 | 0 | 0.0 | 333 ms | 0 |
| Tue 17 | 0 | 0.0 | 552 ms | 0 |
| Tue 19 | 0 | 0.0 | 383 ms | 0 |
| Tue 22 | 0 | 0.0 | 466 ms | 0 |
| Wed 00 | 0 | 0.0 | 430 ms | 0 |
| Wed 02 | 0 | 0.0 | 477 ms | 0 |
| Wed 04 | 0 | 0.0 | 453 ms | 0 |
| Wed 07 | 0 | 0.0 | 435 ms | 0 |
| Wed 09 | 0 | 0.0 | 457 ms | 0 |
| Wed 11 | 0 | 0.0 | 561 ms | 0 |
| Wed 13 | 0 | 0.0 | 452 ms | 0 |
| Wed 15 | 0 | 0.0 | 301 ms | 0 |
| Wed 17 | 0 | 0.0 | 448 ms | 0 |
| Wed 20 | 0 | 0.0 | 291 ms | 0 |
| Wed 22 | 0 | 0.0 | 454 ms | 0 |
| Thu 00 | 0 | 0.0 | 688 ms | 0 |
| Thu 02 | 0 | 0.0 | 393 ms | 0 |
| Thu 04 | 0 | 0.0 | 587 ms | 0 |
| Thu 06 | 0 | 0.0 | 458 ms | 0 |
| Thu 08 | 0 | 0.0 | 551 ms | 0 |
| Thu 10 | 0 | 0.0 | 450 ms | 0 |
| Thu 12 | 0 | 0.0 | 451 ms | 0 |
| Thu 15 | 0 | 0.0 | 359 ms | 0 |
| Thu 17 | 0 | 0.0 | 437 ms | 0 |
| Thu 19 | 0 | 0.0 | 488 ms | 0 |
| Thu 21 | 0 | 0.0 | 431 ms | 0 |
| Thu 23 | 0 | 0.0 | 526 ms | 0 |
| Fri 01 | 0 | 0.0 | 427 ms | 0 |
| Fri 03 | 0 | 0.0 | 367 ms | 0 |
| Fri 05 | 0 | 0.0 | 477 ms | 0 |
| Fri 07 | 0 | 0.0 | 469 ms | 0 |
| Fri 09 | 0 | 0.0 | 427 ms | 0 |
| Fri 11 | 0 | 0.0 | 490 ms | 0 |
| Fri 13 | 0 | 0.0 | 452 ms | 0 |
| Fri 15 | 0 | 0.0 | 363 ms | 0 |
| Fri 17 | 0 | 0.0 | 522 ms | 0 |
| Fri 19 | 0 | 0.0 | 460 ms | 0 |
| Fri 21 | 0 | 0.0 | 483 ms | 0 |
| Fri 23 | 0 | 0.0 | 438 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 Stripo 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 Stripo goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Stripo alerts to Slack, Discord or a webhook — free.
Stripo is listed in our Productivity category and checked at stripo.email. Stripo — free email template builder. Create professional and responsive emails fast with no HTML skills. Use it to automate email production.
Stripo publishes an official status page at status.stripo.email; when we can read it, its incident level is folded into the status shown here.
Typical issues 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: 448 ms average, 267–578 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Stripo incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
448 ms on average over the last 24 hours (267–578 ms).
Yes, at https://status.stripo.email.
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 Stripo here at once, the problem is on Stripo'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 Stripo. 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.