International slow ?

Necuno

Necuno

Court Jester
Joined
Sep 27, 2005
Messages
58,566
Reaction score
3,437
Facebook for example or intel.com seems dead.
 
Pr⊕phet said:
Facebook for example or intel.com seems dead.
Click to expand...

Zappers said:
i am having the same issues
Click to expand...

Good morning Guys, please provide me pings and tracers to local and international sites. Also if you are experiencing browsing problems, please be specific about the websites and what the problems are (i.e. pages taking long to load, time outs, etc.). Your location would also be appreciated.
 
Hi MWEB Guy,

I'm in Durbanville, these stats from after rebooting my router, during a particularly bad patch, the low connectivity comes and goes. We've been experiencing this since about lunchtime yesterday.

$ ping github.com
PING github.com (207.97.227.239) 56(84) bytes of data.
64 bytes from github.com (207.97.227.239): icmp_req=12 ttl=43 time=258 ms
^C
--- github.com ping statistics ---
25 packets transmitted, 1 received, 96% packet loss, time 24168ms
rtt min/avg/max/mdev = 258.535/258.535/258.535/0.000 ms

$ ping www.github.com
PING www.github.com (207.97.227.243) 56(84) bytes of data.
64 bytes from gist.github.com (207.97.227.243): icmp_req=1 ttl=45 time=236 ms
64 bytes from gist.github.com (207.97.227.243): icmp_req=2 ttl=45 time=234 ms
^C
--- www.github.com ping statistics ---
34 packets transmitted, 2 received, 94% packet loss, time 33241ms
rtt min/avg/max/mdev = 234.049/235.164/236.280/1.216 ms

$ ping www.facebook.com
PING www.facebook.com (69.63.190.18) 56(84) bytes of data.
^C
--- www.facebook.com ping statistics ---
49 packets transmitted, 0 received, 100% packet loss, time 48214ms

$ ping facebook.com
PING facebook.com (69.171.229.11) 56(84) bytes of data.
64 bytes from www-10-06-prn1.facebook.com (69.171.229.11): icmp_req=1 ttl=240 time=342 ms
64 bytes from www-10-06-prn1.facebook.com (69.171.229.11): icmp_req=2 ttl=240 time=341 ms
64 bytes from www-10-06-prn1.facebook.com (69.171.229.11): icmp_req=3 ttl=240 time=386 ms
64 bytes from www-10-06-prn1.facebook.com (69.171.229.11): icmp_req=4 ttl=240 time=326 ms
^C
--- facebook.com ping statistics ---
43 packets transmitted, 4 received, 90% packet loss, time 42136ms
rtt min/avg/max/mdev = 326.525/349.344/386.900/22.596 ms

$ traceroute www.facebook.com
traceroute to www.facebook.com (69.63.190.18), 30 hops max, 60 byte packets
1 home.gateway (10.0.0.2) 3.808 ms 3.823 ms 5.719 ms
2 41-133-102-1.dsl.mweb.co.za (41.133.102.1) 84.811 ms 102.961 ms 103.344 ms
3 te1-1-0.508.cpt-ipc-1.mweb.co.za (196.28.178.190) 104.264 ms 104.456 ms 108.260 ms
4 197-84-3-2.cpt.mweb.co.za (197.84.3.2) 109.348 ms 109.632 ms 109.795 ms
5 tengige0-3-0-0.12.cpt-up-1.mweb.co.za (196.28.178.113) 116.546 ms 117.258 ms 123.688 ms
6 197-80-4-136.jhb.mweb.co.za (197.80.4.136) 308.634 ms 235.916 ms 237.034 ms
7 pos0-0-3-0.lon-up-1.mweb.co.za (196.22.164.2) 200.413 ms 205.179 ms 186.853 ms
8 195.66.227.121 (195.66.227.121) 168.570 ms * 173.775 ms
9 * * *
10 ae0.dr03.ash2.tfbnw.net (204.15.20.35) 260.398 ms ae11.dr03.ash2.tfbnw.net (74.119.78.154) 286.484 ms ae6.dr04.ash2.tfbnw.net (74.119.78.85) 291.128 ms
11 po1018.csw02a.ash2.tfbnw.net (74.119.77.53) 295.767 ms po1016.csw02a.ash2.tfbnw.net (74.119.76.195) 236.151 ms po1017.csw02b.ash2.tfbnw.net (74.119.76.205) 246.693 ms
12 * * *
...
30 * * *

