Forum loading and working slowly

For about 2 days, the forum has been loading and working very slowly here. I am not sure whether something is going on with my Internet connection, or the problem is with the forum itself. I have tried restarting the modem and the router, using different Web browsers, etc., but there is no difference. The forum used to load very quickly, but now it seems to take 5+ seconds to process every request.

I have done a few speed tests to check the Internet connection, but they come out normally. Other websites also seem to load as usual.

Has anyone else experienced any slowdowns, or am I the only one? :thinking:

It feels as usual for me, and I practically live here. Not always ultra snappy but I think that’s just a huge ruby on rails app being a huge ruby on rails app… Certainly no 5s+ wait times.

Hmm, that is good to know.

It used to be snappy, but suddenly became sluggish yesterday, and has stayed this way since then. Especially the very first load may take even 15 seconds or so. After that, it is usable, but still something feels off.

My experience is normal and hasn’t noticeably changed lately, so I’d say check your devices and connections.

This will probably reveal nothing of much use, but you can do a speedtest to DigitalOceans servers and check if you’re getting acceptable bandwidth and/or latency.

I think this forum (currently) runs in DigitalOcean’s AMS2 data center (at least that’s what a traceroute from my side suggests) and they have a speedtest there:

http://speedtest-ams2.digitalocean.com/

(For me only the manual test via HTTP test file download worked - compare the speeds you’re getting with the speeds you would expect from a “usual” speedtest. I was getting speeds well exceeding 200 Mbit/s, so the thing seems to be working)

If you’re getting horrible speeds, it’s probably some overloaded transit provider.

2 Likes

The speeds are not great. It is impossible to know what they had been before the slowdown though.

image

On the other hand, this is the maximum bandwidth of my home Internet connection.

image

However, the situation seems to have improved a little today. Still not as fast as it used to be, but the forum is loading quicker and responds to requests snappier than yesterday.

Something’s up with either you provider or the path you have to Digital Ocean, then. Screenshot Screenshot_20200517_075437

And I’m not in Amsterdam, not even close.

Well, I do live on the other side of the globe than Amsterdam, so I am not expecting super fast speeds or anything like that, but this is still way slower than it used to be. The previous rates were from the morning, now in the daytime it is even worse.

image

I am curious what the problem is though, as both my provider’s speed test and other popular speed tests like https://speedtest.net or https://fast.com do not have any issues. Below is a result of doing a speed test with a server located in Amsterdam (not DigitalOcean though), and everything seems normal here.

image

I’d try to traceroute and understand where on the path the problem is, then.

This is how it looks like. Also, when pinging forum.syncthing.net, there is no packet loss, so the connection is stable, just very slow.

Windows:

tracert forum.syncthing.net

Tracing route to forum.syncthing.net [37.139.7.17]
over a maximum of 30 hops:

  1     2 ms     2 ms     1 ms  10.0.0.1
  2     *        *        *     Request timed out.
  3     9 ms    10 ms     9 ms  X.X.X.X
  4     9 ms    10 ms    14 ms  X.X.X.X
  5    15 ms    10 ms    10 ms  X.X.X.X
  6     *       13 ms    13 ms  X.X.X.X
  7    16 ms    15 ms    13 ms  X.X.X.X
  8    15 ms    15 ms    15 ms  X.X.X.X
  9    14 ms    13 ms    13 ms  X.X.X.X
 10   182 ms   176 ms   186 ms  X.X.X.X
 11   185 ms   181 ms   166 ms  X.X.X.X
 12   173 ms   167 ms   177 ms  sl-mst30-la-.sprintlink.net [144.223.44.41]
 13   181 ms   177 ms   181 ms  sl-mst31-la-be5.sprintlink.net [144.232.4.129]
 14   183 ms   184 ms   183 ms  ix-ae-13-0.tcore1.eql-los-angeles.as6453.net [206.82.129.1]
 15   347 ms   347 ms   348 ms  if-ae-30-2.tcore1.lvw-los-angeles.as6453.net [206.82.129.19]
 16   322 ms   326 ms   333 ms  if-ae-60-2.tcore1.sv1-santa-clara.as6453.net [63.243.250.54]
 17   334 ms   331 ms   312 ms  if-ae-0-3.tcore2.sv1-santa-clara.as6453.net [63.243.250.61]
 18   318 ms   319 ms   315 ms  if-ae-18-2.tcore1.sqn-san-jose.as6453.net [63.243.205.72]
 19   329 ms   322 ms   317 ms  if-ae-0-2.tcore1.nto-new-york.as6453.net [63.243.128.30]
 20   319 ms   320 ms   302 ms  if-ae-18-2.tcore2.l78-london.as6453.net [80.231.131.72]
 21   312 ms   308 ms   305 ms  if-ae-14-2.tcore2.av2-amsterdam.as6453.net [80.231.131.161]
 22   319 ms   318 ms   327 ms  if-ae-11-2.tcore1.ad1-amsterdam.as6453.net [80.231.152.26]
 23     *        *        *     Request timed out.
 24   335 ms   333 ms   334 ms  138.197.244.74
 25     *        *        *     Request timed out.
 26   331 ms   324 ms   321 ms  forum.syncthing.net [37.139.7.17]

Trace complete.

Linux (Android):

