User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Productivity
crisistextline.org · 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 432 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 19 | 0 | 0.0 | 365 ms | 0 |
| Tue 21 | 0 | 0.0 | 365 ms | 0 |
| Wed 00 | 0 | 0.0 | 305 ms | 0 |
| Wed 02 | 0 | 0.0 | 496 ms | 0 |
| Wed 04 | 0 | 0.0 | 428 ms | 0 |
| Wed 06 | 0 | 0.0 | 401 ms | 0 |
| Wed 08 | 0 | 0.0 | 405 ms | 0 |
| Wed 11 | 0 | 0.0 | 248 ms | 0 |
| Wed 13 | 0 | 0.0 | 211 ms | 0 |
| Wed 15 | 0 | 0.0 | 342 ms | 0 |
| Wed 17 | 0 | 0.0 | 342 ms | 0 |
| Wed 19 | 0 | 0.0 | 347 ms | 0 |
| Wed 21 | 0 | 0.0 | 275 ms | 0 |
| Wed 22 | 0 | 0.0 | 73 ms | 0 |
| Thu 00 | 0 | 0.0 | 361 ms | 0 |
| Thu 02 | 0 | 0.0 | 386 ms | 0 |
| Thu 04 | 0 | 0.0 | 388 ms | 0 |
| Thu 06 | 0 | 0.0 | 306 ms | 0 |
| Thu 08 | 0 | 0.0 | 360 ms | 0 |
| Thu 10 | 0 | 0.0 | 398 ms | 0 |
| Thu 12 | 0 | 0.0 | 268 ms | 0 |
| Thu 14 | 0 | 0.0 | 344 ms | 0 |
| Thu 16 | 0 | 0.0 | 424 ms | 0 |
| Thu 18 | 0 | 0.0 | 291 ms | 0 |
| Thu 20 | 0 | 0.0 | 352 ms | 0 |
| Thu 22 | 0 | 0.0 | 473 ms | 0 |
| Fri 00 | 0 | 0.0 | 400 ms | 0 |
| Fri 02 | 0 | 0.0 | 452 ms | 0 |
| Fri 04 | 0 | 0.0 | 243 ms | 0 |
| Fri 06 | 0 | 0.0 | 463 ms | 0 |
| Fri 08 | 0 | 0.0 | 441 ms | 0 |
| Fri 10 | 0 | 0.0 | 410 ms | 0 |
| Fri 12 | 0 | 0.0 | 495 ms | 0 |
| Fri 14 | 0 | 0.0 | 399 ms | 0 |
| Fri 17 | 0 | 0.0 | 432 ms | 0 |
| Fri 19 | 0 | 0.0 | 417 ms | 0 |
| Fri 21 | 0 | 0.0 | 395 ms | 0 |
| Fri 22 | 0 | 0.0 | 433 ms | 0 |
| Sat 00 | 0 | 0.0 | 360 ms | 0 |
| Sat 02 | 0 | 0.0 | 443 ms | 0 |
| Sat 03 | 0 | 0.0 | 240 ms | 0 |
| Sat 05 | 0 | 0.0 | 354 ms | 0 |
| Sat 07 | 0 | 0.0 | 275 ms | 0 |
| Sat 09 | 0 | 0.0 | 234 ms | 0 |
| Sat 11 | 0 | 0.0 | 397 ms | 0 |
| Sat 12 | 0 | 0.0 | 423 ms | 0 |
| Sat 14 | 0 | 0.0 | 233 ms | 0 |
| Sat 16 | 0 | 0.0 | 432 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 Crisis Text Line 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 Crisis Text Line goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send confirmed down and recovery alerts to Slack, Discord or a webhook — free. Early warnings are part of Owner Alerts.
Crisis Text Line, at crisistextline.org, is one of the Productivity services we monitor. Text HOME to 741741 for free, 24/7 confidential crisis support in English & Spanish. Suicide hotline for anxiety, depression, bullying.
Crisis Text Line publishes an official status page at status.crisistextline.org; 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 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 361 ms average, 233–455 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Crisis Text Line incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
361 ms on average over the last 24 hours (233–455 ms).
Yes, at https://status.crisistextline.org.
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 Crisis Text Line here at once, the problem is on Crisis Text Line'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 Crisis Text Line. 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.