Hi,
We're seeing large volumes of HTTP/2 errors communicating with the Bitbucket API. These errors started appearing as of about 6:00AM Pacific time this morning. We're still investigating whether or not these errors are impacted by anything on our end given that the Bitbucket status page shows all systems operational. Any advice?
All errors are of the form:
Get "https://api.bitbucket.org/2.0/user/permissions/workspaces?q=workspace.uuid[redacted]": stream error: stream ID 15; STREAM_CLOSED; received from peer
Same for us!
Started to look into the cause, but seeing others affected and we didn't change anything that could cause those issues, I'd say it's on Atlassian ends or a more general network issues between their servers and us.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Status page updated and acknowledging the outage by the way
https://bitbucket.status.atlassian.com/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
we are also facing the same issue
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.