User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Money
Is Churnkey down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → churnkey.co—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
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.
Live outage map
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.
What's broken
Recent reports
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.
Our checks
Reaching it
Last checked 1 hr ago. Last stored result reached it in 83 ms.
Official status
All clear
All Systems Operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 22 | 0 | 0.0 | 83 ms | 0 |
| Tue 00 | 0 | 0.0 | 90 ms | 0 |
| Tue 02 | 0 | 0.0 | 225 ms | 0 |
| Tue 04 | 0 | 0.0 | 50 ms | 0 |
| Tue 06 | 0 | 0.0 | 260 ms | 0 |
| Tue 08 | 0 | 0.0 | 209 ms | 0 |
| Tue 10 | 0 | 0.0 | 84 ms | 0 |
| Tue 12 | 0 | 0.0 | 197 ms | 0 |
| Tue 15 | 0 | 0.0 | 136 ms | 0 |
| Tue 17 | 0 | 0.0 | 223 ms | 0 |
| Tue 19 | 0 | 0.0 | 41 ms | 0 |
| Tue 21 | 0 | 0.0 | 213 ms | 0 |
| Wed 00 | 0 | 0.0 | 218 ms | 0 |
| Wed 02 | 0 | 0.0 | 215 ms | 0 |
| Wed 04 | 0 | 0.0 | 149 ms | 0 |
| Wed 06 | 0 | 0.0 | 161 ms | 0 |
| Wed 09 | 0 | 0.0 | 64 ms | 0 |
| Wed 11 | 0 | 0.0 | 132 ms | 0 |
| Wed 13 | 0 | 0.0 | 1038 ms | 0 |
| Wed 15 | 0 | 0.0 | 1048 ms | 0 |
| Wed 17 | 0 | 0.0 | 229 ms | 0 |
| Wed 19 | 0 | 0.0 | 37 ms | 0 |
| Wed 22 | 0 | 0.0 | 163 ms | 0 |
| Thu 00 | 0 | 0.0 | 78 ms | 0 |
| Thu 02 | 0 | 0.0 | 319 ms | 0 |
| Thu 04 | 0 | 0.0 | 104 ms | 0 |
| Thu 06 | 0 | 0.0 | 262 ms | 0 |
| Thu 08 | 0 | 0.0 | 189 ms | 0 |
| Thu 10 | 0 | 0.0 | 85 ms | 0 |
| Thu 12 | 0 | 0.0 | 98 ms | 0 |
| Thu 14 | 0 | 0.0 | 128 ms | 0 |
| Thu 16 | 0 | 0.0 | 158 ms | 0 |
| Thu 18 | 0 | 0.0 | 70 ms | 0 |
| Thu 20 | 0 | 0.0 | 116 ms | 0 |
| Thu 22 | 0 | 0.0 | 90 ms | 0 |
| Fri 01 | 0 | 0.0 | 119 ms | 0 |
| Fri 03 | 0 | 0.0 | 340 ms | 0 |
| Fri 05 | 0 | 0.0 | 153 ms | 0 |
| Fri 07 | 0 | 0.0 | 135 ms | 0 |
| Fri 09 | 0 | 0.0 | 145 ms | 0 |
| Fri 10 | 0 | 0.0 | 196 ms | 0 |
| Fri 12 | 0 | 0.0 | 134 ms | 0 |
| Fri 14 | 0 | 0.0 | 218 ms | 0 |
| Fri 16 | 0 | 0.0 | 154 ms | 0 |
| Fri 17 | 0 | 0.0 | 63 ms | 0 |
| Fri 18 | 0 | 0.0 | 249 ms | 0 |
| Fri 19 | 0 | 0.0 | 70 ms | 0 |
| Fri 20 | 0 | 0.0 | 83 ms | 0 |
Reliability
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.
Embed this status: free live Churnkey badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for Churnkey yet. Outages of 10 minutes or more get their own page here.
Having trouble with Churnkey?
One report per service every 10 minutes from this network. No account.
Follow Churnkey
Get an email when Churnkey goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Churnkey alerts to Slack, Discord or a webhook — free.
About Churnkey
We track Churnkey (churnkey.co) as part of the Money group. Churnkey is customer retention and churn management software built specifically for Stripe. Connect your account and start fixing cancellations and failed payments in as little as 15 minutes.
Churnkey publishes an official status page at status.churnkey.co; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with money services: login and two-factor problems, payments or transfers failing, and app errors.
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: 151 ms average, 63–340 ms range across 15 successful checks.
Questions
Is Churnkey down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Churnkey last down?
We have not recorded a public Churnkey incident since monitoring began 8 days ago.
What is Churnkey's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Churnkey respond?
151 ms on average over the last 24 hours (63–340 ms).
Does Churnkey have an official status page?
Yes, at https://status.churnkey.co.
Churnkey not working for me but the status is fine. What now?
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For money services, watch for login and two-factor problems, payments or transfers failing, and app errors. If many people report Churnkey here at once, the problem is on Churnkey'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 Churnkey. 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.