User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Some components degraded (no active incident posted)
Source: the vendor's status page · We are not affiliated with fraud.net.
Correction: On Nov 10, 2026 we retracted an incident report for fraud.net published in error on Nov 6, 2026. No outage occurred. Read the retraction →
Estimated fix: Not enough fraud.net history yet; similar AI outages lasted 27 min (median, typically 9 min–2 h; 41 outages).
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.
Reachable from all 4 regions we check from.
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 72 ms.
Minor incident
Some components degraded (no active incident posted) Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 171 ms | 0 |
| Nov 7 | 0 | 0.0 | 101 ms | 0 |
| Nov 7 | 0 | 0.0 | 64 ms | 0 |
| Nov 7 | 0 | 0.0 | 49 ms | 0 |
| Nov 8 | 0 | 0.0 | 77 ms | 0 |
| Nov 8 | 0 | 0.0 | 108 ms | 0 |
| Nov 8 | 0 | 0.0 | 100 ms | 0 |
| Nov 8 | 0 | 0.0 | 129 ms | 0 |
| Nov 9 | 0 | 0.0 | 85 ms | 0 |
| Nov 9 | 0 | 0.0 | 70 ms | 0 |
| Nov 9 | 0 | 0.0 | 80 ms | 0 |
| Nov 9 | 0 | 0.0 | 83 ms | 0 |
| Nov 10 | 0 | 0.0 | 79 ms | 0 |
| Nov 10 | 0 | 0.0 | 68 ms | 0 |
| Nov 10 | 0 | 0.0 | 122 ms | 0 |
| Nov 10 | 0 | 0.0 | 52 ms | 0 |
| Nov 11 | 0 | 0.0 | 105 ms | 0 |
| Nov 11 | 0 | 0.0 | 75 ms | 0 |
| Nov 11 | 0 | 0.0 | 96 ms | 0 |
| Nov 11 | 0 | 0.0 | 65 ms | 0 |
| Nov 12 | 0 | 0.0 | 97 ms | 0 |
| Nov 12 | 0 | 0.0 | 92 ms | 0 |
| Nov 12 | 0 | 0.0 | 102 ms | 0 |
| Nov 12 | 0 | 0.0 | 69 ms | 0 |
| Nov 13 | 0 | 0.0 | 88 ms | 0 |
| Nov 13 | 0 | 0.0 | 85 ms | 0 |
| Nov 13 | 0 | 0.0 | 79 ms | 0 |
| Nov 13 | 0 | 0.0 | 72 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 fraud.net 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 fraud.net goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send fraud.net alerts to Slack, Discord or a webhook — free.
We track fraud.net (fraud.net) as part of the AI group. Reduce fraud with real-time, AI-powered fraud detection, case management and advanced analytics. Schedule a free demo today.
fraud.net publishes an official status page at status.fraud.net; when we can read it, its incident level is folded into the status shown here.
Common problems for AI services: slow or failed responses, rate-limit errors, and API timeouts.
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: 85 ms average, 41–176 ms range across 15 successful checks.
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Some components degraded (no active incident posted)
We have not recorded a public fraud.net incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
85 ms on average over the last 24 hours (41–176 ms). Latest regional checks: US East 56 ms, US West 115 ms, Europe 46 ms, Asia-Pacific 209 ms.
Yes, at https://status.fraud.net.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report fraud.net here at once, the problem is on fraud.net'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 fraud.net. 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.