Same here, I get HTTP 403. already opened a support ticket. This is really annoying. I recently switched to GitHub Actions and got rid of my Jenkins+Nexus which cached the jars.
Thought the new hype is all cloud only, so there should not be any limitation on the repos!
I am not willing to pay 50bucks per month again to host and maintain a Nexus instance, just because Atlassian starts limiting maven repo access out of the blue.
No communication on this topic beforehand to prepare. My whole release chain is currently blocked by this……
Reportedly (i.e. unconfirmed) the Maven limiting is not deliberate, rather a side effect of the major ongoing outage across the entire Atlassian Cloud platform: https://status.atlassian.com/
Our maven repository was having problem during Jul 6th. I believe it was the main reason that made you experience with the problem
That one has been sorted and should run fine now.