There is definitely something wrong with their routing. I was battling to use Postman, which was half-working but timing out and couldn't load requests, and after two days of back-and-forth with Postman support I was eventually able to get an address that I could show wasn't working - go.pstmn.io. This address is reachable over every other network I've tried except MTS.

View attachment 1722809

I logged a support request with them on Thu which they said would be handled by the core network team, but haven't heard anything. This has really impacted my work this week. Are your problems resolved?
Hi @Spoed

Hope you are well,

I have looked into your ticket that is with the support team this matter is being dealt with our core network team, However this issue of yours with the address go.pstmn.io. has been logged with the company of this server postman.com As we can see the go.pstmn.io redirects to https://identity.getpostman.com.

I will get the support team to provide you with an update on your ticket shortly
 
I'm getting ping issues (300ms+) and disconnect issues with the Overwatch EU servers. I assumed it was an undersea cable thing but it's been going for weeks if not months. And some days it's much worse than others.

Based in Cape Town. Vumatel. PC connected via ethernet.

ping.jpgping plot.jpg
 
getting about 180ms (here from JHB) (not with Mind the speed)

Code:
Keys:  Help   Display mode   Restart statistics   Order of fields   quit
                                                                               Packets               Pings
 Host                                                                        Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. .mshome.net                                                    0.0%    41    0.8   0.6   0.4   0.9   0.1
 2. router.lan                                                                0.0%    41    1.7   1.8   1.4   2.2   0.2
 3. spe-01-tjb-ftx-gig-1-0-xdsl.co.za                                         0.0%    41    3.5   5.1   2.3  29.4   4.7
 4. core-01-tjhb1-gig-5-1-6-0-xdsl.co.za                                      0.0%    41   46.8   7.4   2.9  46.8   8.9
 5. core-01-lon-gig-2-1-1-0-xdsl.co.za                                        0.0%    41    3.6   7.5   2.2  39.5   8.9
 6. 197.157.64.82                                                             0.0%    41    3.9   4.8   3.0  19.1   3.5
 7. cr1-lhx-et42.wolcomm.net                                                  0.0%    41  160.4 475.0 159.9 2679. 660.0
 8. cr1-amx-et48.wolcomm.net                                                  0.0%    41  160.4 588.3 159.7 2566. 722.7
 9. 41.78.188.1                                                               0.0%    41  171.3 179.2 168.1 306.4  22.2
10. 41.78.188.50                                                              0.0%    41  170.9 177.1 168.8 273.4  17.1
11. cr2-umh-et48.wolcomm.net                                                  0.0%    41  168.2 170.6 167.7 186.8   5.0
12. cr1-umh-et49-1.wolcomm.net                                                0.0%    41  168.1 168.8 167.2 183.6   2.6
13. 195.66.226.234                                                            0.0%    41  171.5 174.5 168.3 211.2   9.2
14. ae1-br01-eqld5.as57976.net                                                0.0%    41  382.8 288.4 183.2 388.4  61.9
15. (waiting for reply)
16. (waiting for reply)
17. et-0-0-1-pe02-eqam3.as57976.net                                           2.4%    41  181.4 177.3 173.9 195.8   5.4
18. (waiting for reply)

edit - well difficult to say, last hope is ICMP blocked ?
 
getting about 180ms (here from JHB) (not with Mind the speed)

Code:
Keys:  Help   Display mode   Restart statistics   Order of fields   quit
                                                                               Packets               Pings
 Host                                                                        Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. .mshome.net                                                    0.0%    41    0.8   0.6   0.4   0.9   0.1
 2. router.lan                                                                0.0%    41    1.7   1.8   1.4   2.2   0.2
 3. spe-01-tjb-ftx-gig-1-0-xdsl.co.za                                         0.0%    41    3.5   5.1   2.3  29.4   4.7
 4. core-01-tjhb1-gig-5-1-6-0-xdsl.co.za                                      0.0%    41   46.8   7.4   2.9  46.8   8.9
 5. core-01-lon-gig-2-1-1-0-xdsl.co.za                                        0.0%    41    3.6   7.5   2.2  39.5   8.9
 6. 197.157.64.82                                                             0.0%    41    3.9   4.8   3.0  19.1   3.5
 7. cr1-lhx-et42.wolcomm.net                                                  0.0%    41  160.4 475.0 159.9 2679. 660.0
 8. cr1-amx-et48.wolcomm.net                                                  0.0%    41  160.4 588.3 159.7 2566. 722.7
 9. 41.78.188.1                                                               0.0%    41  171.3 179.2 168.1 306.4  22.2
