BanAsync() itself does work, the “moderation” tab is is hidden and trying to access it returns a 404 error. I don’t think that the hidden tab affects the api itself.
Experiencing the same issue. Shame, because we were relying on it heavily when it rolled out. I’ve made a Roblox Support ticket but I doubt I’ll get an info or help out of it.
The API is unaffected, you can still use it and IP ban people.
As for timespan, in case this knowledge may be relevant:
As of yesterday (Oct 29), 9 AM Central, the Moderation tab was available and functioning.
When I returned to it at 3 PM Central, it was gone and the pages redirect to 404s.
This is such a baffling sequence of events. Roblox has removed our ability to manage bans, made no announcements, and removed any posts about it. Like ???
Experiencing the same issue. We cannot handle appeals right now because we have no access to view or revoke bans.
They were in dev discussion because none of us can tell if this is a bug or intentional. There are no reported outages, and Roblox has made no announcements or replies to bug reports despite this being a major issue.
It’s sad to see how nobody from Roblox staff has responded to this report. Especially since lots of people are (well, were) using the ban category to manage their banned players. It makes it a lot harder to find a particular user to unban if the page is gone . This sure seems like a major issue that is seemingly going unnoticed by them.
It is a major issue, but a very recent one. Might take a few days…
At least the API still works, so you can ban people via console or whatever. Just more of a hassle.
But yes, it’s SUPER bizarre that it’s just gone with no warning or announcement or anything. I was using it at 9 AM and when I came back from my classes at 3 it was gone. Like it never existed.
Hi everyone! Thanks to everyone who reported this issue. There was a faulty change made to our systems that caused the bans page to be hidden from Creator Hub—we definitely have no plans to remove the ability to manage user bans!
We have reverted the change, and the page should be visible to everyone now! Sorry for the delay on getting this fixed—we appreciate your patience!