User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
Is fraud.net down?
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 →
What to try while fraud.net is having problems
Estimated fix: Not enough fraud.net history yet; similar AI outages lasted 27 min (median, typically 9 min–2 h; 41 outages).
- Try the mobile app or a private window, or the API; another assistant can cover urgent work.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → fraud.net—
Your browser → us—
Our checksReaching it
Official · ReportsMinor incident · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
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.
Live outage map
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.
What's broken
Recent reports
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.
Our checks
Reaching it
Last checked 39 min ago. Last stored result reached it in 72 ms.
Official status
Minor incident
Some components degraded (no active incident posted) Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 20 | 0 | 0.0 | 73 ms | 0 |
| Mon 22 | 0 | 0.0 | 92 ms | 0 |
| Tue 00 | 0 | 0.0 | 123 ms | 0 |
| Tue 02 | 0 | 0.0 | 79 ms | 0 |
| Tue 04 | 0 | 0.0 | 69 ms | 0 |
| Tue 06 | 0 | 0.0 | 72 ms | 0 |
| Tue 08 | 0 | 0.0 | 68 ms | 0 |
| Tue 10 | 0 | 0.0 | 62 ms | 0 |
| Tue 12 | 0 | 0.0 | 63 ms | 0 |
| Tue 15 | 0 | 0.0 | 128 ms | 0 |
| Tue 17 | 0 | 0.0 | 132 ms | 0 |
| Tue 19 | 0 | 0.0 | 86 ms | 0 |
| Tue 21 | 0 | 0.0 | 52 ms | 0 |
| Wed 00 | 0 | 0.0 | 146 ms | 0 |
| Wed 02 | 0 | 0.0 | 66 ms | 0 |
| Wed 04 | 0 | 0.0 | 83 ms | 0 |
| Wed 06 | 0 | 0.0 | 75 ms | 0 |
| Wed 09 | 0 | 0.0 | 63 ms | 0 |
| Wed 11 | 0 | 0.0 | 116 ms | 0 |
| Wed 13 | 0 | 0.0 | 98 ms | 0 |
| Wed 15 | 0 | 0.0 | 80 ms | 0 |
| Wed 17 | 0 | 0.0 | 96 ms | 0 |
| Wed 19 | 0 | 0.0 | 105 ms | 0 |
| Wed 22 | 0 | 0.0 | 25 ms | 0 |
| Thu 00 | 0 | 0.0 | 76 ms | 0 |
| Thu 01 | 0 | 0.0 | 146 ms | 0 |
| Thu 03 | 0 | 0.0 | 94 ms | 0 |
| Thu 04 | 0 | 0.0 | 99 ms | 0 |
| Thu 06 | 0 | 0.0 | 71 ms | 0 |
| Thu 08 | 0 | 0.0 | 118 ms | 0 |
| Thu 10 | 0 | 0.0 | 92 ms | 0 |
| Thu 13 | 0 | 0.0 | 102 ms | 0 |
| Thu 15 | 0 | 0.0 | 91 ms | 0 |
| Thu 17 | 0 | 0.0 | 107 ms | 0 |
| Thu 19 | 0 | 0.0 | 104 ms | 0 |
| Thu 21 | 0 | 0.0 | 62 ms | 0 |
| Thu 23 | 0 | 0.0 | 69 ms | 0 |
| Fri 01 | 0 | 0.0 | 176 ms | 0 |
| Fri 03 | 0 | 0.0 | 88 ms | 0 |
| Fri 05 | 0 | 0.0 | 63 ms | 0 |
| Fri 07 | 0 | 0.0 | 76 ms | 0 |
| Fri 09 | 0 | 0.0 | 75 ms | 0 |
| Fri 10 | 0 | 0.0 | 103 ms | 0 |
| Fri 11 | 0 | 0.0 | 72 ms | 0 |
| Fri 13 | 0 | 0.0 | 79 ms | 0 |
| Fri 15 | 0 | 0.0 | 72 ms | 0 |
| Fri 17 | 0 | 0.0 | 127 ms | 0 |
| Fri 19 | 0 | 0.0 | 72 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
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.
Embed this status: free live fraud.net badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for fraud.net yet. Outages of 10 minutes or more get their own page here.
Having trouble with fraud.net?
One report per service every 10 minutes from this network. No account.
Follow fraud.net
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.
About fraud.net
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.
Questions
Is fraud.net down right now?
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)
When was fraud.net last down?
We have not recorded a public fraud.net incident since monitoring began 7 days ago.
What is fraud.net's uptime?
From our own checks: 100% over 7 days of checks.
How fast does fraud.net respond?
85 ms on average over the last 24 hours (41–176 ms).
Does fraud.net have an official status page?
Yes, at https://status.fraud.net.
fraud.net not working for me but the status is fine. What now?
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.