$ traceroute www.github.com
traceroute to www.github.com (207.97.227.243), 30 hops max, 60 byte packets
1 home.gateway (10.0.0.2) 4.848 ms 4.979 ms 5.613 ms
2 41-133-102-1.dsl.mweb.co.za (41.133.102.1) 20.920 ms 21.324 ms 21.988 ms
3 te1-1-0.508.cpt-ipc-1.mweb.co.za (196.28.178.190) 27.012 ms 27.522 ms 33.532 ms
4 197-84-3-2.cpt.mweb.co.za (197.84.3.2) 37.398 ms 37.924 ms 38.193 ms
5 tengige0-3-0-0.12.cpt-up-1.mweb.co.za (196.28.178.113) 48.572 ms 49.100 ms 49.281 ms
6 197-80-4-136.jhb.mweb.co.za (197.80.4.136) 236.797 ms 226.628 ms 227.372 ms
7 pos0-0-3-0.lon-up-1.mweb.co.za (196.22.164.2) 225.763 ms 187.961 ms 202.413 ms
8 xe-10-1-3.edge4.London1.Level3.net (212.113.14.121) 164.544 ms 166.925 ms 169.639 ms
9 ae-52-52.csw2.London1.Level3.net (4.69.139.120) 187.822 ms * 201.615 ms
10 * * *
11 ae-44-44.ebr1.NewYork1.Level3.net (4.69.137.78) 255.090 ms * *
12 * * ae-10-10.ebr2.Washington12.Level3.net (4.69.148.50) 282.535 ms
13 ae-3-3.ebr2.Washington1.Level3.net (4.69.132.89) 265.896 ms 265.236 ms *
14 ae-82-82.csw3.Washington1.Level3.net (4.69.134.154) 272.684 ms * *
15 ae-1-60.edge1.Washington4.Level3.net (4.69.149.15) 260.440 ms * ae-3-80.edge1.Washington4.Level3.net (4.69.149.143) 258.097 ms
16 RACKSPACE-M.edge1.Washington4.Level3.net (4.53.112.46) 238.584 ms * *
17 vlan905.core5.iad2.rackspace.net (72.4.122.10) 261.674 ms * *
18 aggr301a-1-core5.iad2.rackspace.net (72.4.122.121) 261.000 ms * *
19 gist.github.com (207.97.227.243) 257.858 ms 258.422 ms 258.757 ms

$ ping mweb.co.za
PING mweb.co.za (196.2.63.110) 56(84) bytes of data.
64 bytes from www.mweb.co.za (196.2.63.110): icmp_req=1 ttl=122 time=10.9 ms
64 bytes from www.mweb.co.za (196.2.63.110): icmp_req=2 ttl=122 time=8.95 ms
64 bytes from www.mweb.co.za (196.2.63.110): icmp_req=3 ttl=122 time=16.2 ms
64 bytes from www.mweb.co.za (196.2.63.110): icmp_req=4 ttl=122 time=9.53 ms
64 bytes from www.mweb.co.za (196.2.63.110): icmp_req=5 ttl=122 time=13.6 ms
64 bytes from www.mweb.co.za (196.2.63.110): icmp_req=6 ttl=122 time=16.5 ms
^C
--- mweb.co.za ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5003ms
rtt min/avg/max/mdev = 8.955/12.654/16.588/3.044 ms

$ traceroute mweb.co.za
traceroute to mweb.co.za (196.2.63.110), 30 hops max, 60 byte packets
1 home.gateway (10.0.0.2) 4.462 ms 4.500 ms 4.581 ms
2 41-133-102-1.dsl.mweb.co.za (41.133.102.1) 85.834 ms 93.127 ms 94.359 ms
3 te1-1-0.505.cpt-ipc-1.mweb.co.za (196.28.178.178) 96.601 ms 98.717 ms 102.188 ms
4 197-84-3-2.cpt.mweb.co.za (197.84.3.2) 103.951 ms 110.215 ms 110.540 ms
5 196-28-178-38.adsl.mweb.co.za (196.28.178.38) 117.464 ms 117.995 ms 118.261 ms
6 cte-core-sw2.vwol.net (196.41.144.35) 118.834 ms 100.820 ms 105.468 ms
7 * * *
...
30 * * *
 
