Forums slow to load.

[#1]

I have to admit I have also noticed a degradation in service as far as this forum is concerned. It is noticeably slower to load than it has been in the past, and has been like this for many days now.

[#2]

---

@jaread83 wrote:

Lithium have not found any anomalies with the platform so far. I have checked on my home connection (100mb fibre from Virgin Media) and my 4G (Three) phone connection on my iPhone and it loads pretty quickly for me.

---

Well that's ok then. It must be fine and dandy. I'll just tell it to stop messing about and load faster.

[#3]

It's still being looked at, we aren't brushing this to one side just yet.

[#4]

---

@jaread83 wrote:

... we aren't brushing this to one side just yet.

---

@jaread83 - Your wording does imply that it will be brushed to one side at some point!

[#5]

oops, that wasn't my intention

I am looking into it and will post updates here when any come to light.

[#6]

Just to be clear waiting a few seconds longer, than other forums, to load isn't a problem as it does load.

Curious to the why that's all.

[#7]

For anyone having issues with the slow loading of the forums, can I ask that you provide a screenshot/copy of a TRACERT report? This is so Lithium can have a look and diagnose.

To do this, on Mac open Terminal and type

traceroute community.plus.net

For Windows users, open the CMD prompt and type (link to MS help article)

tracert community.plus.net

It should provide you with details about the connection from your computer to the community and will help us understand why you are getting slow loading times.

If you can post a screenshot of the results or insert into a code block that would be very helpful.

If you don't feel comfortable posting your report here publicly, send me a PM with those details and i will pass them on to Lithium.

[#8]

jaread83  here you go

[#9]

Here's another one for you @jaread83.

iMac:~ Mook$ traceroute community.plus.net
traceroute to aptgm87544.lithium.com (46.19.168.229), 64 hops max, 52 byte packets
 1  vigor.router (192.168.0.1)  0.361 ms  0.152 ms  0.146 ms
 2  lo0.12.central12.pcl-bng01.plus.net (195.166.130.140)  16.544 ms  17.951 ms  16.446 ms
 3  irb.12.pcl-cr01.plus.net (84.93.249.113)  16.600 ms  16.951 ms
    irb.12.pcl-cr02.plus.net (84.93.249.114)  18.678 ms
 4  195.99.126.96 (195.99.126.96)  17.052 ms
    195.99.126.98 (195.99.126.98)  17.530 ms  17.519 ms
 5  core3-te0-9-0-26.faraday.ukcore.bt.net (109.159.249.51)  18.788 ms
    core3-te0-10-0-27.faraday.ukcore.bt.net (109.159.249.181)  17.268 ms
    core4-te0-12-0-18.faraday.ukcore.bt.net (109.159.249.17)  19.269 ms
 6  213.121.193.195 (213.121.193.195)  17.423 ms
    peer1-xe0-0-2.faraday.ukcore.bt.net (213.121.193.185)  17.509 ms
    peer1-xe0-0-1.faraday.ukcore.bt.net (213.121.193.193)  18.660 ms
 7  166-49-211-234.eu.bt.net (166.49.211.234)  17.712 ms
    166-49-211-232.eu.bt.net (166.49.211.232)  18.140 ms
    t2c4-et-3-1-0-0.uk-lon1.eu.bt.net (166.49.211.244)  17.653 ms
 8  hu0-1-0-0.ccr22.lon01.atlas.cogentco.com (130.117.14.229)  17.432 ms  17.239 ms  17.455 ms
 9  be2869.ccr42.lon13.atlas.cogentco.com (154.54.57.161)  18.063 ms
    be2870.ccr41.lon13.atlas.cogentco.com (154.54.58.173)  17.438 ms
    be2869.ccr42.lon13.atlas.cogentco.com (154.54.57.161)  17.993 ms
10  be12488.ccr42.ams03.atlas.cogentco.com (130.117.51.42)  25.784 ms  25.540 ms
    be12194.ccr41.ams03.atlas.cogentco.com (154.54.56.94)  25.663 ms
11  be2447.rcr21.b021535-1.ams03.atlas.cogentco.com (130.117.50.250)  26.761 ms
    be2322.rcr21.b021535-1.ams03.atlas.cogentco.com (130.117.50.82)  25.655 ms
    be2447.rcr21.b021535-1.ams03.atlas.cogentco.com (130.117.50.250)  26.199 ms
12  149.6.129.194 (149.6.129.194)  25.360 ms  25.155 ms  25.617 ms
13  aptgm87544.lithium.com (46.19.168.229)  25.501 ms  25.828 ms  26.046 ms

[#10]

Tracing route to aptgm87544.lithium.com [46.19.168.229]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     *        *        *     Request timed out.
  3     5 ms     5 ms     4 ms  lo0-central10.ptn-ag03.plus.net [195.166.128.192]
  4     5 ms     5 ms     4 ms  link-a-central10.ptn-gw01.plus.net [212.159.2.136]
  5     5 ms     4 ms     4 ms  xe-5-3-0.ptw-cr01.plus.net [212.159.0.108]
  6     4 ms     4 ms     4 ms  195.99.126.138
  7     6 ms     7 ms     7 ms  core1-te0-0-0-11.ilford.ukcore.bt.net [109.159.254.123]
  8     6 ms     6 ms     6 ms  109.159.255.105
  9     5 ms     5 ms     5 ms  166-49-211-232.eu.bt.net [166.49.211.232]
 10     6 ms     6 ms     6 ms  hu0-1-0-0.ccr22.lon01.atlas.cogentco.com [130.117.14.229]
 11     6 ms     6 ms     5 ms  be2869.ccr42.lon13.atlas.cogentco.com [154.54.57.161]
 12    14 ms    13 ms    14 ms  be12488.ccr42.ams03.atlas.cogentco.com [130.117.51.42]
 13    15 ms    14 ms    14 ms  be2447.rcr21.b021535-1.ams03.atlas.cogentco.com [130.117.50.250]
 14    13 ms    13 ms    13 ms  149.6.129.194
 15    13 ms    13 ms    13 ms  aptgm87544.lithium.com [46.19.168.229]

Trace complete.

[#11]

Thanks @Anonymous, @rongtw and @SpendLessTime

@rongtw, there was no report in your post? My bad, its an image attachment

[#12]

There is @jaread83 look at the attached image.

[#13]

Ah ha, missed that!

Thanks for the reports, I have passed this over to Lithium so they can have a look.

[#14]

And one from me...

C:\WINDOWS\system32>tracert community.plus.net

Tracing route to aptgm87544.lithium.com [46.19.168.229]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  PNHUB1 [192.168.1.254]
  2    36 ms    14 ms    12 ms  lo0-central10.pcl-ag08.plus.net [195.166.128.189]
  3    11 ms    12 ms    11 ms  link-b-central10.pcl-gw02.plus.net [212.159.2.190]
  4    12 ms    12 ms    12 ms  xe-9-1-0.pcl-cr02.plus.net [212.159.0.222]
  5    13 ms    13 ms    12 ms  195.99.126.98
  6    13 ms    12 ms    12 ms  core4-te0-19-0-27.faraday.ukcore.bt.net [109.159.255.203]
  7    13 ms    13 ms    12 ms  213.121.193.195
  8    14 ms    13 ms    13 ms  t2c4-et-8-1-0-0.uk-lon1.eu.bt.net [166.49.211.248]
  9    12 ms    13 ms    13 ms  hu0-1-0-0.ccr22.lon01.atlas.cogentco.com [130.117.14.229]
 10    13 ms    13 ms    13 ms  be2870.ccr41.lon13.atlas.cogentco.com [154.54.58.173]
 11    21 ms    20 ms    21 ms  be12194.ccr41.ams03.atlas.cogentco.com [154.54.56.94]
 12    21 ms    21 ms    21 ms  be2322.rcr21.b021535-1.ams03.atlas.cogentco.com [130.117.50.82]
 13    20 ms    20 ms    20 ms  149.6.129.194
 14    21 ms    21 ms    21 ms  aptgm87544.lithium.com [46.19.168.229]

Trace complete.

As an aside Flagfox puts the Community in The Netherlands

[#15]

For completeness - this one is mine:

jread:~ $ traceroute community.plus.net
traceroute to aptgm87544.lithium.com (46.19.168.229), 64 hops max, 52 byte packets
 1  10.3.3.253 (10.3.3.253)  0.678 ms  0.390 ms  0.368 ms
 2  10.0.3.3 (10.0.3.3)  0.688 ms  0.559 ms  0.579 ms
 3  vlan380.pbs-cr01.plus.net (84.93.216.88)  0.939 ms  0.881 ms  0.896 ms
 4  gi6-8.ptp-cr01.plus.net (84.93.216.95)  1.231 ms  1.323 ms  1.843 ms
 5  gi1-22.pcl-gw01.plus.net (84.93.224.49)  7.318 ms  8.020 ms  7.254 ms
 6  ae3.pcl-cr01.plus.net (195.166.129.40)  6.980 ms  6.999 ms  6.943 ms
 7  195.99.126.96 (195.99.126.96)  7.537 ms  7.501 ms  9.151 ms
 8  core4-te0-9-0-19.faraday.ukcore.bt.net (109.159.249.15)  7.727 ms
    core3-te0-12-0-19.faraday.ukcore.bt.net (109.159.249.31)  8.465 ms
    core3-te0-9-0-18.faraday.ukcore.bt.net (109.159.249.33)  7.711 ms
 9  peer1-xe-11-0-0.faraday.ukcore.bt.net (213.121.193.169)  9.387 ms  8.326 ms
    peer1-xe0-0-2.faraday.ukcore.bt.net (213.121.193.185)  7.925 ms
10  t2c4-et-3-1-0-0.uk-lon1.eu.bt.net (166.49.211.244)  7.839 ms
    166-49-211-234.eu.bt.net (166.49.211.234)  8.260 ms  7.956 ms
11  hu0-1-0-0.ccr22.lon01.atlas.cogentco.com (130.117.14.229)  8.150 ms  8.164 ms  8.293 ms
12  be2870.ccr41.lon13.atlas.cogentco.com (154.54.58.173)  9.905 ms  8.221 ms  8.948 ms
13  be12488.ccr42.ams03.atlas.cogentco.com (130.117.51.42)  15.612 ms  15.960 ms
    be12194.ccr41.ams03.atlas.cogentco.com (154.54.56.94)  16.338 ms
14  be2447.rcr21.b021535-1.ams03.atlas.cogentco.com (130.117.50.250)  16.033 ms  16.931 ms  16.368 ms
15  149.6.129.194 (149.6.129.194)  15.707 ms  15.511 ms  15.856 ms
16  aptgm87544.lithium.com (46.19.168.229)  16.199 ms  19.926 ms  15.735 ms

Hopefully Lithium will be able to identify whats going on from this information. Will keep you all posted when I get some updates.