Issues

Issue #7718 resolved

Some people cannot reach the Bitbucket.org site after the migration

scand
created an issue

EDIT: Support editing this issue to request more information for other users having this issue.

Some users have reported issues reaching the site since our migration. To help us understand the scope of the issue, please try the following and let us know the result

  • Flush your browser cache and DNS
  • Verify that you're connecting to our new IP addresses. Ping us, we should should reply from our new IP addresses
  • Try connecting over SSH. You can simply run ssh -Tv git@bitbucket.org and should at least get a refused connection. This will also tell us if it is just one kind of traffic or another.
  • Do a traceroute to Bitbucket and include it here. This will be especially helpful in determining where we should be looking. If you have some machines that function and others that do not, include one from each.
  • Post your public IP address here.

We (Support) will keep editing/updating this issue with more information and requested information as we are investigating.

Previous description.

Hello.

For some reason some of PCs in local network can't get access to bitbucket.org. When we try to get it loaded in browser it hang up and show status "waiting page loading".

It appears starting this Monday (08.07.2013).

Meantime we looked to IP addresses resolved by DNS - these looks correct. 'tracert' get reached target IP address.

But we still didn't find what could be difference between PC that can access and PC that can't.

Are there any solutions we could try?

Thank you.

With best regards and wishes, Alex.

