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:
AddressFamily inet
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.
Did you reconnected to your network or restarted your devices?
I use mobile hot-spot for Internet, so rebooting my mobile worked and not just disconnecting and reconnecting to Internet
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you very much Samuel, forcing ssh to use IPv4 also solved slow response time from bitbucket. This was driving me crazy since it would not replicate on two different PC both connected on the same network !
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Same "story" here.
I think it would be faster to visit their data center on foot and copy data, than wait for "git clone"
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.
Same here in 2019.. download speed from repo 60-100 kbps on 100 mbps download. No problem on ISP, everything else working perfectly. Obviously Bitbucket is being very slow and nobody pays attention. Time to move to GitHub
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.
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.
Same here in Sep 2020 mine is even shameful,
4.8 KB/s - 689 KB of 60.3 MB, 4 hours left
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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 must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
worst speed ever seen 3kbps, please look into this atlassian
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.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I tried SSH connection via ipv4, but same issue. i just turned off everything like @hritikarthur suggestion and it's working now.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
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.
Was this issue ever resolved? I am also experiencing slow speeds when cloning a git repo. Actually my downloads seem to get throttled after about 30% downloaded. My average speeds are 90Kbps to 150Kbps, on a gigabit network. Anyone have any additional insight on this issue?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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:
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.