User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Money
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 402 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 380 ms | 0 |
| Nov 7 | 0 | 0.0 | 481 ms | 0 |
| Nov 7 | 0 | 0.0 | 3037 ms | 0 |
| Nov 7 | 0 | 0.0 | 474 ms | 0 |
| Nov 7 | 0 | 0.0 | 541 ms | 0 |
| Nov 8 | 0 | 0.0 | 490 ms | 0 |
| Nov 8 | 0 | 0.0 | 485 ms | 0 |
| Nov 8 | 0 | 0.0 | 369 ms | 0 |
| Nov 8 | 0 | 0.0 | 354 ms | 0 |
| Nov 9 | 0 | 0.0 | 470 ms | 0 |
| Nov 9 | 0 | 0.0 | 495 ms | 0 |
| Nov 9 | 0 | 0.0 | 325 ms | 0 |
| Nov 9 | 0 | 0.0 | 490 ms | 0 |
| Nov 10 | 0 | 0.0 | 459 ms | 0 |
| Nov 10 | 0 | 0.0 | 3092 ms | 0 |
| Nov 10 | 0 | 0.0 | 426 ms | 0 |
| Nov 10 | 0 | 0.0 | 444 ms | 0 |
| Nov 11 | 0 | 0.0 | 409 ms | 0 |
| Nov 11 | 0 | 0.0 | 506 ms | 0 |
| Nov 11 | 0 | 0.0 | 356 ms | 0 |
| Nov 11 | 0 | 0.0 | 420 ms | 0 |
| Nov 12 | 0 | 0.0 | 459 ms | 0 |
| Nov 12 | 0 | 0.0 | 463 ms | 0 |
| Nov 12 | 0 | 0.0 | 451 ms | 0 |
| Nov 12 | 0 | 0.0 | 398 ms | 0 |
| Nov 13 | 0 | 0.0 | 472 ms | 0 |
| Nov 13 | 0 | 0.0 | 501 ms | 0 |
| Nov 13 | 0 | 0.0 | 482 ms | 0 |
| Nov 13 | 0 | 0.0 | 427 ms | 0 |
| Nov 14 | 0 | 0.0 | 517 ms | 0 |
| Nov 14 | 0 | 0.0 | 420 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 Credit Key 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 Credit Key goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Credit Key alerts to Slack, Discord or a webhook — free.
Credit Key is listed in our Money category and checked at creditkey.com. Offer business customers net terms and pay-over-time options with Credit Key, online, in-store, and through phone and field sales.
Credit Key publishes an official status page at status.creditkey.com; 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 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 783 ms average, 278–5441 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 Credit Key incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
783 ms on average over the last 24 hours (278–5441 ms).
Yes, at https://status.creditkey.com.
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 Credit Key here at once, the problem is on Credit Key'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 Credit Key. 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.