Restarting doesn't help at all for me. I've restarted both, network-connection and PC. Without success.
For me it takes now round about 5 Minutes to do a fetch and > 10 Minutes to do a push. The Network-Speed shows a short peak of 150KiB/s and after that slow down to round about 1-3KiB/s. The Screenshot shows round about 1 Minute of connection time (and the fetch was not yet finished after that)
I've looked at the network-troubleshooting guide, and figured out, that the ping does not get a connection:
After all, what solve my Issue was to force ssh in ~/.ssh/config to use IPv4 with this line:
I don't know, why this issue happend out of the blue, because before yesterday it works like a charm without... but this solve it for me.
Thanks from me as well!
I just started using BitBucket and had excruciatingly slow clone times which made it basically impossible to clone a repository, either via https or ssh.
My ISP does in fact only provide me with an IPv6 address.
I resolved the issue by using my company VPN which prodvides me with an IPv4 address. After connecting to the VPN the git clone was as fast as I'm used to from GitLab!
Hello everyone, just restart all your network devices like your modems, routers, hotspots and whatever you are using to get connected to internet.
This worked for me.
I was also facing the same issue, everything else was getting good speed except bitbucket, but it is solved when I restarted my mobile (I was using mobile's internet using hotspot)
You don't say what kind of repo (Git/Mercurial) or the size of the repository. All those can make a difference in clone performance. Your network may also impact the performance. Here are some things you can do to troubleshoot:
We don't have any issues with our network that would cause this. In many cases, we've found that the route from a user's ISP to our network (NTT) to be the issue. Please work with your ISP first to determine if they can reproduce the issue. Then, review our network troubleshooting guide for assistance in things you can check that could be a cause. Finally, once you've exhausted these options, come to support with the results from the tests noted in our trhoubleshooting guide. We will be able to provide this information to our network provider.
Hi everyone, We are looking to learn more about development teams’ workflows and pain points, especially around DevOps, integrations, administration, scale, security, and the related challeng...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events