Description
My small experience appears to have been affected by coordinated rating manipulation.
The experience had only 47 total visits, but it suddenly received 10 downvotes. Acquisition analytics show a matching spike of exactly 10 users on July 14, 2026 UTC, after almost no preceding activity. I noticed the rating change on July 16.
The matching numbers do not independently prove that those exact users submitted the downvotes. However, the pattern is abnormal enough that it should be reviewable through Roblox’s internal records.
Observed pattern
- 47 total visits
- 10 downvotes
- A sudden spike of exactly 10 users
- Almost no traffic immediately before the spike
- A hostile detailed-feedback entry appearing around the same period
Actual behavior
Creators cannot see which accounts submitted ratings, their session durations, or the exact times at which individual votes were submitted. This prevents creators from identifying and reporting accounts involved in suspected rating manipulation.
I reported the incident to Roblox Support and requested an internal comparison of:
- The accounts responsible for the ratings
- The accounts included in the traffic spike
- Rating and session timestamps
- Session durations and gameplay activity
- Potentially related account behavior
Support initially interpreted the report as a request to manually remove ordinary downvotes and responded that creators cannot delete ratings.
I clarified that I was not requesting a creator-side rating-removal feature. I was reporting suspected coordinated manipulation and asking Roblox to investigate the relevant accounts and activity.
Support later acknowledged that the report concerned potential coordinated rating manipulation, but still responded with generic advice about improving the experience and earning additional positive ratings. No investigation or escalation route was provided.
This leaves creators without a practical method to report suspicious rating activity. Roblox has access to the necessary account and session information, but creators cannot access it, and Support did not provide a route for having it reviewed.
Expected behavior
There should be an effective system for identifying and reviewing suspicious experience-rating patterns.
At minimum:
- Creators should have a clear reporting and escalation path for suspected rating manipulation.
- Roblox should internally compare concentrated ratings with account and session activity.
- Creator Dashboard analytics should provide enough information to report suspicious patterns without exposing private account data.
- Roblox should clarify whether coordinated or illegitimate ratings are automatically detected and excluded.
- Support reports involving suspected manipulation should not be handled as requests to remove legitimate negative feedback.
Why this matters
A small number of coordinated accounts can heavily affect the public rating of a new or low-traffic experience.
Because creators cannot identify the voting accounts, only Roblox can determine whether the ratings came from legitimate independent players or from alternate accounts, coordinated users, or automated activity.
The current process creates a gap where suspicious ratings can substantially damage an experience, while the creator has no meaningful way to request an internal review.
Reproduction
I cannot safely or appropriately reproduce this issue intentionally, because doing so would require coordinating ratings against an experience.
Roblox staff would need to inspect the internal rating and session records associated with the incident.
Place ID: 86622796637821