Hi Smautf,

Thank you for bring this to my attention.
Could you please forward me you MWEB account details via PM.

Smautf said:
Hi MWEB Guy,

I'm in Durbanville, these stats from after rebooting my router, during a particularly bad patch, the low connectivity comes and goes. We've been experiencing this since about lunchtime yesterday.

$ ping github.com
PING github.com (207.97.227.239) 56(84) bytes of data.
64 bytes from github.com (207.97.227.239): icmp_req=12 ttl=43 time=258 ms
^C
--- github.com ping statistics ---
25 packets transmitted, 1 received, 96% packet loss, time 24168ms
rtt min/avg/max/mdev = 258.535/258.535/258.535/0.000 ms

$ ping www.github.com
PING www.github.com (207.97.227.243) 56(84) bytes of data.
64 bytes from gist.github.com (207.97.227.243): icmp_req=1 ttl=45 time=236 ms
64 bytes from gist.github.com (207.97.227.243): icmp_req=2 ttl=45 time=234 ms
^C
--- www.github.com ping statistics ---
34 packets transmitted, 2 received, 94% packet loss, time 33241ms
rtt min/avg/max/mdev = 234.049/235.164/236.280/1.216 ms

$ ping www.facebook.com
PING www.facebook.com (69.63.190.18) 56(84) bytes of data.
^C
--- www.facebook.com ping statistics ---
49 packets transmitted, 0 received, 100% packet loss, time 48214ms

$ ping facebook.com
PING facebook.com (69.171.229.11) 56(84) bytes of data.
64 bytes from www-10-06-prn1.facebook.com (69.171.229.11): icmp_req=1 ttl=240 time=342 ms
64 bytes from www-10-06-prn1.facebook.com (69.171.229.11): icmp_req=2 ttl=240 time=341 ms
64 bytes from www-10-06-prn1.facebook.com (69.171.229.11): icmp_req=3 ttl=240 time=386 ms
64 bytes from www-10-06-prn1.facebook.com (69.171.229.11): icmp_req=4 ttl=240 time=326 ms
^C
--- facebook.com ping statistics ---
43 packets transmitted, 4 received, 90% packet loss, time 42136ms
rtt min/avg/max/mdev = 326.525/349.344/386.900/22.596 ms

$ traceroute www.facebook.com
traceroute to www.facebook.com (69.63.190.18), 30 hops max, 60 byte packets
1 home.gateway (10.0.0.2) 3.808 ms 3.823 ms 5.719 ms
2 41-133-102-1.dsl.mweb.co.za (41.133.102.1) 84.811 ms 102.961 ms 103.344 ms
3 te1-1-0.508.cpt-ipc-1.mweb.co.za (196.28.178.190) 104.264 ms 104.456 ms 108.260 ms
4 197-84-3-2.cpt.mweb.co.za (197.84.3.2) 109.348 ms 109.632 ms 109.795 ms
5 tengige0-3-0-0.12.cpt-up-1.mweb.co.za (196.28.178.113) 116.546 ms 117.258 ms 123.688 ms
6 197-80-4-136.jhb.mweb.co.za (197.80.4.136) 308.634 ms 235.916 ms 237.034 ms
7 pos0-0-3-0.lon-up-1.mweb.co.za (196.22.164.2) 200.413 ms 205.179 ms 186.853 ms
8 195.66.227.121 (195.66.227.121) 168.570 ms * 173.775 ms
9 * * *
10 ae0.dr03.ash2.tfbnw.net (204.15.20.35) 260.398 ms ae11.dr03.ash2.tfbnw.net (74.119.78.154) 286.484 ms ae6.dr04.ash2.tfbnw.net (74.119.78.85) 291.128 ms
11 po1018.csw02a.ash2.tfbnw.net (74.119.77.53) 295.767 ms po1016.csw02a.ash2.tfbnw.net (74.119.76.195) 236.151 ms po1017.csw02b.ash2.tfbnw.net (74.119.76.205) 246.693 ms
12 * * *
...
30 * * *