Comments (39)

  1. scand reporter

    Any custom hosts file? Network firewall restrictions?

    No any custom hosts file detected.

    As well for PC that it does not work we didn't change anything from last Friday that it was working. It looks it some way could be related to migration to new storage.

  2. scand reporter

    You mentioned a traceroute brings you to us, but any http request times out? What about SSH connections? Can you try that?

    SSH connection using plink.exe - access the host and shows warning that TTY connection is not permitted.

    Also, does a working machine have the same outbound IP address of a non-working machine? If not, what are they? Also, are both machines relatively identical? As in, same OS, same browser etc?

    Both machines relatively identical, uses Windows 7, use the same gateway.

    One thing that similar to all of three PCs that have problem is that all of these were turned on today and tried access to bitbucket at nearly the same time. It was about 10:00 GMT+02.

  3. Marcus Bertrand staff

    Please add a traceroute from a working machine and a non-working machine. This will help us determine what parts of our infrastructure to investigate from. The more information we have the better.

  4. Marcus Bertrand staff

    Hi, should we expect the DNS to have propagated? I can't get to the website, nor can I push code. Below is ping and traceroute -- note the "multiple addresses" warning in the traceroute...

    BigIron:~ mjy$ ping bitbucket.org
    PING bitbucket.org (131.103.20.167): 56 data bytes
    64 bytes from 131.103.20.167: icmp_seq=0 ttl=48 time=51.331 ms
    64 bytes from 131.103.20.167: icmp_seq=1 ttl=48 time=50.499 m
    ^C
    --- bitbucket.org ping statistics ---
    8 packets transmitted, 8 packets received, 0.0% packet loss
    round-trip min/avg/max/stddev = 50.499/51.899/53.490/1.056 ms
    
    BigIron:~ mjy$ traceroute bitbucket.org
    traceroute: Warning: bitbucket.org has multiple addresses; using 131.103.20.167
    traceroute to bitbucket.org (131.103.20.167), 64 hops max, 52 byte packets
    1 10.0.1.1 (10.0.1.1) 0.492 ms 0.542 ms 0.353 ms
    2 * * * 7.879 ms 7.559 ms 8.195 ms
    3 te-9-2-ur01.lebanon.nh.boston.... (68.87.156.5) 8.073 ms 7.640 ms 8.468 ms
    4 po-50-ur01.berlin.vt.boston.co... (68.87.146.214) 10.492 ms 17.590 ms 11.983 ms
    5 be-70-ar01.needham.ma.boston.c... (68.85.69.177) 21.446 ms 19.258 ms 20.144 ms
    6 he-2-8-0-0-cr01.newyork.ny.ibo... (68.86.93.185) 46.618 ms 47.518 ms 47.903 ms
    7 pos-0-1-0-0-pe01.111eighthave.... (68.86.87.170) 46.949 ms 47.546 ms 48.060 ms
    8 ix-0-1-1-0.tcore1.nto-newyork.... (209.58.26.117) 44.722 ms 52.413 ms 45.302 ms
    9 ae-9.r05.nycmny01.us.bb.gin.nt... (129.250.9.213) 46.470 ms 47.469 ms 46.400 ms
    10 ae-1.r23.nycmny01.us.bb.gin.nt... (129.250.4.68) 47.498 ms 47.739 ms 46.097 ms
    11 ae-1.r20.asbnva02.us.bb.gin.nt... (129.250.2.9) 53.196 ms 53.033 ms 51.068 ms
    12 * * *
    13 po-1.a00.asbnva03.us.da.verio.... (129.250.27.130) 64.512 ms 51.411 ms 54.187 ms
    14 * * *
    15 * * *
    16 * * *
    17 * * *
    ^C
    BigIron:~ mjy$
    
  5. Jason Worley staff

    (BBS-4036)

    Microsoft Windows [Version 6.1.7600] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Users\Mikers>tracert www.bitbucket.org Tracing route to www.bitbucket.org [131.103.20.167] over a maximum of 30 hops: 1 6 ms 6 ms 9 ms 10.7.104.1 2 6 ms 7 ms 7 ms wolv-core-2a-ae9-612.network.virginmedia.net [80 .3.146.57] 3 25 ms 9 ms 9 ms manc-bb-1c-ae12-0.network.virginmedia.net [213.1 05.159.141] 4 8 ms 11 ms 14 ms manc-bb-1d-ae2-0.network.virginmedia.net [62.253 .174.93] 5 33 ms 22 ms 26 ms te-4-3.ar3.CDG2.gblx.net [204.246.200.177] 6 24 ms 26 ms 30 ms xe-0-0-0-5.r04.parsfr01.fr.bb.gin.ntt.net [129.2 50.9.145] 7 22 ms 22 ms 41 ms ae-4.r21.parsfr01.fr.bb.gin.ntt.net [129.250.6.1 78] 8 23 ms 21 ms 27 ms ae-1.r20.parsfr01.fr.bb.gin.ntt.net [129.250.2.1 80] 9 45 ms 29 ms 27 ms as-2.r23.londen03.uk.bb.gin.ntt.net [129.250.5.8 ] 10 46 ms 43 ms 60 ms ae-0.r22.londen03.uk.bb.gin.ntt.net [129.250.4.8 5] 11 148 ms 143 ms 116 ms ae-4.r22.nycmny01.us.bb.gin.ntt.net [129.250.3.1 26] 12 96 ms 124 ms 116 ms ae-0.r23.nycmny01.us.bb.gin.ntt.net [129.250.3.7 3] 13 148 ms 158 ms 160 ms ae-5.r20.asbnva02.us.bb.gin.ntt.net [129.250.2.1 83] 14 122 ms 129 ms 185 ms xe-6-1.r00.asbnva03.us.bb.gin.ntt.net [129.250.2 .57] 15 134 ms 214 ms 200 ms po-1.a00.asbnva03.us.da.verio.net [129.250.27.13 0] 16 116 ms 119 ms 132 ms po-1.a01.asbnva03.us.da.verio.net [129.250.27.13 1] 17 * 129 ms * 131.103.20.156 18 150 ms 144 ms 147 ms 131.103.20.167 Trace complete.

    Update from Customer: 08/Jul/13 11:48 PM "it appears to be back to normal now. Thanks"

  6. Tom Roche

    I'm running git version=1.7.9.2 on a US federal govt HPC cluster

    1. as a very-unprivileged user
    2. inside a firewall that does not allow SSH out
    3. on nodes (which are RHEL) that lack bitbucket's certificates

    :-( Hence I customarily push like env GIT_SSL_NO_VERIFY=true git push bbh master where

    $ git remote -v
    bbh https://tlroche@bitbucket.org/tlroche/gfed-3.1_global_to_aqmeii-na.git (fetch)
    bbh https://tlroche@bitbucket.org/tlroche/gfed-3.1_global_to_aqmeii-na.git (push)
    

    That worked fine before yesterday (U 7 Jul 13). However currently (2339 UTC 8 Jul 13) I'm getting

    $ env GIT_SSL_NO_VERIFY=true git push bbh master
    error: The requested URL returned error: 503 while accessing https://tlroche@bitbucket.org/tlroche/gfed-3.1_global_to_aqmeii-na.git/info/refs
    fatal: HTTP request failed
    
    $ ping bitbucket.org
    PING bitbucket.org (131.103.20.167) 56(84) bytes of data.
    ^C
    --- bitbucket.org ping statistics ---
    21 packets transmitted, 0 received, 100% packet loss, time 19999ms
    
    $ nslookup bitbucket.org
    Server:     134.67.208.5
    Address:    134.67.208.5#53
    
    Non-authoritative answer:
    Name:   bitbucket.org
    Address: 131.103.20.168
    Name:   bitbucket.org
    Address: 131.103.20.167
    
    $ traceroute bitbucket.org
    traceroute to bitbucket.org (131.103.20.168), 30 hops max, 40 byte packets
     1  ncc-s2bb-v68.nccr.epa.gov (134.67.68.2)  0.285 ms  0.340 ms  0.457 ms
     2  ncc-w1-g05-02.nccr.epa.gov (134.67.214.69)  0.333 ms  0.438 ms  0.533 ms
     3  att-ncc-screening-rtr-inside.nccr.epa.gov (134.67.1.54)  0.392 ms  0.389 ms  0.397 ms
     4  * * *
     5  nothing.attdns.com (135.32.27.186)  10.470 ms  10.481 ms  10.484 ms
     6  nothing.attdns.com (135.32.27.185)  10.787 ms  10.484 ms  10.571 ms
     7  * * *
     8  * * *
     9  * * *
    10  * * *
    11  * * *
    12  * * *
    13  * * *
    14  * * *
    15  * * *
    16  * * *
    17  * * *
    18  * * *
    19  * * *
    20  * * *
    21  * * *
    22  * * *
    23  * * *
    24  * * *
    25  * * *
    26  * * *
    27  * * *
    28  * * *
    29  * * *
    30  * * *
    
  7. Francesco Colombo

    Italy here.

    We currently have very LOW download rate from the bitbucket.org site. Also pulls are very slow (4-5Kbyte/sec)

    My traceroute

    C:\Users\Francesco>tracert bitbucket.org
    
    Tracing route to bitbucket.org [131.103.20.168]
    over a maximum of 30 hops:
    
      1     3 ms     4 ms     4 ms  DSL2740B.DSL2740B [192.168.1.1]
      2     *        *        *     Request timed out.
      3    27 ms    25 ms    27 ms  172.17.81.33
      4    26 ms    32 ms    25 ms  172.17.80.13
      5    31 ms    32 ms    29 ms  172.17.6.185
      6    31 ms    31 ms    31 ms  172.17.10.69
      7    33 ms    32 ms    31 ms  bundle-ether15.milano50.mil.seabone.net [93.186.
    128.245]
      8   117 ms   127 ms   127 ms  te8-3.milano52.mil.seabone.net [195.22.205.193]
    
      9    29 ms    30 ms    30 ms  ntt-verio.milano52.mil.seabone.net [93.186.128.2
    5]
     10   142 ms   143 ms   142 ms  xe-0-0-0-3.r03.amstnl02.nl.bb.gin.ntt.net [129.2
    50.4.14]
     11    66 ms    66 ms    66 ms  ae-4.r23.amstnl02.nl.bb.gin.ntt.net [129.250.2.1
    46]
     12    51 ms    52 ms    51 ms  ae-1.r20.frnkge04.de.bb.gin.ntt.net [129.250.3.1
    78]
     13    52 ms    53 ms    52 ms  ae-2.r21.frnkge03.de.bb.gin.ntt.net [129.250.2.1
    2]
     14   145 ms   145 ms   144 ms  ae-3.r23.nycmny01.us.bb.gin.ntt.net [129.250.3.1
    80]
     15   154 ms   140 ms   153 ms  ae-5.r20.asbnva02.us.bb.gin.ntt.net [129.250.2.1
    83]
     16   136 ms   141 ms   142 ms  xe-6-1.r00.asbnva03.us.bb.gin.ntt.net [129.250.2
    .57]
     17   304 ms   216 ms   203 ms  po-1.a00.asbnva03.us.da.verio.net [129.250.27.13
    0]
     18   141 ms   141 ms     *     131.103.20.156
     19   140 ms   145 ms   141 ms  131.103.20.168
    
    Trace complete.
    
  8. TownSpot Inc.

    I'm unable to connect. Last Tuesday we had no issues. This Tuesday we went to do our weekly push to Production and were unable to connect (do a git pull, or ssh -Tv git@bitbucket.org)

    traceroute to bitbucket.org (131.103.20.168), 30 hops max, 60 byte packets
     1  * * *
     2  * * *
     3  * * *
     4  * * *
     5  * * *
     6  * * *
     7  * * *
     8  * * *
     9  * * *
    10  * * *
    11  * * *
    12  * * *
    13  * * *
    14  * * *
    15  * * *
    16  * * *
    17  * * *
    18  * * *
    19  * * *
    20  * * *
    21  * * *
    22  * * *
    23  * * *
    
    ssh -Tv git@bitbucket.org
    OpenSSH_5.3p1, OpenSSL 1.0.0-fips 29 Mar 2010
    debug1: Reading configuration data /etc/ssh/ssh_config
    debug1: Applying options for *
    debug1: Connecting to bitbucket.org [131.103.20.167] port 22.
    debug1: connect to address 131.103.20.167 port 22: Connection timed out
    debug1: Connecting to bitbucket.org [131.103.20.168] port 22.
    debug1: connect to address 131.103.20.168 port 22: Connection timed out
    ssh: connect to host bitbucket.org port 22: Connection timed out
    
    PING bitbucket.org (131.103.20.167) 56(84) bytes of data.
    64 bytes from 131.103.20.167: icmp_seq=1 ttl=55 time=2.92 ms
    64 bytes from 131.103.20.167: icmp_seq=2 ttl=55 time=2.37 ms
    ^C
    --- bitbucket.org ping statistics ---
    2 packets transmitted, 2 received, 0% packet loss, time 1970ms
    rtt min/avg/max/mdev = 2.370/2.647/2.925/0.282 ms
    

    PUB IP: 216.157.108.162

  9. Marcus Bertrand staff

    We've made a few changes in the past week to improve the situation. If you're still seeing the issue, please report everything requested from above to support. We're compiling data from the remaining users with issues.

  10. Marcus Bertrand staff
    • changed status to open

    Changing this back to open as a very small subset of users are still experiencing issues with slow connections. We'd still like all users to report their data to support@bitbucket.org though.

  11. Thomas Guillory

    Hi,

    We are experiencing this issue since yesterday 08/20/13

    Our IP: 82.127.170.100

    Traceroute:

    ~ » traceroute bitbucket.org                                                                                                                                                    thomas@wizcover
    traceroute to bitbucket.org (131.103.20.167), 30 hops max, 60 byte packets
     1  192.168.1.2 (192.168.1.2)  6.812 ms  12.882 ms  14.756 ms
     2  80.10.245.219 (80.10.245.219)  916.354 ms  916.371 ms  918.407 ms
     3  10.123.194.10 (10.123.194.10)  918.396 ms  918.356 ms  918.336 ms
     4  xe-3-2-1-0.ncnan201.Nantes.francetelecom.net (193.253.151.10)  918.319 ms  919.475 ms  919.460 ms
     5  ae45-0.niaub201.Aubervilliers.francetelecom.net (193.252.99.238)  920.215 ms  920.204 ms  965.464 ms
     6  81.253.184.10 (81.253.184.10)  967.669 ms  50.382 ms  160.719 ms
     7  tengige0-15-0-8.auvtr4.Aubervilliers.opentransit.net (193.251.242.202)  160.675 ms  164.681 ms  166.115 ms
     8  te3-1.parse1.Paris.opentransit.net (193.251.128.230)  164.564 ms  164.566 ms  168.062 ms
     9  verio-7.GW.opentransit.net (193.251.251.162)  168.052 ms  171.136 ms  171.124 ms
    10  ae-4.r21.parsfr01.fr.bb.gin.ntt.net (129.250.6.178)  171.107 ms  171.903 ms  171.910 ms
    11  as-4.r22.amstnl02.nl.bb.gin.ntt.net (129.250.3.84)  204.325 ms  205.150 ms  205.887 ms
    12  ae-0.r23.amstnl02.nl.bb.gin.ntt.net (129.250.4.126)  66.511 ms  66.469 ms  429.913 ms
    13  ae-7.r21.asbnva02.us.bb.gin.ntt.net (129.250.2.144)  451.560 ms  454.208 ms  454.241 ms
    14  ae-2.r00.asbnva02.us.bb.gin.ntt.net (129.250.3.114)  454.165 ms ae-2.r04.asbnva02.us.bb.gin.ntt.net (129.250.4.207)  454.146 ms  454.739 ms
    15  * * *
    16  po-1.a00.asbnva03.us.da.verio.net (129.250.27.130)  455.689 ms po-2.a00.asbnva03.us.da.verio.net (129.250.29.130)  455.681 ms *
    17  * * *
    18  * * *
    19  * * *
    20  * * *
    21  * * *
    22  * * *
    23  * * *
    24  * * *
    25  * * *
    26  * * *
    27  * * *
    28  * * *
    29  * * *
    30  * * *
    
  12. carnivalpvp

    Yup, getting extremely slow download speeds too.

      1    <1 ms    <1 ms    <1 ms  style [192.168.0.1]
      2     7 ms     7 ms    10 ms  96.120.36.49
      3    18 ms     9 ms     9 ms  xe-2-0-0-32767sur01.southdade.fl.pompano.comcast.net [68.86.160.73]
      4    12 ms    10 ms    11 ms  te-0-2-0-12-ar03.northdade.fl.pompano.comcast.net[162.151.2.97]
      5    17 ms    11 ms    11 ms  he-2-7-0-0-cr01.miami.fl.ibone.comcast.net[68.86.93.81]
      6    13 ms    15 ms    11 ms  pos-0-0-0-0-pe01.nota.fl.ibone.comcast.net[68.86.87.102]
      7    27 ms    12 ms    26 ms  ix-2-2-1-0.tcore1.MLN-Miami.as6453.net [216.6.16.9]
      8    10 ms    15 ms    11 ms  ae-6.r04.miamfl02.us.bb.gin.ntt.net [129.250.9.33]
      9    15 ms    12 ms    10 ms  ae-3.r20.miamfl02.us.bb.gin.ntt.net [129.250.2.110]
     10    41 ms    41 ms    40 ms  ae-8.r21.asbnva02.us.bb.gin.ntt.net [129.250.2.99]
     11    42 ms    40 ms    42 ms  ae-2.r04.asbnva02.us.bb.gin.ntt.net [129.250.4.207]
     12    43 ms    38 ms   147 ms  xe-6-2.r00.asbnva03.us.bb.gin.ntt.net [129.250.3.153]
     13   223 ms   199 ms   199 ms  po-1.a00.asbnva03.us.da.verio.net [129.250.27.130]
     14    41 ms    42 ms    41 ms  131.103.20.156
     15    42 ms    42 ms    40 ms  131.103.20.167
    
  13. Marcus Bertrand staff

    At this point, we've resolved nearly every major issue we've found since migrating to the new DC. Any further issues should be reported to your local ISP first. Then us (support.atlassian.com) once it has been determined there aren't any other issues between you and us.

  14. Manuele Menozzi

    Hi. I'm still getting very slow speed (20/30 KB/s) when cloning or pulling from a Bitbucket repository. Here is my trace route:

    webgriffe@magentopartners:~/domains/magetest.webgriffe.com/public_html/1702$ traceroute bitbucket.org
    traceroute to bitbucket.org (131.103.20.168), 30 hops max, 60 byte packets
     1  static.1.74.4.46.clients.your-server.de (46.4.74.1)  4.031 ms  4.139 ms  4.179 ms
     2  hos-tr4.juniper2.rz14.hetzner.de (213.239.224.225)  0.174 ms  0.179 ms hos-tr2.juniper1.rz14.hetzner.de (213.239.224.161)  22.385 ms
     3  core22.hetzner.de (213.239.245.125)  15.031 ms  0.241 ms  15.025 ms
     4  core12.hetzner.de (213.239.245.29)  2.839 ms  2.842 ms core21.hetzner.de (213.239.245.161)  15.719 ms
     5  core12.hetzner.de (213.239.245.29)  2.839 ms  2.854 ms juniper4.rz2.hetzner.de (213.239.245.26)  2.842 ms
     6  ae51.bar2.Munich1.Level3.net (62.140.25.101)  5.502 ms juniper4.rz2.hetzner.de (213.239.245.26)  2.801 ms ae51.bar2.Munich1.Level3.net (62.140.25.101)  5.431 ms
     7  ae55.edge7.Frankfurt1.Level3.net (195.16.162.253)  7.255 ms ae-1-60.edge6.Frankfurt1.Level3.net (4.69.154.10)  7.238 ms ae-2-70.edge6.Frankfurt1.Level3.net (4.69.154.74)  7.270 ms
     8  ae-19-19.ebr1.Frankfurt1.Level3.net (4.69.153.246)  9.354 ms ae-0-11.bar1.Munich1.Level3.net (4.69.153.253)  5.722 ms ae-3-80.edge6.Frankfurt1.Level3.net (4.69.154.138)  7.297 ms
     9  ae-19-19.ebr1.Frankfurt1.Level3.net (4.69.153.246)  9.395 ms * ae-61-61.csw1.Frankfurt1.Level3.net (4.69.140.2)  9.386 ms
    10  ae-2-70.edge6.Frankfurt1.Level3.net (4.69.154.74)  9.390 ms ae-71-71.csw2.Frankfurt1.Level3.net (4.69.140.6)  9.374 ms ae-2-70.edge6.Frankfurt1.Level3.net (4.69.154.74)  9.366 ms
    11  * ae-1.r21.asbnva02.us.bb.gin.ntt.net (129.250.3.20)  97.312 ms xe-0-2-0-7.r02.frnkge03.de.bb.gin.ntt.net (129.250.8.201)  9.822 ms
    12  ae-2.r04.asbnva02.us.bb.gin.ntt.net (129.250.4.207)  97.007 ms ae-2.r00.asbnva02.us.bb.gin.ntt.net (129.250.3.114)  94.744 ms xe-0-4-0-7.r02.frnkge03.de.bb.gin.ntt.net (129.250.8.205)  9.843 ms
    13  * * ae-1.r21.asbnva02.us.bb.gin.ntt.net (129.250.3.20)  126.335 ms
    14  po-1.a00.asbnva03.us.da.verio.net (129.250.27.130)  94.730 ms ae-2.r04.asbnva02.us.bb.gin.ntt.net (129.250.4.207)  99.032 ms ae-1.r21.asbnva02.us.bb.gin.ntt.net (129.250.3.20)  95.970 ms
    15  * ae-2.r04.asbnva02.us.bb.gin.ntt.net (129.250.4.207)  97.732 ms  98.990 ms
    16  * po-1.a00.asbnva03.us.da.verio.net (129.250.27.130)  97.971 ms *
    17  * * *
    18  * * *
    19  * * *
    20  * * *
    21  * * *
    22  * * *
    23  * * *
    24  * * *
    25  * * *
    26  * * *
    27  * * *
    28  * * *
    29  * * *
    30  * * *
    

    We're paying for Bitbucket service so please, solve this issue as soon as possible or we'll be forced to migrate to GitHub.

  15. Jesse Yowell staff

    Hi Manuele,

    Your traceroute doesn't seem too bad to me, and the speeds are almost comparable to me here in SF. I'm wondering if this is more of an HTTPS/SSH issue. Could you do the following and send to support@bitbucket.org

    All this should help us troubleshoot the issue better.

    Cheers, Jesse

  16. websiteswithclass

    Pushes take ~ 25 seconds.

    My traceroute says:

     1:  wwc-ubuntu.local                                      0.075ms pmtu 1500
     1:  192.168.1.1                                           0.682ms 
     1:  192.168.1.1                                           0.672ms 
     2:  c-98-233-50-1.hsd1.md.comcast.net                    40.647ms 
     3:  xe-4-1-0-32767-sur01.owingsmills.md.bad.comcast.net  11.524ms asymm  4 
     4:  xe-5-0-0-0-ar04.whitemarsh.md.bad.comcast.net        12.278ms asymm  5 
     5:  he-3-3-0-0-11-cr01.newyork.ny.ibone.comcast.net      20.500ms 
     6:  pos-0-1-0-0-pe01.111eighthave.ny.ibone.comcast.net   23.354ms 
     7:  ix-8-0-1-0.tcore1.NTO-NewYork.as6453.net             43.410ms 
     8:  ae-9.r05.nycmny01.us.bb.gin.ntt.net                  73.873ms 
     9:  ae-7.r23.nycmny01.us.bb.gin.ntt.net                  69.644ms 
    10:  ae-5.r20.asbnva02.us.bb.gin.ntt.net                  19.818ms 
    11:  ae-1.r04.asbnva02.us.bb.gin.ntt.net                  24.618ms asymm 12 
    12:  no reply
    13:  po-1.a00.asbnva03.us.da.verio.net                    19.122ms asymm 11 
    14:  no reply
    15:  no reply
    16:  no reply
    17:  no reply
    18:  no reply
    19:  no reply
    20:  no reply
    21:  no reply
    22:  no reply
    23:  no reply
    24:  no reply
    25:  no reply
    26:  no reply
    27:  no reply
    28:  no reply
    29:  no reply
    30:  no reply
    31:  no reply
         Too many hops: pmtu 1500
         Resume: pmtu 1500
    
  17. Alba Garcia

    tracert (Windows 7 OS)

    $ tracert bitbucket.org
    
    Traza a la dirección bitbucket.org [131.103.20.168]
    sobre un máximo de 30 saltos:
    
      1    37 ms    29 ms    25 ms  212.166.251.122
      2    33 ms    49 ms    49 ms  172.29.131.5
      3     *       46 ms    58 ms  195.10.44.10
      4    68 ms    49 ms    65 ms  195.10.44.9
      5     *        *        *     Tiempo de espera agotado para esta solicitud.
      6     *        *        *     Tiempo de espera agotado para esta solicitud.
      7   415 ms   366 ms   379 ms  ae0-xcr2.prp.cw.net [195.2.10.146]
      8     *        *        *     Tiempo de espera agotado para esta solicitud.
      9     *        *        *     Tiempo de espera agotado para esta solicitud.
     10     *        *        *     Tiempo de espera agotado para esta solicitud.
     11     *        *        *     Tiempo de espera agotado para esta solicitud.
     12     *        *        *     Tiempo de espera agotado para esta solicitud.
     13     *        *        *     Tiempo de espera agotado para esta solicitud.
     14     *        *        *     Tiempo de espera agotado para esta solicitud.
     15   184 ms     *      192 ms  131.103.20.168
    
    Traza completa.
    

    Public IP: 178.139.124.185

  18. henry w

    I am seeing what I think is the same issue here.

    from a command line, I can ping bitbucket.org, but a git clone to either https or ssh address results in 'Could not resolve host: bitbucket.org'.

    this appears to be a windows only issue as other people on the same lan using linux have no issues.

    thanks

  19. Jaikiran Pai

    The past few days we have been having major issues with our continuous integration server which builds against mercurial repos hosted on bitbucket.org. Most of those jobs have been hanging for hours without completing. Investigating into it led us to problems with the bitbucket infrastructure. Running traceroute to bitbucket.org shows that it fails to complete. The output is as follows:

    traceroute to bitbucket.org (131.103.20.167), 30 hops max, 60 byte packets
     1  192.168.0.1 (192.168.0.1)  3.463 ms  3.558 ms  3.710 ms
     2  v1130.core2.fmt2.he.net (216.218.185.209)  7.184 ms  14.669 ms  15.225 ms
     3  10ge3-3.core3.fmt2.he.net (184.105.222.141)  7.477 ms  13.972 ms  13.943 ms
     4  10ge10-1.core1.sjc2.he.net (184.105.222.14)  22.177 ms  21.800 ms  21.781 ms
     5  sjo-bb1-link.telia.net (213.248.67.105)  20.979 ms  20.960 ms  21.096 ms
     6  ntt-ic-306350-sjo-bb1.c.telia.net (62.115.44.46)  14.159 ms ae-9.r20.snjsca04.us.bb.gin.ntt.net (129.250.4.206)  3.149 ms  11.597 ms
     7  * * *
     8  ae-2.r06.asbnva02.us.bb.gin.ntt.net (129.250.7.27)  79.288 ms  81.709 ms  81.151 ms
     9  xe-0-2-0-19.r06.asbnva02.us.ce.gin.ntt.net (129.250.203.90)  81.584 ms  81.719 ms xe-0-8-0-19.r05.asbnva02.us.ce.gin.ntt.net (129.250.203.54)  82.168 ms
    10  * * *
    11  * * *
    12  * * *
    13  * * *
    14  * * *
    15  * * *
    16  * * *
    17  * * *
    18  * * *
    19  * * *
    20  * * *
    21  * * *
    22  * * *
    23  * * *
    24  * * *
    25  * * *
    26  * * *
    27  * * *
    28  * * *
    29  * * *
    30  * * *
    

    We are seeing this problem on some other systems too. Is there something that can be done about this? It's been a pain baby sitting our build server, due to this issue, the past few days.

    FWIW, we are trying to hg pull the repos backed by ssh.

  20. Jaikiran Pai

    I had to switch to using https repo URL (and that worked) to workaround these problems and get our builds going temporarily. We'll have to revisit our entire setup in the next few days to think of a permanent solution because this has now caused us enough pain for the past few days.

  21. Log in to comment