I understand that the answer you’re getting for is not the answers you were hoping to get. But just opening more topics about the same issue is not going to help fix it.
Yes, we already told you multiple times:
Basically everyone experiences this after setting up their website, because it’s DNS cache, and this is just how the internet works.
It’s so common that there is even a warning banner in the client area shown for new accounts to inform people about this.
So please stop insisting that this is some mysterious hosting issue. It’s not a hosting issue and it’s very common. And we can help you, but not if you completely ignore what we tell you and insist it’s a something you need us to fix.
The screenshot actually proves this: DNS caching is a thing. Some resolvers still thing your domain is at AWS even though it isn’t. And as you can see: it’s different locations and DNS resolvers that affect this. And there is a reason the DNS propagation checker doesn’t tell you which browser they use for the test, because it’s unrelated to browsers.