Your connection when cloning, pushing, or pulling from Bitbucket seems really slow. You checked the site status at http://status.bitbucket.org and the status doesn't show any downtime or issues. Bitbucket uses NTT/Verio, a top level ISP and hosting service. NTT/Verio provides some of the fastest connections possible globally. Problems can exist anywhere between multiple points. So, it is difficult for Bitbucket Support to troubleshoot your specific network connection issues.Below, we've listed common troubleshooting steps to help you self-diagnose your issues.
Many countries filter or otherwise slow encrypted traffic. HTTPS and SSH are encrypted traffic. Depending which country you are working from, you could be subject to certain issues completely outside of Bitbucket and your control.
Step 1. Test your connection speed
You should see speeds around 200+ KiB/sec or (much) faster consistently from anywhere globally. To test your connection, use Git and the public Git repository mirror we host.
- Ensure you have Git setup.
If you aren't using Git, you will need it. Please follow our setup guide to get everything setup.
Clone the Git mirror using https.
- Examine the output for this line:
Receiving objects: 100% (156094/156094), 36.57 MiB | 1.21 MiB/s, done.
The speed in this test was 1.21 MiB/s which is very fast. Any number equal to or larger than 200 KiB/s is a good result.
Let this serve as your benchmark to target. If you aren't seeing 200 KiB/s or faster, continue troubleshooting.
Step 2. Isolate the source
Try to find out the source of the slower connection. Is it your computer, the environment on your computer, or the network the computer is on.
Is your computer the problem?
- Go to another computer on your network.
- Run the clone mirror test.
- Is the speed significantly faster on the other machine
- Yes? Then, likely the slowness you are experiencing is a result of you computer or its environment. Check the common causes below to further narrow down the issue.
- No? Go on to check if your network is the problem.
Is your network the problem?
- Go to a computer outside your network.
For example, if your office has the issue, check your home connection or even your cell using tethering.
- Run the clone mirror test.
- Is the speed significantly faster on this network?
- Yes? Then, likely the slowness you are experiencing on the original machine is caused by your network. Check the common causes below to further narrow down the issue.
- No? Go on to check the other common causes.
Step 3. Check The Common Causes
Once you've narrowed down the issue to a specific machine or machines, double check the following
- Check all network and configuration settings between the two machines if you see slowness in only a single machine
- Network configuration (DHCP, DNS)
DNSClick here to expand...
Try using Google DNS if you're having issues trying to resolve the site:
- Git configuration
- Network configuration (DHCP, DNS)
- Check all wired and wireless interfaces physically. Sometimes a simple cable issue can cause significant slowness or a flaky network connection.
- For wireless networks, try cloning when very near to your access point.
- Connect your computer directly to your internet connection, if possible. This will rule out any intermediate networking equipment.
If you're in an office with an issue, contact your local network administrator to be sure that they aren't blocking/slowing connections. You can sometimes test this by running a ping or traceroute to bitbucket.org. You should see ~ 10-100ms responses depending on where you are located geographically.
Step 4. Check the Uncommon Causes
- Check latency between major internet backbones (AT&T, Cogent, NTT, Sprint, Verizon, Level3, etc.) – http://www.internetpulse.net/
- Our status page to ensure we haven't reported any outages/issues: http://status.bitbucket.org
Customer Routing from NTT
- First acquire your IP address (http://www.whatsmyip.net/)
- Use the IP address and go to http://www.us.ntt.net/support/looking-glass/ (NTT is our network provider):
- Select the 'Ashburn, VA' Router
- Select 'BGP' (Border Gateway Protocol)
- Enter your IP
- Once you receive this output, please send to https://support.atlassian.com – also, we encourage to contact your ISP as well if you are noticing difficulty connecting to bitbucket.org or any other Atlassian products.
Step 5. Collect Information
There could many other issues affecting your network connection to us and may require more in depth troubleshooting. We recommend always learning more about these suggestions before installing any utilities or executing any of these commands. Note that Bitbucket support cannot help you with these tools and this guide is only to help you troubleshoot.
Check the MTU
If you're on DSL, a possible issue could be a larger than expected MTU size being forced somewhere along the way, this can cause packet fragmentation and loss in some cases. You can check this with a utility called mturoute.exe – http://www.elifulkerson.com/projects/mturoute.php
You should see output similar to the below:
Check the ideal MTU
If you're on DSL, a possible issue could be a larger than expected MTU size being forced somewhere along the way, this can cause packet fragmentation and loss in some cases. To check this on your local machine, do the following:
If you get a message similar to the below, then your MTU is set higher than it should be for your connection. Try lowering it incrementally until you no longer see these messages.
If you're on DSL, a possible issue could be a larger than expected MTU size being forced somewhere along the way, this can cause packet fragmentation and loss in some cases. You can check this with a utility called tracepath, available from the iputils package – http://www.linuxfoundation.org/collaborate/workgroups/networking/iputils
- Install tcptraceroute on the affected machine(s) – Windows - OSX Linux
- Your Operating System and Version
- Your network setup (Wired/Wireless)
Ultimately, the people who will be able to help resolve your issues are your local ISP. They have direct access to the same network as you and are in a much better position to help troubleshoot possible issues.
There are numerous guides out there to help troubleshoot
http://jeromejaglale.com/doc/mac/fix_ssh_connection_delays (Fix slow SSH connections on Mac)