MDE
Expert Member
- Joined
- May 18, 2009
- Messages
- 2,247
Will monitor. Just curious. But ping jumping around by 10ms. Not as flat as normal.We have just moved over to our other carrier back to WACS, so resolved technically. Are you having any trouble?
Will monitor. Just curious. But ping jumping around by 10ms. Not as flat as normal.We have just moved over to our other carrier back to WACS, so resolved technically. Are you having any trouble?
CSGO servers are local so either server issues or your connection to the server. WACs is not involved in getting you to the CS sever.CSGO also has a very noticeable loss since the 'situation' or event as they have called it was restored. I will check back next week.
CSGO servers are local so either server issues or your connection to the server. WACs is not involved in getting you to the CS sever.
What's an MTR look like? I use a VPN which is located in JHB and been fine and also been playing on Apex Belgium severs which takes me to JHB and then uses Google transit... Don't really trust going via London since jitter is bad...Not WACs, the Cape Town backbone restore.
Noticing this too, looks to be multiple paths in the mix atm, seeing 140-150ms to the UK where it was usually around ~140-141 averageWill monitor. Just curious. But ping jumping around by 10ms. Not as flat as normal.
Yeah...still jumping around... definitely not as stable as before the incident.Noticing this too, looks to be multiple paths in the mix atm, seeing 140-150ms to the UK where it was usually around ~140-141 average
Yeah with WACs currently we have capacity via provider X and Wiocc, (provider X gets capacity from Wiocc but adds a layer of MPLS).Noticing this too, looks to be multiple paths in the mix atm, seeing 140-150ms to the UK where it was usually around ~140-141 average
X is making for people reaching for the XXXX.Yeah with WACs currently we have capacity via provider X and Wiocc, (provider X gets capacity from Wiocc but adds a layer of MPLS).
Provider X's contract is finished with us in September and everything will move directly to Wiocc (as it is now)
Wioccs service to us currently has two WACs paths one is "express route" IE Ysterfontein to London direct.
The other has an additional hop, more than likely via a country on the western coast, we are in the process of changing interfaces and the service with Wiocc which will then only use the express route. So is a temporary thing we need to deal with![]()
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 0 | 157 | 157 | 0 | 0 | 4 | 0 |
| No response from host - 100 | 32 | 0 | 0 | 0 | 0 | 0 |
| c25-backbone.coolideas.co.za - 2 | 149 | 147 | 146 | 151 | 172 | 155 |
| c2e-backbone.coolideas.co.za - 2 | 149 | 147 | 143 | 150 | 153 | 146 |
| c2t-backbone.coolideas.co.za - 1 | 153 | 152 | 143 | 150 | 156 | 145 |
| c1h-backbone.coolideas.co.za - 0 | 157 | 157 | 141 | 150 | 198 | 147 |
| pch.ixp.durban - 1 | 153 | 152 | 142 | 158 | 465 | 144 |
| dns9.quad9.net - 1 | 153 | 152 | 141 | 151 | 174 | 149 |
|________________________________________________|______|______|______|______|______|______|
Will you log it for me? And give me the ref@PBCool My connection has been rocky for the past few evenings and last night it was fine but tonight it's extremely bad.
The upload speed is normal but the download speed and latency is very bad, but I don't seem to have much packet loss strangely. This only happens in the evenings for some reason which makes me think that Openserve might be congested in my area.
I'm on 100Mbps Openserve fibre in KZN. I checked the announcements and didn't see anything relating to my area.
Speedtest:
View attachment 902044
MTR:
Code:|------------------------------------------------------------------------------------------| | WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | 192.168.1.1 - 0 | 157 | 157 | 0 | 0 | 4 | 0 | | No response from host - 100 | 32 | 0 | 0 | 0 | 0 | 0 | | c25-backbone.coolideas.co.za - 2 | 149 | 147 | 146 | 151 | 172 | 155 | | c2e-backbone.coolideas.co.za - 2 | 149 | 147 | 143 | 150 | 153 | 146 | | c2t-backbone.coolideas.co.za - 1 | 153 | 152 | 143 | 150 | 156 | 145 | | c1h-backbone.coolideas.co.za - 0 | 157 | 157 | 141 | 150 | 198 | 147 | | pch.ixp.durban - 1 | 153 | 152 | 142 | 158 | 465 | 144 | | dns9.quad9.net - 1 | 153 | 152 | 141 | 151 | 174 | 149 | |________________________________________________|______|______|______|______|______|______|
Should I log it through the CoolZone?Will you log it for me? And give me the ref
Yeah that's fineShould I log it through the CoolZone?
Here: #COOL-20200829-501566Yeah that's fine![]()
Can you run a trace route when this happens?View attachment 902086
The speed seems back to normal but the ping is still very high.
The ping will usually slowly go back down to normal values as it gets later in the night when this happens, which is why I say it's likely some sort of congestion.
Anyway, I hope Openserve will acknowledge it since I know that getting through to them with this kind of stuff can be a bit of a mission.
Ok it's still not quite back to normal, it's supposed to be around 3 to 6ms on the first hop.Can you run a trace route when this happens?
1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 14 ms 12 ms 14 ms c25-backbone.coolideas.co.za [154.0.1.77]
4 13 ms 10 ms 10 ms c2e-backbone.coolideas.co.za [154.0.1.86]
5 13 ms 10 ms 10 ms c2t-backbone.coolideas.co.za [154.0.1.101]
6 12 ms 11 ms 11 ms c1h-backbone.coolideas.co.za [154.0.1.53]
7 13 ms 11 ms 10 ms uuu-cust.coolideas.co.za [154.0.4.86]
8 20 ms 19 ms 20 ms c6t-backbone.coolideas.co.za [154.0.1.245]
9 21 ms 19 ms 19 ms 100.99.0.180
10 23 ms 23 ms 22 ms google.jinx.net.za [196.223.14.41]
11 23 ms 22 ms 23 ms 74.125.245.193
12 23 ms 22 ms 23 ms 172.253.65.253
13 22 ms 25 ms 23 ms dns.google [8.8.8.8]
Does your router have the ability to show interface usage? You sure there isn't any other traffic?Ok it's still not quite back to normal, it's supposed to be around 3 to 6ms on the first hop.
Code:1 <1 ms <1 ms <1 ms 192.168.1.1 2 * * * Request timed out. 3 14 ms 12 ms 14 ms c25-backbone.coolideas.co.za [154.0.1.77] 4 13 ms 10 ms 10 ms c2e-backbone.coolideas.co.za [154.0.1.86] 5 13 ms 10 ms 10 ms c2t-backbone.coolideas.co.za [154.0.1.101] 6 12 ms 11 ms 11 ms c1h-backbone.coolideas.co.za [154.0.1.53] 7 13 ms 11 ms 10 ms uuu-cust.coolideas.co.za [154.0.4.86] 8 20 ms 19 ms 20 ms c6t-backbone.coolideas.co.za [154.0.1.245] 9 21 ms 19 ms 19 ms 100.99.0.180 10 23 ms 23 ms 22 ms google.jinx.net.za [196.223.14.41] 11 23 ms 22 ms 23 ms 74.125.245.193 12 23 ms 22 ms 23 ms 172.253.65.253 13 22 ms 25 ms 23 ms dns.google [8.8.8.8]
100% sure. I tested with my PC being the only cabled device connected to it and the WiFi on the router was disabled.Does your router have the ability to show interface usage? You sure there isn't any other traffic?
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 0 | 102 | 102 | 0 | 0 | 1 | 0 |
| No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 |
| c25-backbone.coolideas.co.za - 2 | 98 | 97 | 3 | 5 | 21 | 5 |
| c2e-backbone.coolideas.co.za - 0 | 102 | 102 | 3 | 4 | 6 | 4 |
| c2t-backbone.coolideas.co.za - 0 | 102 | 102 | 3 | 4 | 6 | 5 |
| c1h-backbone.coolideas.co.za - 0 | 102 | 102 | 2 | 3 | 9 | 4 |
| 196-10-141-198.ixp.durban - 0 | 102 | 102 | 4 | 6 | 30 | 4 |
| one.one.one.one - 0 | 102 | 102 | 3 | 4 | 11 | 4 |
|________________________________________________|______|______|______|______|______|______|