10. 41.78.188.50                                                              0.0%    41  170.9 177.1 168.8 273.4  17.1
11. cr2-umh-et48.wolcomm.net                                                  0.0%    41  168.2 170.6 167.7 186.8   5.0
12. cr1-umh-et49-1.wolcomm.net                                                0.0%    41  168.1 168.8 167.2 183.6   2.6
13. 195.66.226.234                                                            0.0%    41  171.5 174.5 168.3 211.2   9.2
14. ae1-br01-eqld5.as57976.net                                                0.0%    41  382.8 288.4 183.2 388.4  61.9
15. (waiting for reply)
16. (waiting for reply)
17. et-0-0-1-pe02-eqam3.as57976.net                                           2.4%    41  181.4 177.3 173.9 195.8   5.4
18. (waiting for reply)

edit - well difficult to say, last hope is ICMP blocked ?
185.60.112.157 is the blizzard IP to test to that runs the full route. OP's router looks problematic for starters
 
FYI - 184ms from KZN , you also try the MTS looking glass portal - https://lg.mindthespeed.co.za/ I checked from Joburg on looking glass portal and was getting 162ms from Joburg. Also think maybe a LAN issue with first hop so high .
 
Thanks for the replies everyone.

The first hop issue could a powerline ethernet thing. It's usually not that bad, and mostly better than wifi.

I don't pretend to understand these things, so correct me if I'm wrong. But surely an extra 30ms on the first hop doesn't explain me getting 250-300ms in-game when I used to get 170ms with the same setup? It seems to vary day to day with a trend of getting worse over the last few months.

Here's another plot using the IP that CrypticZA suggested:

ping plot.jpg

edit: And with in-game latency around 280ms

ping.jpg

further edit: Here's a tracert from CMD. I might be reading it wrong, but it seems the latency is from well outside of my own network and this an ISP/routing issue?

tracert 185.60.112.157

Tracing route to 185.60.112.157 over a maximum of 30 hops

1 1 ms 1 ms 1 ms 192.168.0.1
2 4 ms 11 ms 65 ms 192-145-136-129.as328596.net [192.145.136.129]
3 5 ms 2 ms 3 ms 105-68-148-197.as37497.za.net [197.148.68.105]
4 13 ms 27 ms 2 ms 192-145-128-82.as328596.net [192.145.128.82]
5 2 ms 1 ms 5 ms 21-68-148-197.as37497.za.net [197.148.68.21]
6 141 ms 144 ms 141 ms 85-71-148-197.as37497.za.net [197.148.71.85]
7 285 ms 251 ms 249 ms 195.66.226.234
8 405 ms * * ae1-br01-eqld5.as57976.net [137.221.79.33]
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 250 ms 261 ms 250 ms et-0-0-1-pe01-eqam3.as57976.net [137.221.78.55]
14 249 ms 249 ms 250 ms 185.60.112.157

Trace complete.
 
Last edited:
Thanks for the replies everyone.

The first hop issue could a powerline ethernet thing. It's usually not that bad, and mostly better than wifi.

I don't pretend to understand these things, so correct me if I'm wrong. But surely an extra 30ms on the first hop doesn't explain me getting 250-300ms in-game when I used to get 170ms with the same setup? It seems to vary day to day with a trend of getting worse over the last few months.

Here's another plot using the IP that CrypticZA suggested:

View attachment 1723771

edit: And with in-game latency around 280ms

View attachment 1723777

