For me it was really an issue with my Internet Service Provider (ISP) not having a great connection to Amazon S3 - that eventually got solved by them. But since you say you have the same issue through a VPN then I don't know really what could cause this. I can definitely say once my ISP solved it prismic is blazing fast for me.
Hmm maybe you can try using an internet connection at a cafe or so that has a different provider than your own? Poking in the dark here, sorry.
It seems to work fine for me when the VPN is set to certain countries, but not others. I guess I'll just keep going that way, but probably something worth looking into for the Prismic team since now it has happened for at least a few people with different locations.
Yeah, I am no Amazon pro, but I'm pretty sure one can set the files to be stored in multiple locations. Maybe they already do that, so that's up to the prismic team to check. Though if it was not it might be worth a try. For static files it shouldn't be that expensive and mirroring the files to servers that are closer to the customers will significantly speed up things and also increases the chance that ISPs have a distinct connection to that local server in contrast to going half around the planet to the US.
At least in my case it was purely an issue with the static files that serve the UI of the data.
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.