Is Cash App down?
Cash App is up.
Our last check reached cash.app and got a healthy response.
Cash App's own status page agrees — all systems operational. View it
The numbers
Availability and response time for Cash App over the last 24 hours.
Availability
100%
144 checks, none failed
Avg response
331 ms
Mean of every check
Slowest
973 ms
Worst single check
Incidents
0
Runs of failing checks
Downtime
None
Estimated from samples
Downtime is estimated from 10-minute samples, so figures are accurate to within one check interval.
Over time
Every check we ran, and how long each one took.
Availability
- All checks passed
- Some checks failed
- All checks failed
Response time
Where the time goes
"Is it down?" is usually really "it feels broken — what's wrong with it?" This is the answer: every millisecond of a request to cash.app, broken into the four phases it actually spends time in.
- DNS
- 3 ms1%
- TCP + TLS
- 15 ms5%
- Time to first byte
- 177 ms53%
- Download
- 137 ms41%
Resolving the hostname to an IP address.
Opening the connection and completing the TLS handshake.
Waiting for the server to start responding. Usually the server thinking.
Transferring the response body.
Averaged over the last 24 hours. The four phases add up to the total response time of 332 ms.
Incidents
Every time a check against cash.app failed in the last 30 days, grouped into incidents.
No incidents recorded for Cash App.
Every check we’ve run against Cash App has passed.
This page is a Checkly monitor.
Not a mockup of one. Everything above is produced by the monitor below, running every 10 minutes from N. Virginia and Frankfurt. It lives in a repo, gets code-reviewed, and deploys from CI — the same way you would monitor your own service.
That’s the whole product. Monitoring you can read, diff, and version.
How we check Cash App
A real request to the endpoint that matters, every 10 minutes — measured, not crowd-sourced.
What we actually do
- We send a real HTTP GET to
https://cash.appevery 10 minutes. - We run it from two datacenters: N. Virginia and Frankfurt.
- It passes if the endpoint answers with a status below 400 within 10 seconds. Slower than 3 seconds is “degraded”, not down.
- A single failed check isn’t a verdict. We retry it from the other region before recording anything, so a transient blip never shows here as an outage.
What a green check means
- Cash App answered a real request from both N. Virginia and Frankfurt — an actual measurement, not complaints counted from a crowd.
- We probe the endpoint that fails when Cash App fails, so a green check tracks the part you depend on, not a marketing page that stays up regardless.
- Checks run around the clock, every 10 minutes, on the same infrastructure Checkly customers monitor production with.
Frequently asked
No. Our most recent check reached https://cash.app and got a healthy response. We check every 10 minutes from N. Virginia and Frankfurt.
We run a real HTTP request against https://cash.app every 10 minutes from N. Virginia and Frankfurt, using Checkly's synthetic monitoring. A check passes when the endpoint returns a status below 400 within 10 seconds. We are not counting user reports — we are measuring the actual response.
We probe https://cash.app because it is the endpoint that best reflects whether Cash App is actually usable.
We check Cash App from N. Virginia and Frankfurt. If it answers us but not you, the problem is usually specific to your network, ISP, region, or account rather than Cash App itself.
Downdetector counts user reports — how many people are complaining. We run an actual synthetic check against the service and report what the wire says. Reports lag the outage and can be noisy; a probe either gets a response or it doesn't. For Cash App we also read its own status page, so if the service reports an incident while our probe still reaches it, we surface that too.