Accounts with the verified badge are not displaying the verified badge, backend API returning inconsistent results

[Noble_Draconian]

Currently, as of 8/7/25, there is a problem with verified badges displaying properly.

As of yesterday, a number of accounts (including mine) were granted the verified / “checkmark” badge for meeting updated criteria. However, the badges on these accounts are not displaying properly:

• The website will randomly show the accounts as having the badge, and then not having the badge. Sometimes it won’t show at all anywhere, sometimes it only shows by the account names in a group wall but not the title or any shouts, sometimes it only shows on the account’s profile.
• When the users API (https://users.roblox.com/v1/users/ID) is invoked, some of the time it will display HasVerifiedBadge as true, other times it will display as false. In-game, if print(game.Players.<VerifiedPlayer>.HasVerifiedBadge) is called, only some of the time it will return true, returning false the rest of the time.
• The badge typically does not show in-game for these newly verified accounts. Older verified accounts display fine.

To reproduce with my account specifically:

1. Connect to Roblox in a way where you would be connecting to servers in the Eastern US region, specifically the Richmond, VA datacenter.
2. Observe that the verified badge frequently does not show on my account, and the users API shows false for the badge.
3. Join a game where you have permissions to the server console (any server region) as my account. Observe that in-game, the badge does not display. My Player's HasVerifiedBadge property has a value of false when invoked from the server console.
4. Using a VPN (such as mullvad), connect to a European country (such as the netherlands), or connect to a node in California (I tested with a node in LA).
5. Observe that the verified badge displays ~90% of the time on my account, still not showing some of the time.
6. Join a game where you have permissions to the server console (any server region) as my account. Observe that in-game, the badge displays, and Player.HasVerifiedBadge is true, even if it is the same exact server instance that previously showed me as not having the badge.
7. Turn off the VPN, and reconnect to the same server instance. Observe that the badge is now gone and the API returns false.

Additional information:

• The most interesting part with this bug is the fact that rejoining a server instance that showed you as having the badge will return false if you connect from a different region, even though the server is what’s invoking the API and the server’s region obviously does not magically change.
• If invoking the API from firefox or the universal app, the API seems to have a 50/50 chance of returning true or false for a verified account. It does it at random regardless of region or if you are on a VPN or not.
• If invoking the API from chrome with no extensions running, the API has a 0% chance of returning true. It always returns false even though that clearly isn’t correct.

I’m obviously not a network engineer but to me this seems like the updated database just isn’t being replicated to some regions when it should be? Why would it take over 13 hours for the updated data to replicate? This is a bizarre issue that is only affecting a specific group of verified users.

Here’s the API showing me as not having the badge:

Here’s the API in a different browser showing me as having the badge:

Here’s the badge showing in-game while on a VPN:

Here’s the badge not showing while disconnected from a VPN:

Expected behavior

It is expected that accounts with the verified badge would consistently display that badge on the website and in-game. Currently it doesn’t display it for a specific group of verified accounts.

[bvetterdays (roman)]

Vouch. I noticed this happening on group pages too, and I’m in Australia, so don’t think it’s specific to any particular region.

[Noble_Draconian]

It seems this was indeed a migration issue. 24 hours later and the issue is gone, badge is showing up 100% of the time in all regions I’ve tested in without a VPN. I’ve spoken to some other recently verified folks, the issue went away for them as well.