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 1 hr ago. Last stored result reached it in 651 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 21 | 0 | 0.0 | 824 ms | 0 |
| Mon 23 | 0 | 0.0 | 761 ms | 0 |
| Tue 01 | 0 | 0.0 | 515 ms | 0 |
| Tue 03 | 0 | 0.0 | 853 ms | 0 |
| Tue 05 | 0 | 0.0 | 800 ms | 0 |
| Tue 07 | 0 | 0.0 | 664 ms | 0 |
| Tue 10 | 0 | 0.0 | 797 ms | 0 |
| Tue 12 | 0 | 0.0 | 647 ms | 0 |
| Tue 14 | 0 | 0.0 | 791 ms | 0 |
| Tue 16 | 0 | 0.0 | 793 ms | 0 |
| Tue 18 | 0 | 0.0 | 398 ms | 0 |
| Tue 21 | 0 | 0.0 | 654 ms | 0 |
| Tue 23 | 0 | 0.0 | 646 ms | 0 |
| Wed 01 | 0 | 0.0 | 250 ms | 0 |
| Wed 03 | 0 | 0.0 | 603 ms | 0 |
| Wed 06 | 0 | 0.0 | 458 ms | 0 |
| Wed 08 | 0 | 0.0 | 619 ms | 0 |
| Wed 10 | 0 | 0.0 | 179 ms | 0 |
| Wed 12 | 0 | 0.0 | 625 ms | 0 |
| Wed 14 | 0 | 0.0 | 495 ms | 0 |
| Wed 16 | 0 | 0.0 | 819 ms | 0 |
| Wed 19 | 0 | 0.0 | 221 ms | 0 |
| Wed 21 | 0 | 0.0 | 771 ms | 0 |
| Wed 23 | 0 | 0.0 | 646 ms | 0 |
| Thu 01 | 0 | 0.0 | 671 ms | 0 |
| Thu 03 | 0 | 0.0 | 610 ms | 0 |
| Thu 05 | 0 | 0.0 | 492 ms | 0 |
| Thu 07 | 0 | 0.0 | 508 ms | 0 |
| Thu 09 | 0 | 0.0 | 470 ms | 0 |
| Thu 11 | 0 | 0.0 | 597 ms | 0 |
| Thu 13 | 0 | 0.0 | 621 ms | 0 |
| Thu 16 | 0 | 0.0 | 821 ms | 0 |
| Thu 18 | 0 | 0.0 | 411 ms | 0 |
| Thu 20 | 0 | 0.0 | 617 ms | 0 |
| Thu 22 | 0 | 0.0 | 670 ms | 0 |
| Fri 00 | 0 | 0.0 | 799 ms | 0 |
| Fri 02 | 0 | 0.0 | 605 ms | 0 |
| Fri 04 | 0 | 0.0 | 600 ms | 0 |
| Fri 06 | 0 | 0.0 | 585 ms | 0 |
| Fri 08 | 0 | 0.0 | 609 ms | 0 |
| Fri 10 | 0 | 0.0 | 247 ms | 0 |
| Fri 12 | 0 | 0.0 | 586 ms | 0 |
| Fri 14 | 0 | 0.0 | 612 ms | 0 |
| Fri 16 | 0 | 0.0 | 809 ms | 0 |
| Fri 17 | 0 | 0.0 | 840 ms | 0 |
| Fri 19 | 0 | 0.0 | 607 ms | 0 |
| Fri 20 | 0 | 0.0 | 679 ms | 0 |
| Fri 22 | 0 | 0.0 | 651 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 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Faucet Crypto 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 Faucet Crypto goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Faucet Crypto alerts to Slack, Discord or a webhook — free.
We track Faucet Crypto (faucetcrypto.com) as part of the Money group. Your faucet of choice! Earn free cryptocurrencies by completing simple tasks, such as visiting websites, filling surveys and downloading apps. Multiple cryptocurrencies available.
Faucet Crypto publishes an official status page at status.faucetcrypto.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 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 610 ms average, 247–840 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 Faucet Crypto incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
610 ms on average over the last 24 hours (247–840 ms).
Yes, at https://status.faucetcrypto.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 Faucet Crypto here at once, the problem is on Faucet Crypto'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 Faucet Crypto. 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.