3 ms·
Just happened again last week. What's even worse the location from where we tried to access the file also had impact. Like we were able to reproduce the issue f
by biermic 5y ago
Just happened again last week. What's even worse the location from where we tried to access the file also had impact.
Like we were able to reproduce the issue from one location, but not from another.
- loevborg 5y agoThat's interesting - have you tried contacting support? I don't think this is supposed to happen. You might also have better luck using the region-specific S3 endpoint rather than the global domain name.
- biermic 5y agoThat's a fair point. I'll switch over to region specific! Thanks for putting me in that direction. And no - haven't contacted support so far. Will assign someone from my team to get in touch with them.