further edit: Here's a tracert from CMD. I might be reading it wrong, but it seems the latency is from well outside of my own network and this an ISP/routing issue?
Your problem IP seems to be this as the latency jump starts there
195.66.226.234, with a 100ms increase
 
Thanks for the replies everyone.

The first hop issue could a powerline ethernet thing. It's usually not that bad, and mostly better than wifi.

I don't pretend to understand these things, so correct me if I'm wrong. But surely an extra 30ms on the first hop doesn't explain me getting 250-300ms in-game when I used to get 170ms with the same setup? It seems to vary day to day with a trend of getting worse over the last few months.

Here's another plot using the IP that CrypticZA suggested:

View attachment 1723771

edit: And with in-game latency around 280ms

View attachment 1723777

further edit: Here's a tracert from CMD. I might be reading it wrong, but it seems the latency is from well outside of my own network and this an ISP/routing issue?
Yea that trace looks bad from JHB you should be hitting that IP with 166 to 170

Their own looking glass gives the same result of 246ms to Blizzard


PING 185.60.112.157 (185.60.112.157) from 192.145.128.36 : 56(84) bytes of data.
64 bytes from 185.60.112.157: icmp_seq=1 ttl=241 time=246 ms
64 bytes from 185.60.112.157: icmp_seq=2 ttl=241 time=245 ms
64 bytes from 185.60.112.157: icmp_seq=3 ttl=241 time=245 ms
64 bytes from 185.60.112.157: icmp_seq=4 ttl=241 time=245 ms
64 bytes from 185.60.112.157: icmp_seq=5 ttl=241 time=245 ms

--- 185.60.112.157 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4005ms
rtt min/avg/max/mdev = 245.235/245.419/245.818/0.208 ms
 
Thanks for the help!

@Mind the Speed @TristiaanMTS Anything you can do about this?
Hi @Squidcor

We're reaching out with an update regarding the latency you've been experiencing. Our upstream provider identified a congested segment between South Africa and London on the international link. They've rerouted traffic to alleviate the pressure, but there might be a temporary increase in latency until the capacity upgrade is complete in the next few days.

Here's the current latency from Johannesburg to the server you were testing:

PING 185.60.112.157 (185.60.112.157) from 192.145.128.36 : 56(84) bytes of data.
64 bytes from 185.60.112.157: icmp_seq=1 ttl=246 time=162 ms
64 bytes from 185.60.112.157: icmp_seq=2 ttl=246 time=162 ms
64 bytes from 185.60.112.157: icmp_seq=3 ttl=246 time=162 ms
64 bytes from 185.60.112.157: icmp_seq=4 ttl=246 time=162 ms
64 bytes from 185.60.112.157: icmp_seq=5 ttl=246 time=162 ms
--- 185.60.112.157 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4003ms
rtt min/avg/max/mdev = 161.598/161.823/162.283/0.241 ms


Additionally, we noticed on your traceroute you provided a potential issue with packet loss at the second hop (FNO - Fibre Network Operator). To investigate this further, we recommend contacting our support team at [email protected]. They can analyze your specific connection and provide troubleshooting steps.

We apologize for any inconvenience caused by the increased latency and potential packet loss. We appreciate your patience and understanding.

Sincerely,
The Mind the Speed Team
 
Hi @Squidcor

We're reaching out with an update regarding the latency you've been experiencing. Our upstream provider identified a congested segment between South Africa and London on the international link. They've rerouted traffic to alleviate the pressure, but there might be a temporary increase in latency until the capacity upgrade is complete in the next few days.

Here's the current latency from Johannesburg to the server you were testing:

PING 185.60.112.157 (185.60.112.157) from 192.145.128.36 : 56(84) bytes of data.
64 bytes from 185.60.112.157: icmp_seq=1 ttl=246 time=162 ms
64 bytes from 185.60.112.157: icmp_seq=2 ttl=246 time=162 ms
64 bytes from 185.60.112.157: icmp_seq=3 ttl=246 time=162 ms
64 bytes from 185.60.112.157: icmp_seq=4 ttl=246 time=162 ms
64 bytes from 185.60.112.157: icmp_seq=5 ttl=246 time=162 ms
--- 185.60.112.157 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4003ms
rtt min/avg/max/mdev = 161.598/161.823/162.283/0.241 ms


