BetterHelp outages and problems
In the past 24 hours, 407 user reports came in for BetterHelp. Counting only the 15-minute windows with a spike big enough to count as an outage, that comes to 91.67% uptime for the day.
The most recent spike big enough to count as an outage was under 15 minutes ago. The busiest 15-minute window of the day had 74 reports, about 2 hours ago.
-
Outage
Ongoing, started 2 h agoRunning for 2 h 15 min74peak reports
BetterHelp in October 2026
- Problem reports in October (since 28 October)
- 405
Monthly report for October 2026
What went wrong
What people said was wrong in recent problem reports for BetterHelp.
Share of 203 recent reports that said what was wrong.
Where BetterHelp problem reports come from
The map shows where recent problem reports for BetterHelp came from in the UK. Big cities always send the most, so dots in many places point to a widespread problem, and one area far ahead of the rest can mean a regional one.
- Outage now
- Problems now
- Normal
Map outlines: Natural Earth.
BetterHelp problem spikes, last 30 days
Since 28 October, BetterHelp had 1 outage spike.
-
Outage
Thu 29 Oct, 16:02–18:17Still going80peak reports
A spike is a sharp rise in problem reports from users, kept exactly as this page showed it at the time. This history starts on 28 October 2026. Monthly reports for all services
How to fix BetterHelp not working
When BetterHelp itself is having trouble, these steps won't bring it back, but they will rule out anything on your side:
Your browser tries to reach betterhelp.com over your own connection, right now. Nothing is sent to us or stored.
Reload and restart
Reload the page (Ctrl+F5, or Cmd+Shift+R on a Mac), or fully close the app and open it again.
Try another connection
Switch between Wi-Fi and mobile data. If it works on one and not the other, the problem is your network, not BetterHelp.
Update the app
Install the latest version from the App Store or Google Play. Old versions can stop connecting after a server-side change.
Problems at the same time as BetterHelp
Since 28 October, BetterHelp's only spike in problem reports overlapped a spike at another service.
When several services get problem reports at once, something they share, such as a cloud host or a network, can be the real cause. Matching times alone do not prove it.
During the latest spike
BetterHelp: Thu 29 Oct, since 16:02
- ESPN Fantasy Football, outage,27 Oct 19:50 to 18:17
- Archive of Our Own, outage,07:32 to 18:17
- Capital One, outage,13:47 to 18:17
- Starbucks, outage,13:47 to 17:02, 17:32 to 17:47
- Uber, outage,14:02 to 16:32
- USPS, outage,14:47 to 18:17
- Escape from Tarkov, outage,15:02 to 16:32, 17:02 to 17:17
- LexisNexis, outage,15:02 to 16:17
71 more services. Red dot: outage. Amber dot: elevated reports.
A spike is a sharp rise in problem reports from users, as the live pages showed it. Times are Central European time.
BetterHelp IP address, servers and network
- IPv4 addresses
- 18.244.18.41
Show all 4
- 18.244.18.5
- 18.244.18.69
- 18.244.18.98
- IPv6
- Not offered
- Network
- AS16509 · Amazon.com, Inc., registered in the United States
- Served through
- Amazon CloudFront · our check was answered by its Frankfurt (FRA) data centre
- DNS hosted by
- Amazon Route 53
- HTTPS certificate
- Issued by Amazon, valid until 12 Mar 2027 (133 days)
- HTTP/3
- Supported
- Our check
- Answered in 1,757 ms
Checked from our server in Frankfurt, Germany, 1 h ago, for www.betterhelp.com. A service behind a CDN answers from many data centres, usually the one nearest to you, so these addresses are where its traffic enters, not where its own servers stand. Visitors elsewhere may see different addresses.
Checked from 11 places around the world
All 11 locations got an answer from betterhelp.com. Fastest from Los Angeles (279 ms), slowest from Singapore (650 ms). Every location connected through Amazon.com, Inc. (AS16509), using 2 different addresses.
| Location | Result | Time | Address reached |
|---|---|---|---|
| FrankfurtGermany | Up · HTTP 202 | 284 ms | 166.117.115.19 |
| ViennaAustria | Up · HTTP 301 | 329 ms | 166.117.115.19 |
| MilanItaly | Up · HTTP 202 | 318 ms | 166.117.115.19 |
| ParisFrance | Up · HTTP 301 | 289 ms | 166.117.210.39 |
| AmsterdamNetherlands | Up · HTTP 202 | 281 ms | 166.117.210.39 |
| MadridSpain | Up · HTTP 202 | 318 ms | 166.117.115.19 |
| WarsawPoland | Up · HTTP 301 | 366 ms | 166.117.210.39 |
| Los AngelesUSA | Up · HTTP 202 | 279 ms | 166.117.210.39 |
| São PauloBrazil | Up · HTTP 202 | 352 ms | 166.117.115.19 |
| SingaporeSingapore | Up · HTTP 202 | 650 ms | 166.117.210.39 |
| TokyoJapan | Up · HTTP 301 | 516 ms | 166.117.210.39 |
Checked with check-host.net from its servers in these cities 1 h ago, for betterhelp.com. Time is how long each server took to load the page.
Put the BetterHelp status badge on your site
Paste one of these into a web page, a blog post or a README. The badge shows the same status as this page, based on user problem reports. Browsers can keep a copy for up to 4 hours. It links back here.
<a href="https://isitdownrightnow.app/services/betterhelp/"><img src="https://isitdownrightnow.app/badge/betterhelp.svg" alt="BetterHelp status" height="20"></a>[](https://isitdownrightnow.app/services/betterhelp/)The badge is a plain image: no scripts, no cookies. People who see it on your page load it from our server.
How we track BetterHelp
The status on this page comes from user-submitted problem reports for BetterHelp, counted in 15-minute windows over the last 24 hours. Each window is compared with the normal level for BetterHelp, so a few complaints on a quiet day don't trigger anything, but a sudden jump well above normal does.
When reports climb well above normal, the status here changes to partial outage or major outage and the chart moves with it. BetterHelp doesn't publish a public status page that we know of, so user reports are often the quickest sign that something is wrong on their side.