Inconsistent GetBanHistoryAsync behaviour

[Izuk_ii (Izuki)]

Usually to get a user’s current ban status you would use :GetBanHistoryAsync(userId):GetCurrentPage()[1] and check if the .Ban property is true & StartTime + Duration < current timestamp
This works consistently & as intended:

However, trying to use this same method on an account that was banned by the anti alt system results in unexpected behaviour:

The ban history is empty, yet this user is still banned according to the creator hub.

Expected behavior

I would expect GetBanHistoryAsync to work the same for banned alternative accounts, returning the current ban status as shown in the example below:

Consistent behaviour is critical for my moderation systems:
1. When a user is permanently banned, their private servers are locked. This does not work correctly for alt bans as of right now.
2. Moderators have access to a moderation menu that can be used to look up a user’s ban status. The inconsistent behaviour has caused an incident recently where an alt ban could not be removed because the moderation system thought this user wasn’t banned in the first place.

[oopsiemachine]

After review, we’ve determined the reported behavior aligns with our intended design in order to protect our alt account detections and still give you visibility into which users are banned. However, the team will get together to revisit that decision and see what we can do to reduce confusion and meet your expectations.