traceroute forum.syncthing.net
traceroute to forum.syncthing.net(37.139.7.17), 30 hops max, 8 byte packets
 1  10.0.0.1 ( 10.0.0.1)  0.638 ms  0.573 ms  2.345 ms
 2  *  *  *
 3  X.X.X.X ( X.X.X.X)  14.649 ms  8.913 ms  9.841 ms
 4  X.X.X.X ( X.X.X.X)  10.790 ms  10.126 ms  9.023 ms
 5  X.X.X.X ( X.X.X.X)  11.326 ms  9.678 ms  11.603 ms
 6  *  *  X.X.X.X ( X.X.X.X)  18.654 ms
 7  X.X.X.X ( X.X.X.X)  12.355 ms  20.047 ms  13.382 ms
 8  X.X.X.X ( X.X.X.X)  13.939 ms  12.222 ms  44.201 ms
 9  X.X.X.X ( X.X.X.X)  16.208 ms  14.887 ms  13.230 ms
10  X.X.X.X ( X.X.X.X)  189.012 ms  186.108 ms  189.083 ms
11  X.X.X.X ( X.X.X.X)  180.441 ms  X.X.X.X ( X.X.X.X)  315.724 ms  X.X.X.X ( X.X.X.X)  184.310 ms
12  sl-mst30-la-be21.sprintlink.net ( 144.223.44.41)  186.308 ms  182.573 ms  181.882 ms
13  sl-mst31-la-be5.sprintlink.net ( 144.232.4.129)  181.815 ms  185.201 ms  181.979 ms
14  ix-ae-13-0.tcore1.eql-los-angeles.as6453.net ( 206.82.129.1)  180.981 ms  182.126 ms  189.291 ms
15  if-ae-30-2.tcore1.lvw-los-angeles.as6453.net ( 206.82.129.19)  370.892 ms  410.312 ms  407.846 ms
16  if-ae-60-2.tcore1.sv1-santa-clara.as6453.net ( 63.243.250.54)  409.084 ms  430.209 ms  404.578 ms
17  if-ae-0-3.tcore2.sv1-santa-clara.as6453.net ( 63.243.250.61)  322.028 ms  407.691 ms  408.234 ms
18  if-ae-18-2.tcore1.sqn-san-jose.as6453.net ( 63.243.205.72)  408.567 ms  407.116 ms  409.616 ms
19  if-ae-0-2.tcore1.nto-new-york.as6453.net ( 63.243.128.30)  305.024 ms  326.004 ms  388.825 ms
20  if-ae-18-2.tcore2.l78-london.as6453.net ( 80.231.131.72)  320.860 ms  302.035 ms  417.923 ms
21  if-ae-14-2.tcore2.av2-amsterdam.as6453.net ( 80.231.131.161)  407.250 ms  408.474 ms  409.451 ms
22  if-ae-11-2.tcore1.ad1-amsterdam.as6453.net ( 80.231.152.26)  406.471 ms  407.899 ms  406.766 ms
23  *  *  *
24  138.197.244.74 ( 138.197.244.74)  442.787 ms  385.285 ms  334.668 ms
25  *  *  *
26  forum.syncthing.net ( 37.139.7.17)  417.073 ms  325.721 ms  369.164 ms

@tomasz86 I don’t know if this applies to you, but I sometimes have to reboot my AVM FritzBox and I don’t know if its the hardware bug of 7490 or my provider but after a re-dialup to DSL it works much faster again then noticable by speed tests.

tracert forum.syncthing.net

Routenverfolgung zu forum.syncthing.net [37.139.7.17]
ĂĽber maximal 30 Hops:

  1    <1 ms    <1 ms    <1 ms  X.X.X.X
  2     1 ms     1 ms    <1 ms  fritz.box
  3     6 ms     5 ms     5 ms  srbfra31.as20676.net [213.148.133.235]
  4    10 ms    10 ms     9 ms  crmdus11-cg-10-0-2-0.as20676.net [87.234.14.167]
  5    10 ms    10 ms     9 ms  crmdus11-cg-10-0-2-0.as20676.net [87.234.14.167]
  6     9 ms     9 ms     9 ms  ddf-b2-link.telia.net [213.248.73.1]
  7    17 ms    17 ms    16 ms  adm-bb4-link.telia.net [62.115.143.162]
  8    17 ms    19 ms    17 ms  adm-b1-link.telia.net [62.115.137.65]
  9    16 ms    16 ms    16 ms  digitalocean-ic-335926-adm-b1.c.telia.net [213.248.81.75]
 10     *        *        *     ZeitĂĽberschreitung der Anforderung.
 11     *        *        *     ZeitĂĽberschreitung der Anforderung.
 12    19 ms    17 ms    18 ms  forum.syncthing.net [37.139.7.17]

image

1 Like

Yeah that really sounds like a transit provider/connection that is choking.

Diagnosing that is a fun thing (not really), you can try and compare traceroutes to providers in a similar region and see what routes give you slow speeds and what routes have good speeds. At some point there should be one transit provider that only appears on the slow routes - that’s the bad player.

Oh and when doing traceroutes, always remember that routing in the www is a mostly asymmetrical thing, e.g upstream route does not equal downstream route. Testing the downstream route requires a traceroute from the other side, which isn’t a trivial thing to do unless you have network access.

You can also try and talk to your local ISP, if you’re lucky they can do something. But I wouldn’t bet on it.

2 Likes

Yes, I highly doubt that they would do anything, as long as their own speed test shows no anomalies. If everything was working slowly, then it would be a different story, but right now this seems to be limited to specific servers/regions. The other websites that I use on a daily basis mostly seem to work as usual.

I have tried rebooting both the modem and the router, and also inspected the configuration, but there has been no change. When it comes to the hardware, everything seems to be working fine.