API returning old data

[imaginethinking]

Hey, I've been encountering some issues where the API is returning data which is very outdated for example if I go to the endpoint:

https://api.ashcon.app/mojang/v2/user/12d44d3d-47a4-496a-aa45-ea0ae677673b

It returns the username "HOGCYCLERBDOT" which was changed 47 days ago to a new username

{
  "uuid": "12d44d3d-47a4-496a-aa45-ea0ae677673b",
  "username": "HOGCYCLERBDOT",
  "username_history": [
    {
      "username": "HOGCYCLERBDOT"
    }
  ],
  ...........

Is there some ongoing issue with the caching time of Mojang profiles?

[u9g]

Any solutions to this issue?

[MisterFixx]

From some independent research, it appears that the Mojang API is blocking all requests coming from CloudFlare IPs, requests coming from CloudFlare workers always return a 403 status code, while the same request from any other IP goes through just fine.

[kimoVoid]

Any chance this could get fixed? Is there even any alternative APIs we can use meanwhile?

[zanethefox]

From some independent research, it appears that the Mojang API is blocking all requests coming from CloudFlare IPs, requests coming from CloudFlare workers always return a 403 status code, while the same request from any other IP goes through just fine.

@Electroid this might help figure out what the issue is.

Does anyone know if there is any way to change the IP the request is coming from?

Is it possible to host the API on a different server/locally potentially?

I'm noticing the same issue, 2 MC username websites are reporting my old username which contains my full IRL name, instead of my new username

@Electroid I've sent you an email with more info if you get a chance, it'd be much appreciated if you can fix this
Thank you for your time