Marathon Ban Wave Tracker recorded 2 community reports in the last 90 days, including 1 in the last 7 days. Community reports are not official confirmation of a ban wave.
BattlEye · Community ban reports
Marathon uses BattlEye. An account penalty follows the account, while a device-linked action can recur on the same PC. Neither the publisher nor BattlEye exposes a complete field list for Marathon or a match threshold, so the exact notice and repeat behavior matter more than a guessed serial.
Marathon players have filed 2 ban reports here over the last 90 days, across 2 separate days — an average of 0 per day. The busiest single day was September 1, 2026, with 1 report. The most recent report landed on October 8, 2026.
This page is a community tracker, not an official status feed for Marathon. Players log their own bans here, so the numbers above show submitted reports rather than confirmed publisher actions. The symptom breakdown can help compare reports, but it cannot identify the enforcement layer by itself.
Marathon players submitted 2 reports to this community tracker in the last 90 days; 1 arrived in the last 7 days.
Averaging 0 reports per day. Peak day: September 1, 2026 with 1. Most recent report: October 8, 2026.
About these reports
The reports on this page are community submissions from Marathon players who were banned for any reason — anti-cheat detections, ban waves, false flags, account-sharing, cheat-software use, suspicious behaviour, payment disputes, and so on. They are community submissions, not verified reports about TraceX use. TraceX rewrites supported hardware identifiers; it does not alter publisher records or guarantee access. The data here shows submitted ban-report patterns so players can decide what to check next.
60% of Marathon reports describe banned — 3 of 5. The rest split across an error when launching (2). Reports of launch or connection failures can reflect client, network, anti-cheat, or enforcement issues and do not identify the affected layer by themselves.
| Reported symptom | Reports | Share |
|---|---|---|
| I got banned | 3 | 60% |
| I get an error when launching | 2 | 40% |
2 community reports during this period.
| Date | Reports |
|---|---|
| Jul 16 | 0 |
| Jul 17 | 0 |
| Jul 18 | 0 |
| Jul 19 | 0 |
| Jul 20 | 0 |
| Jul 21 | 0 |
| Jul 22 | 0 |
| Jul 23 | 0 |
| Jul 24 | 0 |
| Jul 25 | 0 |
| Jul 26 | 0 |
| Jul 27 | 0 |
| Jul 28 | 0 |
| Jul 29 | 0 |
| Jul 30 | 0 |
| Jul 31 | 0 |
| Aug 1 | 0 |
| Aug 2 | 0 |
| Aug 3 | 0 |
| Aug 4 | 0 |
| Aug 5 | 0 |
| Aug 6 | 0 |
| Aug 7 | 0 |
| Aug 8 | 0 |
| Aug 9 | 0 |
| Aug 10 | 0 |
| Aug 11 | 0 |
| Aug 12 | 0 |
| Aug 13 | 0 |
| Aug 14 | 0 |
| Aug 15 | 0 |
| Aug 16 | 0 |
| Aug 17 | 0 |
| Aug 18 | 0 |
| Aug 19 | 0 |
| Aug 20 | 0 |
| Aug 21 | 0 |
| Aug 22 | 0 |
| Aug 23 | 0 |
| Aug 24 | 0 |
| Aug 25 | 0 |
| Aug 26 | 0 |
| Aug 27 | 0 |
| Aug 28 | 0 |
| Aug 29 | 0 |
| Aug 30 | 0 |
| Aug 31 | 0 |
| Sep 1 | 1 |
| Sep 2 | 0 |
| Sep 3 | 0 |
| Sep 4 | 0 |
| Sep 5 | 0 |
| Sep 6 | 0 |
| Sep 7 | 0 |
| Sep 8 | 0 |
| Sep 9 | 0 |
| Sep 10 | 0 |
| Sep 11 | 0 |
| Sep 12 | 0 |
| Sep 13 | 0 |
| Sep 14 | 0 |
| Sep 15 | 0 |
| Sep 16 | 0 |
| Sep 17 | 0 |
| Sep 18 | 0 |
| Sep 19 | 0 |
| Sep 20 | 0 |
| Sep 21 | 0 |
| Sep 22 | 0 |
| Sep 23 | 0 |
| Sep 24 | 0 |
| Sep 25 | 0 |
| Sep 26 | 0 |
| Sep 27 | 0 |
| Sep 28 | 0 |
| Sep 29 | 0 |
| Sep 30 | 0 |
| Oct 1 | 0 |
| Oct 2 | 0 |
| Oct 3 | 0 |
| Oct 4 | 0 |
| Oct 5 | 0 |
| Oct 6 | 0 |
| Oct 7 | 0 |
| Oct 8 | 1 |
| Oct 9 | 0 |
| Oct 10 | 0 |
| Oct 11 | 0 |
| Oct 12 | 0 |
| Oct 13 | 0 |
Select the issue you're experiencing
Community report counts cannot identify a ban as account, IP, or hardware enforcement. Start with the exact publisher notice, then use the diagnostic below to assess which type matches the symptoms in Marathon.
Start with the exact notice shown in Marathon and the evidence on this page: 2 community reports in the last 90 days, including 1 in the last 7 days. Report volume does not establish the cause or duration of a sanction. Next, compare the publisher policy recorded in the ban duration database before replacing parts or reinstalling Windows. For the mechanism behind the enforcement itself, how a hardware ban is built and applied walks through detection, review, and the identifiers that get recorded.
If the notice is fresh, start with the first moves after a ban lands before you replace parts or reinstall Windows. The full ban-type diagnostic carries more context than the compact version above, and the complete games directory shows which engine guards each title.
Got an HWID ban in Marathon?
Get TraceX for MarathonMarathon Ban Wave Tracker FAQs answer the current trend, 90-day report volume, BattlEye hardware signals, duration, and reporting method.