User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
scratchpay.com · Cloud & developer
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 272 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 12 | 0 | 0.0 | 128 ms | 0 |
| Mon 14 | 0 | 0.0 | 251 ms | 0 |
| Mon 16 | 0 | 0.0 | 81 ms | 0 |
| Mon 18 | 0 | 0.0 | 142 ms | 0 |
| Mon 20 | 0 | 0.0 | 160 ms | 0 |
| Mon 22 | 0 | 0.0 | 159 ms | 0 |
| Tue 01 | 0 | 0.0 | 113 ms | 0 |
| Tue 03 | 0 | 0.0 | 87 ms | 0 |
| Tue 05 | 0 | 0.0 | 191 ms | 0 |
| Tue 07 | 0 | 0.0 | 226 ms | 0 |
| Tue 09 | 0 | 0.0 | 307 ms | 0 |
| Tue 11 | 0 | 0.0 | 161 ms | 0 |
| Tue 13 | 0 | 0.0 | 676 ms | 0 |
| Tue 16 | 0 | 0.0 | 197 ms | 0 |
| Tue 18 | 0 | 0.0 | 191 ms | 0 |
| Tue 20 | 0 | 0.0 | 226 ms | 0 |
| Tue 22 | 0 | 0.0 | 165 ms | 0 |
| Wed 01 | 0 | 0.0 | 116 ms | 0 |
| Wed 03 | 0 | 0.0 | 83 ms | 0 |
| Wed 05 | 0 | 0.0 | 239 ms | 0 |
| Wed 07 | 0 | 0.0 | 238 ms | 0 |
| Wed 10 | 0 | 0.0 | 234 ms | 0 |
| Wed 12 | 0 | 0.0 | 145 ms | 0 |
| Wed 14 | 0 | 0.0 | 140 ms | 0 |
| Wed 16 | 0 | 0.0 | 375 ms | 0 |
| Wed 18 | 0 | 0.0 | 182 ms | 0 |
| Wed 20 | 0 | 0.0 | 176 ms | 0 |
| Wed 23 | 0 | 0.0 | 246 ms | 0 |
| Thu 01 | 0 | 0.0 | 259 ms | 0 |
| Thu 03 | 0 | 0.0 | 126 ms | 0 |
| Thu 05 | 0 | 0.0 | 127 ms | 0 |
| Thu 07 | 0 | 0.0 | 136 ms | 0 |
| Thu 09 | 0 | 0.0 | 261 ms | 0 |
| Thu 11 | 0 | 0.0 | 240 ms | 0 |
| Thu 13 | 0 | 0.0 | 231 ms | 0 |
| Thu 15 | 0 | 0.0 | 297 ms | 0 |
| Thu 17 | 0 | 0.0 | 253 ms | 0 |
| Thu 19 | 0 | 0.0 | 219 ms | 0 |
| Thu 21 | 0 | 0.0 | 130 ms | 0 |
| Fri 00 | 0 | 0.0 | 339 ms | 0 |
| Fri 02 | 0 | 0.0 | 86 ms | 0 |
| Fri 04 | 0 | 0.0 | 129 ms | 0 |
| Fri 06 | 0 | 0.0 | 230 ms | 0 |
| Fri 08 | 0 | 0.0 | 285 ms | 0 |
| Fri 10 | 0 | 0.0 | 266 ms | 0 |
| Fri 11 | 0 | 0.0 | 152 ms | 0 |
| Fri 13 | 0 | 0.0 | 213 ms | 0 |
| Fri 15 | 0 | 0.0 | 272 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 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Scratchpay 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 Scratchpay goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Scratchpay alerts to Slack, Discord or a webhook — free.
Scratchpay, at scratchpay.com, is one of the Cloud & developer services we monitor. Scratchpay offers 12–24 month plans for amounts between $200–$10,000, with no hidden fees. See your options instantly—without affecting your credit score.
Scratchpay publishes an official status page at status.scratchpay.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
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: 215 ms average, 86–339 ms range across 12 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Scratchpay incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
215 ms on average over the last 24 hours (86–339 ms).
Yes, at https://status.scratchpay.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report Scratchpay here at once, the problem is on Scratchpay'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 Scratchpay. 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.