Additionally, we noticed on your traceroute you provided a potential issue with packet loss at the second hop (FNO - Fibre Network Operator). To investigate this further, we recommend contacting our support team at [email protected]. They can analyze your specific connection and provide troubleshooting steps.

We apologize for any inconvenience caused by the increased latency and potential packet loss. We appreciate your patience and understanding.

Sincerely,
The Mind the Speed Team
Thank you for looking into this. I'll open a support ticket. I'm curious as to how you got those latency numbers from Joburg? When I do the ping test via lg.mindthespeed.co.za I get 250ms from both Joburg and Cape Town.

PING 185.60.112.157 (185.60.112.157) from 192.145.128.36 : 56(84) bytes of data.
64 bytes from 185.60.112.157: icmp_seq=1 ttl=241 time=246 ms
64 bytes from 185.60.112.157: icmp_seq=2 ttl=241 time=245 ms
64 bytes from 185.60.112.157: icmp_seq=3 ttl=241 time=245 ms
64 bytes from 185.60.112.157: icmp_seq=4 ttl=241 time=245 ms
64 bytes from 185.60.112.157: icmp_seq=5 ttl=241 time=245 ms

--- 185.60.112.157 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4005ms
rtt min/avg/max/mdev = 245.078/245.375/245.816/0.274 ms
 
Thank you for looking into this. I'll open a support ticket. I'm curious as to how you got those latency numbers from Joburg? When I do the ping test via lg.mindthespeed.co.za I get 250ms from both Joburg and Cape Town.
Hi @Squidcor

With our upstream provider identifying a congested segment, they are rerouting traffic via alternative paths to optimize network performance. While the current path is optimal, you may experience temporary increases in latency as the provider monitors and selects the most efficient route.

We anticipate this rerouting to be temporary, lasting until a capacity upgrade is completed by our upstream provider in the coming days. During this time, rerouting may occur as needed to alleviate network pressure.

We apologize for any inconvenience this may cause and appreciate your understanding.
 
Thank you for looking into this. I'll open a support ticket. I'm curious as to how you got those latency numbers from Joburg? When I do the ping test via lg.mindthespeed.co.za I get 250ms from both Joburg and Cape Town.
Hi @Squidcor

Hope that you are well.

Our upstream provider has confirmed that additional capacity has been added to the primary path. Latency will remain consistent, and traffic rerouting will no longer be required. Thank you for your patience. Should you experience any further issues, please log a ticket with our support team.

Kind Regards
Mind The Speed
 
Last edited:
Just confirming that my latency has been fixed. Very impressed with MTS support!
Hi @Squidcor.


Thank you for taking the time to share your feedback! We're thrilled to hear that our support team was able to resolve your latency issue promptly. At MTS, ensuring our clients' satisfaction is our top priority, and it's fantastic to know that we met your expectations. Should you have any further questions or concerns, please don't hesitate to reach out. We're here to help!

Sincerely,
The Mind the Speed Team
 
To follow up on my problem with Postman, MTS worked with Postman support to get the issue resolved and kept me updated daily, and today it is fixed. Competent, high-level support from MTS right from the start, really pleased I switched to them.
 
Hi @Mind the Speed and @TristiaanMTS
Hope you guys are well? So I previously logged a call about the high latency on Rocket League to EU servers and since my issue was resolved last time everything was fine for a while, but I see we back to over 300ms latency to those servers. It is worse now, where 2/3 games I will get latency of over 300ms.
I'm based in Durban on OpenServe and one of the game servers I connected to was 85.195.98.249.

rocket league ping.png

lg.mindthespeed.co.za:
rocket league ping 2.png
 
Top
Sign up to the MyBroadband newsletter