$ traceroute www.github.com
traceroute to www.github.com (207.97.227.243), 30 hops max, 60 byte packets
1 home.gateway (10.0.0.2) 4.848 ms 4.979 ms 5.613 ms
2 41-133-102-1.dsl.mweb.co.za (41.133.102.1) 20.920 ms 21.324 ms 21.988 ms
3 te1-1-0.508.cpt-ipc-1.mweb.co.za (196.28.178.190) 27.012 ms 27.522 ms 33.532 ms
4 197-84-3-2.cpt.mweb.co.za (197.84.3.2) 37.398 ms 37.924 ms 38.193 ms
5 tengige0-3-0-0.12.cpt-up-1.mweb.co.za (196.28.178.113) 48.572 ms 49.100 ms 49.281 ms
6 197-80-4-136.jhb.mweb.co.za (197.80.4.136) 236.797 ms 226.628 ms 227.372 ms
7 pos0-0-3-0.lon-up-1.mweb.co.za (196.22.164.2) 225.763 ms 187.961 ms 202.413 ms
8 xe-10-1-3.edge4.London1.Level3.net (212.113.14.121) 164.544 ms 166.925 ms 169.639 ms
9 ae-52-52.csw2.London1.Level3.net (4.69.139.120) 187.822 ms * 201.615 ms
10 * * *
11 ae-44-44.ebr1.NewYork1.Level3.net (4.69.137.78) 255.090 ms * *
12 * * ae-10-10.ebr2.Washington12.Level3.net (4.69.148.50) 282.535 ms
13 ae-3-3.ebr2.Washington1.Level3.net (4.69.132.89) 265.896 ms 265.236 ms *
14 ae-82-82.csw3.Washington1.Level3.net (4.69.134.154) 272.684 ms * *
15 ae-1-60.edge1.Washington4.Level3.net (4.69.149.15) 260.440 ms * ae-3-80.edge1.Washington4.Level3.net (4.69.149.143) 258.097 ms
16 RACKSPACE-M.edge1.Washington4.Level3.net (4.53.112.46) 238.584 ms * *
17 vlan905.core5.iad2.rackspace.net (72.4.122.10) 261.674 ms * *
18 aggr301a-1-core5.iad2.rackspace.net (72.4.122.121) 261.000 ms * *
19 gist.github.com (207.97.227.243) 257.858 ms 258.422 ms 258.757 ms

$ ping mweb.co.za
PING mweb.co.za (196.2.63.110) 56(84) bytes of data.
64 bytes from www.mweb.co.za (196.2.63.110): icmp_req=1 ttl=122 time=10.9 ms
64 bytes from www.mweb.co.za (196.2.63.110): icmp_req=2 ttl=122 time=8.95 ms
64 bytes from www.mweb.co.za (196.2.63.110): icmp_req=3 ttl=122 time=16.2 ms
64 bytes from www.mweb.co.za (196.2.63.110): icmp_req=4 ttl=122 time=9.53 ms
64 bytes from www.mweb.co.za (196.2.63.110): icmp_req=5 ttl=122 time=13.6 ms
64 bytes from www.mweb.co.za (196.2.63.110): icmp_req=6 ttl=122 time=16.5 ms
^C
--- mweb.co.za ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5003ms
rtt min/avg/max/mdev = 8.955/12.654/16.588/3.044 ms

$ traceroute mweb.co.za
traceroute to mweb.co.za (196.2.63.110), 30 hops max, 60 byte packets
1 home.gateway (10.0.0.2) 4.462 ms 4.500 ms 4.581 ms
2 41-133-102-1.dsl.mweb.co.za (41.133.102.1) 85.834 ms 93.127 ms 94.359 ms
3 te1-1-0.505.cpt-ipc-1.mweb.co.za (196.28.178.178) 96.601 ms 98.717 ms 102.188 ms
4 197-84-3-2.cpt.mweb.co.za (197.84.3.2) 103.951 ms 110.215 ms 110.540 ms
5 196-28-178-38.adsl.mweb.co.za (196.28.178.38) 117.464 ms 117.995 ms 118.261 ms
6 cte-core-sw2.vwol.net (196.41.144.35) 118.834 ms 100.820 ms 105.468 ms
7 * * *
...
30 * * *
Click to expand...
 
Hi MWEB Guy,

Thanks for the reply. The connection seems much better right now:

--- facebook.com ping statistics ---
41 packets transmitted, 40 received, 2% packet loss, time 40046ms
rtt min/avg/max/mdev = 321.177/333.195/522.709/38.902 ms
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X