Trying to get on the forum and using wind is a mission these days sometimes it does not even load and when it does it is slooooow and the other day landed on a nginx page or something the same goes for wind
The nginx page was a problem on the forum which I fixed. The slow loading could be anything. If it happens again post a trace from your RB to the forum. I suspect you are too far from your nearest break-out or that the route between you and forum is congested. Especially outside gametime.
ok here is a trace outside gametime but even in gametime it is slow or not loading at all will post traces from rb later out and in gametime
EDIT: Here is a trace i have done now 16:04 to the forum will do one later in gametime
And then to wind also 16:12 will do one later in gametime
Tracing route to reaction.ctwug.za.net [172.18.1.13]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms rb.sparkie-2.ctwug.za.net [172.26.178.22]
2 3 ms 5 ms 5 ms rb1.pine.ctwug.za.net [172.26.178.1]
3 18 ms 6 ms 5 ms rb2.pine.ctwug.za.net [172.26.178.2]
4 27 ms 4 ms 4 ms 172.26.178.253
5 43 ms 160 ms 18 ms ub1.anubis.ctwug.za.net [172.26.132.226]
6 26 ms 9 ms 6 ms anubis-german-rb8.anubis.ctwug.za.net [172.26.13
2.245]
7 6 ms 15 ms 14 ms link-anubis.german.ctwug.za.net [172.26.132.214]
8 8 ms 19 ms 13 ms german-gekido.german.ctwug.za.net [172.26.128.24
7]
9 32 ms 32 ms 32 ms link-german.gekido.ctwug.za.net [172.26.130.73]
10 35 ms 35 ms * dns.gekido.ctwug.za.net [172.26.130.12]
11 * 220 ms * reaction.ctwug.za.net [172.18.1.13]
12 226 ms 179 ms * reaction.ctwug.za.net [172.18.1.13]
13 206 ms 194 ms * reaction.ctwug.za.net [172.18.1.13]
14 234 ms 233 ms 218 ms reaction.ctwug.za.net [172.18.1.13]
Trace complete.
Hi @razor1,
Try again, I resolved issue from skouperd dns server, please post updated results.
I’ll look at skouperd tunnel.
@spin does skouperd run over an Openserve line?
I know Openserve are having exchange congestion in certain areas. Maybe this might be the cause?
Don’t know. Will have a look tonight and disable it if we can’t get it working.
Both tunnels dns.puck and dns.skouperd had poor connectivity internationally. Looks like the same upstream provider. Disabled both of these for now. @JellyBean / @Skouperd
Thanks @spin, I have logged a call for it.
@MDE, it is an Openserve line 
1 month 10 days to go until new fibre line provider 
what is happening to the wug these days nothing is working properly been getting yellow faces and can’t even load wind or the forum
We are busy trying to sort out the issues at skouperd, have disabled the DNS server there for now.








