From today at 15:00 CET we started receiving “access denied” and “internal” errors when interacting with our existing buckets. It doesn’t happen with new buckets though and we haven’t changed anything in our logic that would explain the issue.
Something that we also noticed is that if we try to visualize the bucket through Tigris’ web’ interface, we also get a 500 error there so we believe it’s most likely a service disruption on Tigris end. This is currently causing an incident in our service, so we’d appreciate if anyone from Fly/Tigris can prioritize looking into it.
