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 47 min ago. Last stored result reached it in 307 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 20 | 0 | 0.0 | 668 ms | 0 |
| Mon 22 | 0 | 0.0 | 510 ms | 0 |
| Tue 00 | 0 | 0.0 | 485 ms | 0 |
| Tue 02 | 0 | 0.0 | 285 ms | 0 |
| Tue 04 | 0 | 0.0 | 619 ms | 0 |
| Tue 06 | 0 | 0.0 | — | 2 |
| Tue 08 | 0 | 0.0 | 638 ms | 0 |
| Tue 10 | 0 | 0.0 | 663 ms | 0 |
| Tue 12 | 0 | 0.0 | 656 ms | 0 |
| Tue 15 | 0 | 0.0 | 696 ms | 0 |
| Tue 17 | 0 | 0.0 | 764 ms | 0 |
| Tue 19 | 0 | 0.0 | 582 ms | 0 |
| Tue 21 | 0 | 0.0 | 583 ms | 0 |
| Wed 00 | 0 | 0.0 | 488 ms | 0 |
| Wed 02 | 0 | 0.0 | 321 ms | 0 |
| Wed 04 | 0 | 0.0 | 404 ms | 0 |
| Wed 06 | 0 | 0.0 | 571 ms | 0 |
| Wed 07 | 0 | 0.0 | 605 ms | 0 |
| Wed 08 | 0 | 0.0 | 599 ms | 0 |
| Wed 10 | 0 | 0.0 | 596 ms | 0 |
| Wed 12 | 0 | 0.0 | 654 ms | 0 |
| Wed 14 | 0 | 0.0 | 593 ms | 0 |
| Wed 17 | 0 | 0.0 | 324 ms | 0 |
| Wed 19 | 0 | 0.0 | 381 ms | 0 |
| Wed 21 | 0 | 0.0 | 207 ms | 0 |
| Wed 23 | 0 | 0.0 | 648 ms | 0 |
| Thu 01 | 0 | 0.0 | 612 ms | 0 |
| Thu 03 | 0 | 0.0 | 631 ms | 0 |
| Thu 05 | 0 | 0.0 | 663 ms | 0 |
| Thu 07 | 0 | 0.0 | 274 ms | 0 |
| Thu 09 | 0 | 0.0 | 330 ms | 0 |
| Thu 12 | 0 | 0.0 | 630 ms | 0 |
| Thu 14 | 0 | 0.0 | 658 ms | 0 |
| Thu 16 | 0 | 0.0 | 531 ms | 0 |
| Thu 18 | 0 | 0.0 | 506 ms | 0 |
| Thu 20 | 0 | 0.0 | 630 ms | 0 |
| Thu 22 | 0 | 0.0 | 520 ms | 0 |
| Fri 00 | 0 | 0.0 | 768 ms | 0 |
| Fri 02 | 0 | 0.0 | 642 ms | 0 |
| Fri 04 | 0 | 0.0 | 703 ms | 0 |
| Fri 06 | 0 | 0.0 | 668 ms | 0 |
| Fri 08 | 0 | 0.0 | 466 ms | 0 |
| Fri 10 | 0 | 0.0 | 613 ms | 0 |
| Fri 11 | 0 | 0.0 | 317 ms | 0 |
| Fri 12 | 0 | 0.0 | 606 ms | 0 |
| Fri 14 | 0 | 0.0 | 600 ms | 0 |
| Fri 16 | 0 | 0.0 | 499 ms | 0 |
| Fri 18 | 0 | 0.0 | 307 ms | 0 |
97.33% 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.
One report per service every 10 minutes from this network. No account.
Get an email when Cloudfam goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Cloudfam alerts to Slack, Discord or a webhook — free.
Cloudfam is listed in our Money category and checked at cloudfam.io. Monetize digital files with CloudFam. Standard Tier 1 rates from $18+ CPM up to $25.00 Elite CPM on Pay-Per-Download, AdFlow impression earnings, 85% revenue split on direct file sales, video streaming, 300GB free storage, and daily payouts from $5.00.
Cloudfam publishes an official status page at status.cloudfam.io; 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: 97.33% over 8 days of checks. We logged 1 public incident since monitoring began 8 days ago.
Response time over the last 24 hours: 565 ms average, 307–768 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
The most recent public incident we recorded started 2026-11-10 and lasted 2 h 6 min. 1 incident since monitoring began 8 days ago.
From our own checks: 97.33% over 8 days of checks.
565 ms on average over the last 24 hours (307–768 ms).
Yes, at https://status.cloudfam.io.
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 Cloudfam here at once, the problem is on Cloudfam'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 Cloudfam. 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.