biometrics
Honorary Master
- Joined
- Aug 7, 2003
- Messages
- 71,856
- Reaction score
- 2,239
Terrible again. Better get sorted pronto or I'm out by the 25th ...
-
Join the MyBroadband community
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
-
Question of the Day: Did you buy your last car with cash or on a finance plan?
Plugg Uncapped ADSL Feedback
- Thread starter TheBossMan
- Start date
Ho3n3r
Honorary Master
Ditto. It's getting ridiculous.
Ho3n3r
Honorary Master
Obviously.
I have with Openweb, and with a different Plugg account.
Problem is, they also handle my line, so it seems they're stuffing up the line somewhere.
If I move, I will move everything.
hayted
Well-Known Member
- Joined
- May 10, 2007
- Messages
- 327
- Reaction score
- 0
Hi Janitor
I received a trial account with you guys and it was supposed to expire on the 23rd (today) but it was still working when I got home. I have changed my details on my router now so that I have gone back to my old ISP, just in case my trial account slipped through the cracks and I don't want to use it if it was intended to be terminated today. I was very happy with your service and will get an account with you guys at the end of this month. Thanks for everything
. So happy!
I received a trial account with you guys and it was supposed to expire on the 23rd (today) but it was still working when I got home. I have changed my details on my router now so that I have gone back to my old ISP, just in case my trial account slipped through the cracks and I don't want to use it if it was intended to be terminated today. I was very happy with your service and will get an account with you guys at the end of this month. Thanks for everything
. So happy!
Howdy,
Not really possible for an ISP to 'stuff up' your actual line unless they upgrade/downgrade it without your permission. Telkom only allows ISPs to do so much with the systems they made available.
I have been monitoring the support & escalation team's handling of your query. From the emails that I have seen, your traffic profile is completely the reverse of the normal user out there. In other words, transmit data > receive data. Usually it is a case of people downloading more than what they upload. Support will however be in touch to take it further.
--
The Janitor @ PluGG
PluGG - Consumer division of Internet Solutions
[email protected] | [email protected]
www.plugg.co.za | 08611 PluGG | www.is.co.za
#include <std-disclaimer.h>
Not really possible for an ISP to 'stuff up' your actual line unless they upgrade/downgrade it without your permission. Telkom only allows ISPs to do so much with the systems they made available.
I have been monitoring the support & escalation team's handling of your query. From the emails that I have seen, your traffic profile is completely the reverse of the normal user out there. In other words, transmit data > receive data. Usually it is a case of people downloading more than what they upload. Support will however be in touch to take it further.
--
The Janitor @ PluGG
PluGG - Consumer division of Internet Solutions
[email protected] | [email protected]
www.plugg.co.za | 08611 PluGG | www.is.co.za
#include <std-disclaimer.h>
Howdy!
Some feedback regarding Plugg Support.
Firstly, thank you for all the relevant information of problems experienced. I have taken down every complaint on MyBB and those mailed to me in order to take it up with the relevant parties.
Various issues addressed are resolved already, such as delays with auto responders, some staffing issues and priority between taking calls and resolving them versus incoming emails and resolving those.
The Plugg Product & Portfolio Managers had a meeting with the company responsible for support and there are now stricter SLA and penalties in play. We are getting more frequent reports (read daily) as to incoming emails vs telephonic statistics and so on; also added myself onto the Plugg support@ and sales@ aliases in order to keep an eye on things as I will not stand for generic answers in order to close a ticket.
Also consider that addressed. There is no excuse for being unprofessional and not showing any pride in your work.
I further requested that there are additional training sessions set up for Support in order to make sure they are always up to par on the latest developments/technical issues out there when it comes to Telkom, DSL and so forth; it is just all too easy for things to be blamed on Telkom or say that a port's been moved etc without knowing whether that is actually the issue at hand.
Next on my list, the changes in and around the Plugg website. Need something much more functional especially when it comes to notification and when throttling starts to kick in according to the FUP.
So things are definitely in motion.
If you do notice or experience something you are not happy about, please email me at [email protected] as that is the quickest way to get my attention. I (un)fortunately
do not sit all day and just monitor social platforms but I do scan it frequently through-out the day where possible and respond where need be. I still have to perform my Janitorial duties as well.
Speaking of which, now you need to excuse me, I should go get the kitchens ready for the graveyard shift ;-)
Have a good one!
--
The Janitor @ PluGG
PluGG - Consumer division of Internet Solutions
[email protected] | [email protected]
www.plugg.co.za | 08611 PluGG | www.is.co.za
#include <std-disclaimer.h>[/QUOTE]
Some feedback regarding Plugg Support.
Firstly, thank you for all the relevant information of problems experienced. I have taken down every complaint on MyBB and those mailed to me in order to take it up with the relevant parties.
Various issues addressed are resolved already, such as delays with auto responders, some staffing issues and priority between taking calls and resolving them versus incoming emails and resolving those.
The Plugg Product & Portfolio Managers had a meeting with the company responsible for support and there are now stricter SLA and penalties in play. We are getting more frequent reports (read daily) as to incoming emails vs telephonic statistics and so on; also added myself onto the Plugg support@ and sales@ aliases in order to keep an eye on things as I will not stand for generic answers in order to close a ticket.
Also consider that addressed. There is no excuse for being unprofessional and not showing any pride in your work.
I further requested that there are additional training sessions set up for Support in order to make sure they are always up to par on the latest developments/technical issues out there when it comes to Telkom, DSL and so forth; it is just all too easy for things to be blamed on Telkom or say that a port's been moved etc without knowing whether that is actually the issue at hand.
Next on my list, the changes in and around the Plugg website. Need something much more functional especially when it comes to notification and when throttling starts to kick in according to the FUP.
So things are definitely in motion.
If you do notice or experience something you are not happy about, please email me at [email protected] as that is the quickest way to get my attention. I (un)fortunately
do not sit all day and just monitor social platforms but I do scan it frequently through-out the day where possible and respond where need be. I still have to perform my Janitorial duties as well. Speaking of which, now you need to excuse me, I should go get the kitchens ready for the graveyard shift ;-)
Have a good one!
--
The Janitor @ PluGG
PluGG - Consumer division of Internet Solutions
[email protected] | [email protected]
www.plugg.co.za | 08611 PluGG | www.is.co.za
#include <std-disclaimer.h>[/QUOTE]
Howdy Howdy!
Just a quick friday morning following up on the whole google thread earlier.
I can confirm now that IS peers now with Google in Johannesburg.
and from DSL account (johannesburg) via v6 and v4.
Righty, good speeds and stable connections to all on this friday
--
The Janitor @ PluGG
PluGG - Consumer division of Internet Solutions
[email protected] | [email protected]
www.plugg.co.za | 08611 PluGG | www.is.co.za
#include <std-disclaimer.h>[/QUOTE]
Just a quick friday morning following up on the whole google thread earlier.
I can confirm now that IS peers now with Google in Johannesburg.
Code:
local-route-server>traceroute ip www.gmail.com
Translating "www.gmail.com"...domain server (168.210.2.2) [OK]
1 196.4.160.1 [AS 3741] 0 msec 4 msec 4 msec
2 ar2-rba-tnr-gi0-3-11.ip.isnet.net (196.34.7.195) [AS 3741] 0 msec 4 msec 0 msec
3 196.26.0.130 [AS 3741] 0 msec 0 msec 0 msec
4 74.125.49.66 [AS 15169] 0 msec 4 msec 0 msec
5 64.233.174.57 [AS 15169] 4 msec 0 msec 4 msec
6 googlemail.l.google.com (74.125.233.85) [AS 15169] 0 msec 4 msec 0 msec
local-route-server>traceroute ip www.google.co.za
Translating "www.google.co.za"...domain server (168.210.2.2) [OK]
1 196.4.160.1 [AS 3741] 0 msec 4 msec 0 msec
2 ar2-rba-tnr-gi0-3-11.ip.isnet.net (196.34.7.195) [AS 3741] 4 msec 0 msec 0 msec
3 168.209.1.179 [AS 3741] 4 msec 40 msec 0 msec
4 74.125.49.66 [AS 15169] 4 msec 4 msec 0 msec
5 64.233.174.57 [AS 15169] 0 msec 4 msec 0 msec
6 www.google.co.za (74.125.233.88) [AS 15169] 4 msec * 0 msec
local-route-server>traceroute ip www.google.com
Translating "www.google.com"...domain server (168.210.2.2) [OK]
1 196.4.160.1 [AS 3741] 0 msec 0 msec 0 msec
2 ar2-rba-tnr-gi0-3-11.ip.isnet.net (196.34.7.195) [AS 3741] 0 msec 4 msec 0 msec
3 168.209.1.179 [AS 3741] 4 msec 12 msec 0 msec
4 74.125.49.66 [AS 15169] 4 msec 0 msec 4 msec
5 64.233.174.57 [AS 15169] 0 msec 4 msec 0 msec
6 www.google.com (74.125.233.84) [AS 15169] 4 msec 0 msec 0 msecand from DSL account (johannesburg) via v6 and v4.
Code:
velocidade#traceroute www.google.co.za
Tracing the route to www.google.co.za (2C0F:FB50:4002:801::1017)
1 2C0F:FC00:5000:13::1 16 msec 16 msec 16 msec
2 pr2-rba-te2-2-0.ipv6.isnet.net (2C0F:FC00:0:6::8) 48 msec 12 msec 20 msec
3 2001:4860:1:1:0:E9D:0:1 16 msec 16 msec 20 msec
4 2001:4860:0:1::625 16 msec 368 msec 16 msec
5 2C0F:FB50:8000:3::C 16 msec 16 msec 20 msec
velocidade#traceroute ip www.google.co.za
Tracing the route to www.google.co.za (74.125.233.88)
1 196-210-138-129.dynamic.isadsl.co.za (196.210.138.129) 12 msec 12 msec 20 msec
2 196.38.73.85 24 msec 36 msec 20 msec
3 cdsl2-rba-vl150.ip.isnet.net (196.38.73.9) 8 msec 24 msec 8 msec
4 168.209.1.140 12 msec 28 msec 16 msec
5 196.26.0.130 36 msec 8 msec 12 msec
6 74.125.49.66 12 msec 24 msec 12 msec
7 64.233.174.57 12 msec 12 msec 12 msec
8 www.google.co.za (74.125.233.88) 12 msec 12 msec 28 msec
velocidade#traceroute www.google.com
Tracing the route to www.google.com (2C0F:FB50:4002:801::1012)
1 2C0F:FC00:5000:13::1 16 msec 208 msec 144 msec
2 pr2-rba-te2-2-0.ipv6.isnet.net (2C0F:FC00:0:6::8) 68 msec 36 msec 20 msec
3 2001:4860:1:1:0:E9D:0:1 16 msec 16 msec 16 msec
4 2001:4860:0:1::625 16 msec 20 msec 16 msec
5 2C0F:FB50:8000:3::5 20 msec 40 msec 20 msec
velocidade#traceroute ip www.google.com
Tracing the route to www.google.com (74.125.233.80)
1 196-210-138-129.dynamic.isadsl.co.za (196.210.138.129) 8 msec 8 msec 8 msec
2 196.38.72.229 12 msec 8 msec 12 msec
3 cdsl2-rba-vl150.ip.isnet.net (196.38.73.9) 12 msec 12 msec 92 msec
4 196.26.0.61 8 msec 8 msec 8 msec
5 168.209.1.179 12 msec 8 msec 8 msec
6 74.125.49.66 12 msec 8 msec 12 msec
7 64.233.174.57 8 msec 8 msec 8 msec
8 www.google.com (74.125.233.80) 20 msec 12 msec 12 msec
velocidade#traceroute www.gmail.com
Tracing the route to googlemail.l.google.com (2C0F:FB50:4002:801::1015)
1 2C0F:FC00:5000:13::1 16 msec 16 msec 16 msec
2 pr2-rba-te2-2-0.ipv6.isnet.net (2C0F:FC00:0:6::8) 28 msec 16 msec 12 msec
3 2001:4860:1:1:0:E9D:0:1 16 msec 20 msec 20 msec
4 2001:4860:0:1::625 32 msec 12 msec 16 msec
5 2C0F:FB50:8000:3::C 16 msec 20 msec 40 msec
velocidade#traceroute ip www.gmail.com
Tracing the route to googlemail.l.google.com (74.125.233.85)
1 196-210-138-129.dynamic.isadsl.co.za (196.210.138.129) 12 msec 8 msec 8 msec
2 cdsl1-rba-vl2360.ip.isnet.net (196.38.73.133) 8 msec 12 msec 8 msec
3 cdsl1-rba-vl150.ip.isnet.net (196.38.73.17) 12 msec 8 msec 8 msec
4 core1a-pkl-te-1-1.ip.isnet.net (196.26.0.60) 12 msec 8 msec 12 msec
5 168.209.1.179 20 msec 8 msec 8 msec
6 74.125.49.66 8 msec 8 msec 8 msec
7 64.233.174.57 8 msec 8 msec 12 msec
8 googlemail.l.google.com (74.125.233.85) 8 msec 12 msec 12 msecRighty, good speeds and stable connections to all on this friday
--
The Janitor @ PluGG
PluGG - Consumer division of Internet Solutions
[email protected] | [email protected]
www.plugg.co.za | 08611 PluGG | www.is.co.za
#include <std-disclaimer.h>[/QUOTE]
Last edited:
Tinuva
The Magician
Thank you janitor
Noticed this myself this week, very happy with this change
Noticed this myself this week, very happy with this change
hi janitor, i'm in CPT.. on an IS account - any reason why my traceroutes aren't going locally for gmail?
Code:
michael@macserver:~$traceroute mail.google.com
traceroute: Warning: mail.google.com has multiple addresses; using 173.194.41.117
traceroute to googlemail.l.google.com (173.194.41.117), 64 hops max, 52 byte packets
1 core.i.nt (192.168.88.1) 0.564 ms 0.351 ms 0.318 ms
2 196-210-201-1.dynamic.isadsl.co.za (196.210.201.1) 20.899 ms 10.448 ms 7.759 ms
3 cdsl1-ctn-vl2173.ip.isnet.net (196.38.72.113) 9.590 ms 9.925 ms 9.691 ms
4 196.35.115.128 (196.35.115.128) 9.745 ms 9.693 ms 10.178 ms
5 core1a-ctn-gi0-2.ip.isnet.net (168.209.6.5) 12.671 ms 11.897 ms 13.049 ms
6 168.209.100.13 (168.209.100.13) 32.316 ms 34.086 ms 32.994 ms
7 196.26.0.130 (196.26.0.130) 32.738 ms
168.209.1.179 (168.209.1.179) 36.753 ms
196.26.0.130 (196.26.0.130) 32.489 ms
8 74.125.49.66 (74.125.49.66) 35.442 ms 33.784 ms 32.911 ms
9 72.14.232.102 (72.14.232.102) 186.137 ms 186.924 ms 187.105 ms
10 216.239.43.42 (216.239.43.42) 187.913 ms 187.873 ms 187.253 ms
11 72.14.232.211 (72.14.232.211) 197.713 ms 197.603 ms 195.773 ms
12 209.85.253.95 (209.85.253.95) 200.259 ms 191.970 ms 190.404 ms
13 72.14.238.53 (72.14.238.53) 190.439 ms 198.523 ms 189.050 ms
14 lhr08s02-in-f21.1e100.net (173.194.41.117) 186.961 ms 193.211 ms 186.404 ms[/QUOTE]Howdy Howdy!
Just a quick friday morning following up on the whole google thread earlier.
I can confirm now that IS peers now with Google in Johannesburg.
Code:local-route-server>traceroute ip www.gmail.com Translating "www.gmail.com"...domain server (168.210.2.2) [OK] 1 196.4.160.1 [AS 3741] 0 msec 4 msec 4 msec 2 ar2-rba-tnr-gi0-3-11.ip.isnet.net (196.34.7.195) [AS 3741] 0 msec 4 msec 0 msec 3 196.26.0.130 [AS 3741] 0 msec 0 msec 0 msec 4 74.125.49.66 [AS 15169] 0 msec 4 msec 0 msec 5 64.233.174.57 [AS 15169] 4 msec 0 msec 4 msec 6 googlemail.l.google.com (74.125.233.85) [AS 15169] 0 msec 4 msec 0 msec local-route-server>traceroute ip www.google.co.za Translating "www.google.co.za"...domain server (168.210.2.2) [OK] 1 196.4.160.1 [AS 3741] 0 msec 4 msec 0 msec 2 ar2-rba-tnr-gi0-3-11.ip.isnet.net (196.34.7.195) [AS 3741] 4 msec 0 msec 0 msec 3 168.209.1.179 [AS 3741] 4 msec 40 msec 0 msec 4 74.125.49.66 [AS 15169] 4 msec 4 msec 0 msec 5 64.233.174.57 [AS 15169] 0 msec 4 msec 0 msec 6 www.google.co.za (74.125.233.88) [AS 15169] 4 msec * 0 msec local-route-server>traceroute ip www.google.com Translating "www.google.com"...domain server (168.210.2.2) [OK] 1 196.4.160.1 [AS 3741] 0 msec 0 msec 0 msec 2 ar2-rba-tnr-gi0-3-11.ip.isnet.net (196.34.7.195) [AS 3741] 0 msec 4 msec 0 msec 3 168.209.1.179 [AS 3741] 4 msec 12 msec 0 msec 4 74.125.49.66 [AS 15169] 4 msec 0 msec 4 msec 5 64.233.174.57 [AS 15169] 0 msec 4 msec 0 msec 6 www.google.com (74.125.233.84) [AS 15169] 4 msec 0 msec 0 msec
and from DSL account (johannesburg) via v6 and v4.
Code:velocidade#traceroute www.google.co.za Tracing the route to www.google.co.za (2C0F:FB50:4002:801::1017) 1 2C0F:FC00:5000:13::1 16 msec 16 msec 16 msec 2 pr2-rba-te2-2-0.ipv6.isnet.net (2C0F:FC00:0:6::8) 48 msec 12 msec 20 msec 3 2001:4860:1:1:0:E9D:0:1 16 msec 16 msec 20 msec 4 2001:4860:0:1::625 16 msec 368 msec 16 msec 5 2C0F:FB50:8000:3::C 16 msec 16 msec 20 msec velocidade#traceroute ip www.google.co.za Tracing the route to www.google.co.za (74.125.233.88) 1 196-210-138-129.dynamic.isadsl.co.za (196.210.138.129) 12 msec 12 msec 20 msec 2 196.38.73.85 24 msec 36 msec 20 msec 3 cdsl2-rba-vl150.ip.isnet.net (196.38.73.9) 8 msec 24 msec 8 msec 4 168.209.1.140 12 msec 28 msec 16 msec 5 196.26.0.130 36 msec 8 msec 12 msec 6 74.125.49.66 12 msec 24 msec 12 msec 7 64.233.174.57 12 msec 12 msec 12 msec 8 www.google.co.za (74.125.233.88) 12 msec 12 msec 28 msec velocidade#traceroute www.google.com Tracing the route to www.google.com (2C0F:FB50:4002:801::1012) 1 2C0F:FC00:5000:13::1 16 msec 208 msec 144 msec 2 pr2-rba-te2-2-0.ipv6.isnet.net (2C0F:FC00:0:6::8) 68 msec 36 msec 20 msec 3 2001:4860:1:1:0:E9D:0:1 16 msec 16 msec 16 msec 4 2001:4860:0:1::625 16 msec 20 msec 16 msec 5 2C0F:FB50:8000:3::5 20 msec 40 msec 20 msec velocidade#traceroute ip www.google.com Tracing the route to www.google.com (74.125.233.80) 1 196-210-138-129.dynamic.isadsl.co.za (196.210.138.129) 8 msec 8 msec 8 msec 2 196.38.72.229 12 msec 8 msec 12 msec 3 cdsl2-rba-vl150.ip.isnet.net (196.38.73.9) 12 msec 12 msec 92 msec 4 196.26.0.61 8 msec 8 msec 8 msec 5 168.209.1.179 12 msec 8 msec 8 msec 6 74.125.49.66 12 msec 8 msec 12 msec 7 64.233.174.57 8 msec 8 msec 8 msec 8 www.google.com (74.125.233.80) 20 msec 12 msec 12 msec velocidade#traceroute www.gmail.com Tracing the route to googlemail.l.google.com (2C0F:FB50:4002:801::1015) 1 2C0F:FC00:5000:13::1 16 msec 16 msec 16 msec 2 pr2-rba-te2-2-0.ipv6.isnet.net (2C0F:FC00:0:6::8) 28 msec 16 msec 12 msec 3 2001:4860:1:1:0:E9D:0:1 16 msec 20 msec 20 msec 4 2001:4860:0:1::625 32 msec 12 msec 16 msec 5 2C0F:FB50:8000:3::C 16 msec 20 msec 40 msec velocidade#traceroute ip www.gmail.com Tracing the route to googlemail.l.google.com (74.125.233.85) 1 196-210-138-129.dynamic.isadsl.co.za (196.210.138.129) 12 msec 8 msec 8 msec 2 cdsl1-rba-vl2360.ip.isnet.net (196.38.73.133) 8 msec 12 msec 8 msec 3 cdsl1-rba-vl150.ip.isnet.net (196.38.73.17) 12 msec 8 msec 8 msec 4 core1a-pkl-te-1-1.ip.isnet.net (196.26.0.60) 12 msec 8 msec 12 msec 5 168.209.1.179 20 msec 8 msec 8 msec 6 74.125.49.66 8 msec 8 msec 8 msec 7 64.233.174.57 8 msec 8 msec 12 msec 8 googlemail.l.google.com (74.125.233.85) 8 msec 12 msec 12 msec
Righty, good speeds and stable connections to all on this friday
--
The Janitor @ PluGG
PluGG - Consumer division of Internet Solutions
[email protected] | [email protected]
www.plugg.co.za | 08611 PluGG | www.is.co.za
#include <std-disclaimer.h>
Howdy!
Google made some changes to their network in South Africa and as result decide to stop peering at CINX and joined NAPAfrica in JNB. They are open to private peering in JNB only for the moment.
Your traceroute is fine, all local; it indicates the path taken to Johannesburg and then over the private peering point that we have with them. You should also just remember that even though we peer locally, Google will still serve some content internationally via their own bandwidth.
Have a good one!
--
The Janitor @ PluGG
PluGG - Consumer division of Internet Solutions
[email protected] | [email protected]
www.plugg.co.za | 08611 PluGG | www.is.co.za
#include <std-disclaimer.h>[/QUOTE]
Google made some changes to their network in South Africa and as result decide to stop peering at CINX and joined NAPAfrica in JNB. They are open to private peering in JNB only for the moment.
Your traceroute is fine, all local; it indicates the path taken to Johannesburg and then over the private peering point that we have with them. You should also just remember that even though we peer locally, Google will still serve some content internationally via their own bandwidth.
Have a good one!
--
The Janitor @ PluGG
PluGG - Consumer division of Internet Solutions
[email protected] | [email protected]
www.plugg.co.za | 08611 PluGG | www.is.co.za
#include <std-disclaimer.h>[/QUOTE]
Tinuva
The Magician
Your traffic goes to JNB local peering to Google as janitor mentioned. But just to be sure, make sure you DNS server is set automatic and not statically, because Google dynamically reroute people via DNS to the most optimal cluster. If you use the DNS servers assigned to you by the ISP, after a while Google will direct you to the local cluster dynamically because their systems will detect it is optimal for you.
This redirection sometimes takes a while to happen, but it should happen if you on the ISPs auto assigned DNS servers.
I use unotelly's CPT node as my primary DNS
Tinuva
The Magician
Try to use that only on the pcs where you need to watch hulu/netflix, and the others where you do general browsing ect use the ISPs DNS servers.
Depending on who uses their CPT server, and where it is hosted, that will change where your akamai and google traffic will go, and may not always be as optimized for you as it should be.
Tinuva
The Magician
Janitor, it looks like there is high latency from Cape Town IS ADSL to MTN in JHB. Not exactly sure, but the latency seems much higher than it should be, and I noticed this online in games.
On another account the latencies are closer to 30-40ms.
Code:
C:\Users\Tinuva>tracert 196.30.66.46
Tracing route to 196.30.66.46 over a maximum of 30 hops
1 5 ms <1 ms <1 ms router.heaven.za.net [10.0.0.1]
2 15 ms 5 ms 5 ms 196-209-37-1.dynamic.isadsl.co.za [196.209.37.1]
3 7 ms 7 ms 14 ms 196.38.72.125
4 7 ms 7 ms 17 ms 196.35.115.136
5 9 ms 21 ms 9 ms core2a-ctn-gi0-1.ip.isnet.net [168.209.2.6]
6 18 ms 8 ms 16 ms 168.209.2.130
7 7 ms 6 ms 15 ms 41-208-29-210.mtnns.net [41.208.29.210]
8 17 ms 7 ms 17 ms 196.44.0.75
9 91 ms 80 ms 80 ms rb-cr-1.za--ct-cr-2.za-b.mtnns.net [196.44.31.250]
10 78 ms 80 ms 82 ms jh-dca-2.za--jh-cr-1.za-a.mtnns.net [196.44.0.221]
11 91 ms 80 ms 80 ms ge10-1-9sub0.te3.jnb6.za.mtnbusiness.net [196.31.220.12]
12 94 ms * 75 ms tengigabitethernet9-1.gw20.jnb6.za.mtnbusiness.net [196.31.220.25]
13 93 ms 79 ms 79 ms tengigabitethernet5-1.hr10.jnb6.za.mtnbusiness.net [196.31.63.154]
14 78 ms 80 ms 81 ms 196.30.66.46
Trace complete.On another account the latencies are closer to 30-40ms.
Code:
C:\Users\Tinuva>tracert 196.30.66.46
Tracing route to 196.30.66.46 over a maximum of 30 hops
1 4 ms <1 ms <1 ms router.heaven.za.net [10.0.0.1]
2 5 ms 5 ms 5 ms dsl-61-101-1.dynamic.wa.co.za [41.61.101.1]
3 8 ms 7 ms 6 ms wnls-ipc1-vl-105.wa.co.za [196.220.59.250]
4 10 ms 10 ms 10 ms wnls-cr1-vl-801.wa.co.za [41.185.0.67]
5 38 ms 38 ms 9 ms wbs-ip-hsll-1-vl-102.telkom-ipnet.co.za [196.220.59.230]
6 31 ms 9 ms 9 ms 196.43.11.234
7 14 ms 9 ms 12 ms 196.43.25.206
8 21 ms 12 ms 10 ms mtn-gw.telkom-ipnet.co.za [196.25.165.198]
9 16 ms 34 ms 9 ms tb-cr-1.za--tb-pr-1.za-a.mtnns.net [196.44.18.140]
10 32 ms 61 ms 30 ms jp-ad-1.za--jp-cr-1.za-a.mtnns.net [196.44.31.13]
11 96 ms 51 ms 74 ms rb-cr-1.za--jh-cr-2.za-a.mtnns.net [196.44.31.94]
12 41 ms 75 ms 32 ms jh-dca-2.za--jh-cr-1.za-a.mtnns.net [196.44.0.221]
13 47 ms 33 ms 32 ms ge10-1-9sub0.te3.jnb6.za.mtnbusiness.net [196.31.220.12]
14 33 ms 32 ms 34 ms tengigabitethernet9-1.gw20.jnb6.za.mtnbusiness.net [196.31.220.25]
15 54 ms 30 ms 30 ms tengigabitethernet5-1.hr10.jnb6.za.mtnbusiness.net [196.31.63.154]
16 30 ms 31 ms 30 ms 196.30.66.46
Trace complete.Tinuva
The Magician
Seems the latency issue is fine today.
Last edited:
Tinuva
The Magician
Sure.
Code:
C:\Users\Tinuva>tracert 196.30.66.46
Tracing route to 196.30.66.46 over a maximum of 30 hops
1 4 ms <1 ms <1 ms router.heaven.za.net [10.0.0.1]
2 7 ms 6 ms 18 ms 196-209-37-1.dynamic.isadsl.co.za [196.209.37.1]
3 7 ms 18 ms 6 ms 196.38.72.125
4 18 ms 8 ms 18 ms 196.35.115.136
5 9 ms 24 ms 9 ms core2a-ctn-gi0-1.ip.isnet.net [168.209.2.6]
6 7 ms 16 ms 8 ms 168.209.2.130
7 7 ms 21 ms 6 ms 41-208-29-210.mtnns.net [41.208.29.210]
8 7 ms 7 ms 15 ms 196.44.0.75
9 45 ms 59 ms 59 ms rb-cr-1.za--ct-cr-2.za-b.mtnns.net [196.44.31.250]
10 38 ms 42 ms 39 ms 196.44.31.97
11 37 ms 63 ms 49 ms ge10-1-9sub0.te3.jnb6.za.mtnbusiness.net [196.31.220.12]
12 40 ms 51 ms 51 ms tengigabitethernet9-1.gw20.jnb6.za.mtnbusiness.net [196.31.220.25]
13 37 ms 48 ms 36 ms tengigabitethernet5-1.hr10.jnb6.za.mtnbusiness.n
et [196.31.63.154]
14 38 ms 47 ms 37 ms 196.30.66.46
Trace complete.The trace on the other account still looks the same, just looks like the IS account now is back to what it used to be before what I experienced yesterday (Saterday).
Was odd to see 90-100ms in online games, when it used to be around 30-50ms.