1. Bitbucket
  2. Public Issue Tracker
  3. master
  4. Issues


Issue #8809 invalid

Cloning and Pushing excruciatingly slow

created an issue

Hey Guys,

My colleagues and myself (colleagues working out of Redwood City, CA and me out of Boston, MA), are noticing long push and clone times.

I'm currently at home and I've checked my internet connection and things are fairly speedy (steady around 35 mbps according to speedtest and other sites such as facebook, google news, cnn open up fairly quick)

I've never had a problem cloning/pushing my repo code up to bitbucket, but today it's very slow.

(I've been stuck below for the last 5 to 10 mins now) Receiving objects: 45% (2980/6538), 4.66 MiB | 63.00 KiB/s

Any ideas?

Btw, sorry I do not know who to assign this too so I have chosen someone at random.

Comments (92)

  1. Jonas Bredin

    remote: Counting objects: 1364, done. remote: Compressing objects: 100% (1080/1080), done. Receiving objects: 25% (341/1364), 940.00 KiB | 3.00 KiB/s

    ... I am on a 100 MB fiberline

  2. Alex Antonov

    Ok guys for all of you future SLOW IT NAHT WARKENG i managed to find out why - it's git guys. If you're on git - its slow, the bottleneck is not your connection speed, or Atlassian connection, its the way git handles files, each individual file should be processed in special - "slow" way. So basicly - more files, slower speed, disregarding files size.

    That's afaik ofc, i might me wrong.

  3. ytitov NA

    I'm having the same issue, I managed to get it to 45% by increasing the timeout from 30 seconds to 180 seconds and that helped a little. But still can't pull 100% of my branch, and just a few minutes ago got "SSL peer shutdown incorrectly." Internet is working just fine, pinging www.bitbucket.org is fine... I don't get it.

  4. Philip Ryan

    I wish there was some more feedback via the bitbucket website app. I don't mind things being slow, but just would like to have some idea of the duration expected.

  5. Riad Djemili

    Having the same problem with a private repository. 20 KiB/s on a 100 MB connection. Total repository size is about 600 MB. Tried cloning the git mirror for testing and it was downloading that with over 1 MiB/s. We're on a unpaid plan. Could that be the reason?

  6. Shireesh Jayashetty

    I can tell you its not because you are a non-paying customer. I too am on an unpaid plan as of now. In my case, it turned out to be a firewall issue. Bypassing firewall is my current solution :)

  7. Riad Djemili

    Small Update. Was able to load with nearly 1 MiB/s when I tried a couple of hours later. I don't think that it was related to firewall in my case as I was able to download the git mirror with high speed before.

  8. Kyle Savage

    In case this helps anyone else: I was having the same issue (averaging about 50 KiB/s on a healthy 50mbps connection). Following the Network Troubleshooting Guide posted above, the first test of cloning the git mirror went very fast, averaging 2.5 MiB/s. In that test I noticed that their clone url ended in .git ("git clone https://bitbucket.org/mirror/git.git"), but the command I used for cloning my own repo did not. So I stopped my painfully slow repo clone, grabbed the proper url provided by the repo's Clone action (under the "..." button near the top of the left-hand sidebar), and had a successful fast download of a nearly 1.7GB repo with steady speeds around 3 MiB/s.

    So I can't say for sure if the change in my commands made a difference, or if it was just a matter of stopping and restarting that did the trick, but there's definitely nothing slow about bitbucket!

    Original command:

    git clone https://bitbucket.org/[private]/[repo name]

    New command:

    git clone https://savagekyle@bitbucket.org/[private]/[repo name].git
  9. Jason Stokes

    Why has this been marked invalid? I've just created a few repos and now trying to push and it's creeping. I haven't had this issue before. I think this is definitely an issue that needs to be addressed.

  10. Bernhard Steiner

    I'm in central europe, on a 100mb connection. Currently cloning with a maximum of 90kb/s. Thats awful. Would be nice if the bitbucket team could make a statement on this. Marking a worldwide existing problem as invalid is NOT good user support.

  11. Alexander Holte-Davidsen

    We are experiencing the same exact issue. Checkouts of large repositories are very slow, pushing commits are also terrible slow.

    I did a compare of bitbucket vs gihub:


    home:tmp(1)> git clone https://bitbucket.org/mirror/git.git
    Cloning into 'git'...
    remote: Counting objects: 191144, done.
    remote: Compressing objects: 100% (59637/59637), done.
    remote: Total 191144 (delta 141142), reused 174635 (delta 129583)
    Receiving objects: 100% (191144/191144), 54.35 MiB | 101.00 KiB/s, done.
    Resolving deltas: 100% (141142/141142), done.
    Checking connectivity... done.


    home:tmp(1)> git clone https://github.com/git/git.git git_github
    Cloning into 'git_github'...
    remote: Counting objects: 193609, done.
    remote: Compressing objects: 100% (312/312), done.
    remote: Total 193609 (delta 204), reused 11 (delta 11), pack-reused 193286
    Receiving objects: 100% (193609/193609), 65.10 MiB | 617.00 KiB/s, done.
    Resolving deltas: 100% (141363/141363), done.
    Checking connectivity... done.

    The clones are done from Norway, so I'm not located near either github or Bitbucket.

  12. Isuru Jayakantha

    I'm new to bitbucket but not to git but when i clone it stopped me at the stage

    remote: Counting objects: 76, done. remote: Compressing objects: 100% (59/59), done. Unpacking objects: 65% (50/76)

  13. raymond shpeley

    I just finished watching 10 minutes of data upload at about 500Kbits/s and there is no way my commit was that large. When I closed the upload window from git gui another popped up saying the upload was successful --- what the heck???

  14. raymond shpeley

    Made three small changes to my files and pushed them. Same as last time, high upload rate that keeps on running even after I close the git programs. git-remote-https.exe stays running in the background uploading data. Is this some kind of hacker exploit?

  15. Anthony Scolaro

    For Composer users, I know this doesn't solve Bitbucket bandwidth issues directly but a workaround is to use Toran Proxy. Bitbucket is only a fallback source after the initial clone/deploy and our team's workflow is much faster now. I will continue to find ways to rely on BitBucket.

  16. Matthew Cawley

    I'm suffering with extremely slow push requests. Pull requests are fine though:

    Counting objects: 57, done.
    Delta compression using up to 4 threads.
    Compressing objects: 100% (28/28), done.
    Writing objects:  68% (39/57), 38.24 MiB | 5.00 KiB/s    
  17. prasadguru

    We've been facing this problem for the past couple of weeks when we try to clone or push. it stops at 7% of receiving object and fails.

    Note: We are trying to clone or push files from India. What would be the cause for this issue?

  18. Parth Dave

    getting 1mbps download speed but when i clone or download repo only getting 7-10kbps dunno what's up with bitbucket

    BitBucket please give us a solution

  19. Hannes Väisänen

    Problem you all are having is most probably because you all use plink as ssh client and it's simply, slow.

    I recommend to switch to open ssh and I'll tell you how to that in sourceTree, smartGit, gitBash and tortoiseGit.

    Step 1

    First, open your current key in puttyGen and convert it to openssh key via conversions menu, save it to %homepath%.ssh with name id_rsa By default your openssh key should now be at c:\users\%username%.ssh\id_rsa

    Download git if you don't already have it https://git-for-windows.github.io/ Install it and choose Use OpenSSH as SSH executable. Now we need to make system use OpenSSH as it's ssh client.

    Press windows button + r, type cmd and hit enter write setx GIT_SSH "C:\Program Files\Git\usr\bin\ssh.exe" If you are going to use Git Bash, goto step 3, otherwise goto step 2.

    Step 2

    Pick you client...

    Sourcretree: Go to tools - options - general SSH Client configuration, put your new openssh key to ssh key field and choose OpenSSH as ssh client. You are good to go to Step 3

    SmartGit: Goto Edit - preferences - authentication. Tick 'Use System SSH client' You are good to go to Step 3

    TortoiseGit: Goto folder where your git project is located goto Tortoisegit - Settings - Network Change ssh client to C:\Program Files\Git\usr\bin\ssh.exe Git - Remote, click your remote and place your openSSH key in PuttyKey field. You are good to go to Step 3

    Step 3

    Now it should work for Git Bash but your git host is not known host and most of these GUI client's will not show you prompt to add your host to known_hosts file so we have to use Git Bash at least once to be able to add our host as known. Press windows button + r and type C:\Program Files\Git\git-bash.exe

    Goto your project folder. If your project is on J: drive, then change drive by writing cd j: and after that just use cd path/to/your/folder and press enter. write git pull. You will be warned "The authenticity of host xx.xx.xx can't be established' so this is the prompt we wanted, now write yes and hit enter.

    Now you are done, you can use git with openssh enabled and enjoy fast cloning and pulling.

  20. Jacob T. Nielsen

    In case many different problems are being reflected on this issue, I will mention one scenario where I was doing a push at ~ 150KiB/s before setting the following. After it's about ~ 50MiB/s

    git config --global http.postBuffer 524288000
  21. Sean Knight

    I'm on a paid cloud account. I have gigabit internet right to my workstation, my problem seems to less with transfer speed and more with whatever else git does. For example:

    $ time git pull
    Already up-to-date.
    real    0m23.293s
    user    0m0.251s
    sys     0m0.075s

    23 seconds for a pull where I am already up to date (not even transferring files) is ridiculous. I get the same thing no matter which ISP I connect from. I'm using a Mac (not that that would make a difference). Other services such as Github, or even a private Gitlab hosted on the other side of the United States is much much faster.

  22. Tien Nguyen

    Today I clone a project about 250MB, and its speed is 20KB/s. Unbelievable. Finally I turn on Hotspot Shield and get higher clone speed. So I think, maybe the clone speed is limited in some countries.

  23. mjoseph123

    this is becoming a trend on google searches. i thought this would make our lives easier.17mbps internet , still crawls when cloning to ST. my apologies for ranting.

  24. Abhishek Dujari

    I want to retract what I said about bitbucket being slow. I found the problem to be a slow/jittery connection. I swapped out my switch with a better router and I am back to 1MB++/second for push. I realised this when all my other downloads/uploads also slowed down, whereas the modem itself was reporting 1Gbps which is the actual subscribed speed I have. Now all pull and push are going so fast, I barely get to see what happened.

    I am sorry bitbucket.

  25. Abhishek Dujari

    sean Knight yes and this is my speed. Albeit it is only a home fiber and my expectations are low. myrepublic_1gbps_fiber_test.png

    Trust me these errors are transient. I was frustrated, so I tried Gitlab and still had issues. Check everything between your terminal to the internet. Something is not dealing with SSL correctly. I have strong feeling that the shitty TPLink switch I was using in between must be backdoored

  26. Abhishek Dujari

    @SeanKnight Then it's clear. Bitbucket seems to have a problem with connectivity or routing. Depending on your location you could have bad experience. It may pass in a few minutes, hours or days or never, depending on BGP. Btbucket wont do anything about it, this issue is marked Invalid. We can only help each other in this thread. There are like 50 odd watchers in this thread of how many thousands of people who use Bitbucket without issue. Giorgos Lemonidis Provide more info. Time output is not enough, I mean how big is the repo? How many refs are in there etc. Perhaps we can help troubleshoot.

  27. Jan B

    Wow, so this will never be solved? Got the same issue, Github takes a second while BitBucket takes ages (no matter if via console or sourcetree). It worked fine for me a half year ago and since then I'm only having problems.

    As I'm living in the mid of a state capital the answer "Depending on your location you could have bad experience." is an invalid reason for me ~ the size of my repo only is 1,43 MB so it really shouldn't take that long :/

  28. Giorgos Lemonidis

    Yes I believe it's a location issue. Tried pulling the same repo in two different servers with the same specs and configurations. One located in the uk takes a few seconds, the other in germany takes over a minute.

  29. Roberto Gardenier

    We should just give this a rest already. It's obvious BitBucket doesn't want to handle this problem seriously. All what happens is more and more people "upvoting" this issue, but there has been zero response. I moved all my projects, private and public, out of here. Goodbye Bitbucket :D

  30. Sean Knight

    I disabled IPv6 on my network and haven't noticed the problem since. I had no other problems connecting with IPv6 to other sites. I haven't had time to dig into it further. Maybe it's a reverse DNS issue?

  31. jubari

    Pushing and pulling takes minutes instead of seconds on Bitbucket. Seeing this issue has been marked as "invalid" made it an easy decision to leave.

    Our team and private repos are moving over to Github.

  32. Jan B

    What a shame, this isn't "invalid" nor just "location based" - it's a serious bug that more and more will get with providers switching to IPv6.

  33. Ian Hincks

    On the campus of the University of Waterloo (who runs their own ISP), it reliably takes minutes to push to bitbucket. Our speeds are quite fast, 750Mbps up and down. This is certainly not an invalid issue.

  34. Dinesh Dharme Omniscience

    Guys, This issue is still present as of 31st December 2016. I have 13mbps line and it shows

    Receiving objects: 1% (183/13759), 43.43 MiB | 150.00 KiB/s

    on cloning a project using a ssh url. Could you please fix it.

    Thanks, Dinesh

  35. Curtis Cooley

    For me it's an IPv6 issue. BitBucket doesn't respond to IPv6 ssh requests, so you have to wait for it to timeout. I fixed it by adding

    AddressFamily inet

    to /etc/ssh/ssh_config and git pull responds within seconds not minutes.


    %>time git pull --rebase
    Current branch master is up to date.
    real    1m17.140s
    user    0m0.109s
    sys 0m0.135s


    %>time git pull --rebase
    Current branch master is up to date.
    real    0m1.943s
    user    0m0.110s
    sys 0m0.131s

    Hope that helps someone. I searched all day until I found https://grosse.io/blog/posts/Fixing-slow-Bitbucket-git-connections-via-SSH with the answer.

  36. Log in to comment