Error 503 Backend fetch failed for any UUID that is not cached by MineTools.

[WouterGritter]

We're getting Error 503 Backend fetch failed errors on UUIDs that have not been cached by MineTools.

An example UUID that currently returns this error (as of writing the issue, it has not been cached by MineTools): https://api.minetools.eu/uuid/74352926bba44e7ebea4435a7fce01f8

[Leon-JavaScript]

I can confirm this, it also doesn't only happen at the UUID route, it happens on all routes.

[zanethefox]

Unfortunately, can also confirm this is still happening. @McLive have you seen this? Thanks!

[markusobi0]

It now affects the main route api.minetools.eu as well. @McLive please implement a fix asap.

[AlvinVrolijk]

+1

[WouterGritter]

We unfortunately had to divert to another API, we are now using PlayerDB which is working fine for us. Sucks that our product broke and everyone had to update manually, however.