i.got~issues
Expert Member
- Joined
- Apr 21, 2011
- Messages
- 4,718
Glad I could help dude![]()
You guys were just awsomesauce today.
Glad I could help dude![]()
i.got~issues, too early
View attachment 172065
10mbit line.
tracert webafrica.com
Tracing route to webafrica.com [196.220.58.66]
over a maximum of 30 hops:
1 3 ms 2 ms 2 ms home.gateway.pace.net [192.168.1.1]
2 7 ms 6 ms 7 ms 105-236-234-65-esr-lo.mtnbusiness.co.za [105.236
.234.65]
3 10 ms 9 ms 9 ms 41.181.221.254
4 47 ms 17 ms 10 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.19
8.188]
5 10 ms 10 ms 9 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 12 ms 13 ms 13 ms 196.44.31.106
7 25 ms 9 ms 9 ms nl-ha-2.za--rb-cr-1.za-a.mtnns.net [196.44.0.121
]
8 18 ms 11 ms 10 ms 41-208-29-209.mtnns.net [41.208.29.209]
9 10 ms 33 ms 15 ms css2-ctn-gi0-1.ip.isnet.net [168.209.2.15]
10 12 ms 29 ms 19 ms mi-za-cpt-br1-gi0-3-108.ip.isnet.net [168.209.28
.42]
11 21 ms 13 ms 9 ms 197.96.154.190
12 11 ms 10 ms 10 ms 197.96.154.191
13 20 ms 19 ms 19 ms 196.220.58.66
Trace complete.
EDIT: Back to normal.
No, it's good now.That's strange, has this been happening often?
Reply from 172.30.0.41: bytes=32 time=16ms TTL=125
Reply from 172.30.0.41: bytes=32 time=16ms TTL=125
Reply from 172.30.0.41: bytes=32 time=15ms TTL=125
Request timed out.
Reply from 172.30.0.41: bytes=32 time=16ms TTL=125
Reply from 172.30.0.41: bytes=32 time=14ms TTL=125
Reply from 172.30.0.41: bytes=32 time=21ms TTL=125
Request timed out.
Reply from 172.30.0.41: bytes=32 time=15ms TTL=125
Reply from 172.30.0.41: bytes=32 time=17ms TTL=125
Reply from 172.30.0.41: bytes=32 time=15ms TTL=125
Request timed out.
Reply from 172.30.0.41: bytes=32 time=16ms TTL=125
Reply from 172.30.0.41: bytes=32 time=18ms TTL=125
Request timed out.
Request timed out.
Reply from 172.30.0.41: bytes=32 time=20ms TTL=125
Reply from 172.30.0.41: bytes=32 time=15ms TTL=125
Ping statistics for 172.30.0.41:
Packets: Sent = 444, Received = 291, Lost = 153 (34% loss),
Approximate round trip times in milli-seconds:
Minimum = 14ms, Maximum = 84ms, Average = 21ms
Tracing route to 41.85.xxx.xxx over a maximum of 30 hops
1 1 ms 1 ms 1 ms 192.168.11.1
2 2 ms 1 ms 2 ms 192.168.91.1
3 64 ms 10 ms 10 ms 105.236.8.xxx
4 13 ms 12 ms 12 ms 41.181.221.254
5 11 ms 11 ms 12 ms 41.181.198.188
6 12 ms 12 ms 12 ms 196.44.18.2
7 14 ms 12 ms 13 ms 196.44.31.134
8 12 ms 11 ms 12 ms 196.44.0.74
9 12 ms 12 ms 12 ms 41.208.29.209
10 21 ms 20 ms 23 ms 168.209.6.15
11 13 ms 14 ms 13 ms 168.209.28.42
12 12 ms 13 ms 23 ms 197.96.154.190
13 13 ms 14 ms 12 ms 197.96.154.191
14 17 ms 18 ms 19 ms 41.185.1.106
15 13 ms 13 ms 15 ms 41.185.0.62
16 14 ms 14 ms 13 ms 196.1.56.97
17 14 ms 13 ms 13 ms 41.85.xxx.xxx
18 17 ms 16 ms 14 ms 41.85.xxx.xxx
19 16 ms 15 ms 14 ms 41.85.xxx.xxx
Trace complete.
My fellow Afipeeps you are lucky.
WA has that promo so I am abusing those badboys allowing you oakes some breathing time.
![]()
Getting huge packet loss in CS:GO too. I'm honestly done. Time to move on next month I think
Thor...bud, u really make me laugh. I have never known someone to be so happy with his new toy like u. I swear since getting ur new 40mb line you have been like a sugar induced kid in a candle store. Remember to much of a good thing will rot ur teeth ;-)
My fellow Afipeeps you are lucky.
WA has that promo so I am abusing those badboys allowing you oakes some breathing time.
![]()