Issues with connectivity to hosted Discourse instances

support
1

For the past 36 hours I’ve been having issues reading some of the hosted Discourse forums. I noticed that other people do not have this problem and that I can connect fine if I connect through a VPN exit node, so it’s something specific to my location or ISP, but it’s very annoying.

I browse the internals.rust-lang.org instance almost every day and noticed yesterday that it didn’t load for me. Similar for users.rust-lang.org and community.letsencrypt.org. discourse.julialang.org seems to work, albeit slowly, and this site works fine. DNS resolves quite quickly, to 184.105.176.44. My current IP is 82.174.246.87 (but ip.discourse.org won’t load for me) – my ISP is T-Mobile.

djc-2021 ~ $ sudo mtr -c 10 -r -z internals.rust-lang.org
Start: 2022-02-11T23:26:49+0100
HOST: djc-2021                    Loss%   Snt   Last   Avg  Best  Wrst StDev
  1. AS???    router               0.0%    10    7.0   3.8   2.2   7.0   1.7
  2. AS???    192.168.0.1          0.0%    10    4.3   4.4   3.0   7.5   1.4
  3. AS50266  1-81-132-5.ftth.gla 40.0%    10   14.2  14.5  11.2  23.3   4.5
  4. AS???    10.10.12.81         40.0%    10   11.4  13.8  11.4  18.0   2.7
  5. AS???    ???                 100.0    10    0.0   0.0   0.0   0.0   0.0
  6. AS???    ???                 100.0    10    0.0   0.0   0.0   0.0   0.0
  7. AS???    ???                 100.0    10    0.0   0.0   0.0   0.0   0.0
  8. AS???    ???                 100.0    10    0.0   0.0   0.0   0.0   0.0
  9. AS???    ???                 100.0    10    0.0   0.0   0.0   0.0   0.0
 10. AS???    ???                 100.0    10    0.0   0.0   0.0   0.0   0.0
 11. AS???    ???                 100.0    10    0.0   0.0   0.0   0.0   0.0
 12. AS???    ???                 100.0    10    0.0   0.0   0.0   0.0   0.0
 13. AS???    ???                 100.0    10    0.0   0.0   0.0   0.0   0.0
 14. AS6939   184.105.176.44      90.0%    10  151.4 151.4 151.4 151.4   0.0

Any clues as to what might be going on?

(I noticed that I started a similar thread in April 2020.)

2 Likes
2

Any ideas @supermathie for him to check?

3

Looking at your previous topic, that time you had trouble getting to AWS whereas this time it’s to two of our networks.

julia and rust are both hosted in the US, whereas meta is on AWS.

That traceroute doesn’t look good - it doesn’t seem to even get out of your ISP’s network until the end.

Here’s what it looks like in the reverse direction:

$ mtr -rzn 82.174.246.87
Start: 2022-02-14T21:22:11+0000
HOST: tieinterceptor1a            Loss%   Snt   Last   Avg  Best  Wrst StDev
  1. AS6939   64.71.144.193        0.0%    10    0.8   0.8   0.7   0.9   0.1
  2. AS6939   184.104.194.22       0.0%    10   33.3  33.2  33.1  33.3   0.1
  3. AS6939   184.105.223.177     30.0%    10   41.5  42.1  41.3  44.2   1.0
  4. AS6939   184.104.193.174      0.0%    10   57.9  57.9  57.7  58.0   0.1
  5. AS6939   72.52.92.165         0.0%    10  123.7 123.7 123.6 123.8   0.1
  6. AS6939   184.105.64.2         0.0%    10  128.4 124.6 123.9 128.4   1.3
  7. AS6939   72.52.92.214         0.0%    10  141.8 142.6 129.6 202.3  23.7
  8. AS???    80.249.211.171       0.0%    10  131.9 131.9 131.7 132.1   0.1
  9. AS???    ???                 100.0    10    0.0   0.0   0.0   0.0   0.0

We can get as far as 80.249.211.171.

80.249.211.171 is one of the interfaces on an edge router in AS50266 (your ISP - T-Mobile NL, formerly TELE2) located at the Amsterdam Internet Exchange. It’s advertising the network to which you belong (it’s saying to the world “I can get your traffic get to 82.174.0.0/16!”)

Everything looks to me like a problem within your ISP’s network - I would tentatively say that traffic getting sent to that router isn’t making it any farther, but ultimately this is something for your ISP to investigate.

Hope that helps!

2 Likes
4

Thanks for looking into it! Happily everything started working again. Next time I’ll see if I can get something useful out of my ISP’s support…

2 Likes