[SOLVED] Bubble down or just me?

@funwtp – it’s on our list as a number of people have requested it, but it’s not going to happen in the near future.

@andrew1 @marcusandrews @eurogar, or anyone else who was able to resolve the issue via using a US-based VPN: would one of you mind temporarily turning your VPN off, confirming that you are still seeing issues with Bubble, then running a traceroute (https://support.cloudflare.com/hc/en-us/articles/200169336-How-do-I-run-a-traceroute-) to bubble.is, please? I’ve been testing using a VPN in the UK, but I think the VPN may be messing up my test results, so I’d like to see results from someone who’s based in the UK and is definitely having this issue.

@josh I’m based in Hungary, but don’t have a VPN. I’ll test now and see what’s happening.

Hey @josh

Yep - still running slow.

Traceroute data is below. It was run from Budapest, Hungary. Not sure if it’s normal, but it took 5+ minutes to run:

======
Traceroute has started…

traceroute to www.bubble.is (54.69.164.32), 64 hops max, 72 byte packets
1 * * *
2 hu-bud04a-rc1-ae45-0.aorta.net (84.116.240.205) 10.361 ms 11.879 ms 11.284 ms
3 hu-bud06a-ri1-ae15-0.aorta.net (84.116.137.210) 8.255 ms 10.689 ms 10.512 ms
4 bpt-b4-link.telia.net (213.248.70.253) 10.124 ms 9.156 ms 10.831 ms
5 win-bb2-link.telia.net (213.155.135.222) 172.880 ms 174.168 ms 178.272 ms
6 ffm-bb4-link.telia.net (62.115.133.79) 172.358 ms 178.980 ms 174.780 ms
7 prs-bb4-link.telia.net (62.115.122.138) 178.588 ms 177.709 ms 182.204 ms
8 prs-bb3-link.telia.net (62.115.137.114) 177.261 ms 184.908 ms 176.176 ms
9 ldn-bb3-link.telia.net (62.115.134.93) 183.873 ms 179.571 ms 177.878 ms
10 nyk-bb3-link.telia.net (62.115.135.94) 177.770 ms 180.224 ms 181.249 ms
11 nyk-bb4-link.telia.net (62.115.142.222) 181.817 ms 184.273 ms 187.161 ms
12 sjo-b21-link.telia.net (62.115.119.229) 173.322 ms 173.670 ms 174.543 ms
13 a100row-ic-300117-sjo-b21.c.telia.net (213.248.87.118) 172.990 ms 180.499 ms 188.968 ms
14 54.240.242.72 (54.240.242.72) 180.318 ms 175.488 ms 179.525 ms
15 54.240.242.75 (54.240.242.75) 179.627 ms 178.025 ms 176.370 ms
16 * * *
17 52.93.128.42 (52.93.128.42) 290.625 ms 204.033 ms 200.386 ms
18 54.239.46.106 (54.239.46.106) 190.005 ms 195.335 ms 189.590 ms
19 * * *
20 * 52.93.12.234 (52.93.12.234) 232.349 ms *
21 52.93.12.213 (52.93.12.213) 185.597 ms 190.278 ms 184.052 ms
22 52.93.12.140 (52.93.12.140) 199.020 ms 217.830 ms 208.764 ms
23 52.93.12.171 (52.93.12.171) 201.082 ms * 272.325 ms
24 52.93.240.37 (52.93.240.37) 187.031 ms 211.700 ms 187.318 ms
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
31 * * *
32 * * *
33 * * *
34 * * *
35 * * *
36 * * *
37 * * *
38 * * *
39 * * *
40 * * *
41 * * *
42 * * *
43 * * *
44 * * *
45 * * *
46 * * *
47 * * *
48 * * *
49 * * *
50 * * *
51 * * *
52 * * *
53 * * *
54 * * *
55 * * *
56 * * *
57 * * *
58 * * *
59 * * *
60 * * *
61 * * *
62 * * *
63 * * *
64 * * *

Thanks, I appreciate it! Anyone else? Ideally I’d like at least one report from someone who does have a VPN and confirm that turning it on fixes it, while turning it off causes the issues again.

Hi, working from Warsaw, Poland like always. All day good for me and I was working since morning today.

Cheers!

Still having issues in London (no VPN), both test and live versions :frowning:

Can you do a traceroute too please? I still want one from someone who’s confirmed that VPN fixes it, but even without that I’d like to see how yours compares with andrew1’s.

How do I do that?

@josh

Follow the instructions here: https://support.cloudflare.com/hc/en-us/articles/200169336-How-do-I-run-a-traceroute- . You should get output that looks like what andrew1 posted above.

Please see below.

Josh, overall slowness is a big deal. Just saying. I am not your biggest user, but at this rate of improvement, I must think of options as currently I am not convinced that if my app hits a jack pot I will be able to keep up performance without users just leaving.

Traceroute has started…

traceroute to bubble.is (54.69.164.32), 64 hops max, 72 byte packets
1 192.168.0.1 (192.168.0.1) 33.954 ms 2.917 ms 2.872 ms
2 * * *
3 bmly-core-2b-xe-230-0.network.virginmedia.net (80.1.224.93) 13.506 ms 12.310 ms 11.054 ms
4 * * *
5 m686-mp2.cvx1-b.lis.dial.ntli.net (62.254.42.174) 18.237 ms 14.208 ms 11.919 ms
6 213.46.174.118 (213.46.174.118) 14.876 ms 32.133 ms 17.198 ms
7 ldn-bb3-link.telia.net (62.115.134.134) 181.862 ms 176.862 ms 175.753 ms
8 nyk-bb3-link.telia.net (62.115.135.94) 131.282 ms 113.500 ms 107.665 ms
9 sjo-b21-link.telia.net (213.155.130.129) 172.136 ms 175.808 ms 172.285 ms
10 a100row-ic-300117-sjo-b21.c.telia.net (213.248.87.118) 173.917 ms 178.280 ms 190.083 ms
11 54.240.242.152 (54.240.242.152) 169.838 ms 174.556 ms 174.005 ms
12 54.240.242.161 (54.240.242.161) 169.548 ms 173.561 ms 208.697 ms
13 * * *
14 52.93.128.36 (52.93.128.36) 202.434 ms 186.540 ms 185.394 ms
15 54.239.46.104 (54.239.46.104) 185.960 ms 188.203 ms *
16 * * *
17 52.93.12.78 (52.93.12.78) 229.268 ms 197.265 ms 226.879 ms
18 52.93.12.71 (52.93.12.71) 189.624 ms 189.048 ms 195.242 ms
19 * 52.93.12.34 (52.93.12.34) 221.063 ms 207.990 ms
20 52.93.12.57 (52.93.12.57) 186.974 ms 186.938 ms 199.807 ms
21 54.239.48.183 (54.239.48.183) 250.184 ms 184.281 ms 186.317 ms
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
31 * * *
32 * * *
33 * * *
34 * * *
35 * * *
36 * * *
37 * * *
38 * * *
39 * * *
40 * * *
41 * * *
42 * * *
43 * * *
44 * * *
45 * * *
46 * * *
47 * * *
48 * * *
49 * * *
50 * * *
51 * * *
52 * * *
53 * * *
54 * * *
55 * * *
56 * * *
57 * * *
58 * * *
59 * * *
60 * * *
61 * * *
62 * * *
63 * * *
64 * * *

Hey @josh, I still have the same problem if I get rid of the VPN (I’m in The Netherlands, by the way). The result from the traceroute to bubble.is is as follows:

Traceroute se ha iniciado…

traceroute to bubble.is (54.69.164.32), 64 hops max, 72 byte packets
 1  * * 192.168.0.1 (192.168.0.1)  374.829 ms
 2  a62001.upc-a.chello.nl (62.163.62.1)  20.566 ms * *
 3  * * *
 4  asd-tr0021-cr101-bundle-ether111-1.aorta.net (84.116.244.121)  348.214 ms  75.419 ms  38.440 ms
 5  * * *
 6  nl-ams14a-ri1-ae5-0.aorta.net (84.116.135.34)  200.117 ms  117.260 ms  131.595 ms
 7  be3065.ccr41.ams03.atlas.cogentco.com (130.117.14.1)  141.976 ms  13.208 ms  14.100 ms
 8  be12194.ccr41.lon13.atlas.cogentco.com (154.54.56.93)  123.135 ms  124.703 ms  124.702 ms
 9  be2982.ccr31.bos01.atlas.cogentco.com (154.54.1.117)  145.450 ms  164.428 ms  189.517 ms
10  be3599.ccr21.alb02.atlas.cogentco.com (66.28.4.237)  233.623 ms  151.044 ms  185.108 ms
11  be2878.ccr21.cle04.atlas.cogentco.com (154.54.26.129)  472.338 ms  124.455 ms  156.928 ms
12  be2717.ccr41.ord01.atlas.cogentco.com (154.54.6.221)  127.644 ms  124.451 ms  149.225 ms
13  be2831.ccr21.mci01.atlas.cogentco.com (154.54.42.165)  246.988 ms  172.131 ms  152.500 ms
14  be3035.ccr21.den01.atlas.cogentco.com (154.54.5.89)  212.843 ms  146.986 ms  148.906 ms
15  be3037.ccr21.slc01.atlas.cogentco.com (154.54.41.145)  191.486 ms  198.970 ms  170.567 ms
16  be3110.ccr22.sfo01.atlas.cogentco.com (154.54.44.141)  170.047 ms  181.019 ms  193.667 ms
17  be3670.ccr41.sjc03.atlas.cogentco.com (154.54.43.14)  206.775 ms  206.094 ms  240.044 ms
18  38.88.224.186 (38.88.224.186)  183.516 ms  165.092 ms  191.875 ms
19  52.93.70.178 (52.93.70.178)  207.743 ms  213.784 ms  196.080 ms
20  54.240.242.35 (54.240.242.35)  209.164 ms  292.642 ms  173.914 ms
21  * * *
22  54.239.43.40 (54.239.43.40)  245.128 ms  284.530 ms  228.609 ms
23  54.239.45.127 (54.239.45.127)  189.588 ms  263.883 ms  220.920 ms
24  * * *
25  52.93.12.40 (52.93.12.40)  184.861 ms  184.561 ms  187.214 ms
26  52.93.12.35 (52.93.12.35)  185.678 ms  184.496 ms  184.113 ms
27  52.93.12.70 (52.93.12.70)  184.917 ms  189.743 ms  208.750 ms
28  52.93.12.99 (52.93.12.99)  226.684 ms  226.558 ms  218.467 ms
29  52.93.240.21 (52.93.240.21)  205.035 ms  518.911 ms  322.238 ms
30  * * *
31  * * *
32  * * *
33  * * *
34  * * *
35  * * *
36  * * *
37  * * *
38  * * *
39  * * *
40  * * *
41  * * *
42  * * *
43  * * *
44  * * *
45  * * *
46  * * *
47  * * *
48  * * *
49  * * *
50  * * *
51  * * *
52  * * *
53  * * *
54  * * *
55  * * *
56  * * *
57  * * *
58  * * *
59  * * *
60  * * *

Hope it’s insightful!

Thanks guys, I’m talking to our infrastructure providers and will let you know if there are updates

2 Likes

They’re still investigating on their end. At this point I’m not expecting an answer until tomorrow morning US time, although I think the odds of this clearing up over night are pretty good, because generally any networking issue that can be worked around via VPN touches low-level public infrastructure that gets regularly managed. I’m going to leave the status message up for now; if you see this clear up on your end, please let me know.

Hi @josh

Speed-wise, things seem to be back to normal, and no error messages yet.

AWS confirmed that is looks like an issue with certain European carriers, but it seems to be mostly resolved. I’m taking down the status page notification for now – please submit a bug report (or reply to yours if you opened one already) if you’re still seeing issues.

4 Likes

Thanks for the info, @josh!

This topic was automatically closed after 14 days. New replies are no longer allowed.