Slow speeds - TSV CBD exchange

[Musicinbed]

Everyone who has tested so far has similar international issues except for Newcrest.

In order to help you resolve you issue and to determine what you are explaining here; I would like the following test results from you.

1. Netstat
2. Ping test to http://www.dailymail.co.uk
3. Provide a snap shot of your modem status page

I will work with you in identifying / resolving this issue

C:\Users\Stephen>netstat

Active Connections

Proto Local Address Foreign Address State
TCP 127.0.0.1:12080 Stephen-PC:59416 ESTABLISHED
TCP 127.0.0.1:12080 Stephen-PC:59418 ESTABLISHED
TCP 127.0.0.1:12080 Stephen-PC:59427 ESTABLISHED
TCP 127.0.0.1:12080 Stephen-PC:59428 ESTABLISHED
TCP 127.0.0.1:12080 Stephen-PC:59429 ESTABLISHED
TCP 127.0.0.1:12080 Stephen-PC:59430 ESTABLISHED
TCP 127.0.0.1:12080 Stephen-PC:59431 ESTABLISHED
TCP 127.0.0.1:12080 Stephen-PC:59432 ESTABLISHED
TCP 127.0.0.1:12080 Stephen-PC:59434 ESTABLISHED
TCP 127.0.0.1:12080 Stephen-PC:59435 ESTABLISHED
TCP 127.0.0.1:12080 Stephen-PC:59439 ESTABLISHED
TCP 127.0.0.1:12080 Stephen-PC:59442 TIME_WAIT
TCP 127.0.0.1:59416 Stephen-PC:12080 ESTABLISHED
TCP 127.0.0.1:59418 Stephen-PC:12080 ESTABLISHED
TCP 127.0.0.1:59427 Stephen-PC:12080 ESTABLISHED
TCP 127.0.0.1:59428 Stephen-PC:12080 ESTABLISHED
TCP 127.0.0.1:59429 Stephen-PC:12080 ESTABLISHED
TCP 127.0.0.1:59430 Stephen-PC:12080 ESTABLISHED
TCP 127.0.0.1:59431 Stephen-PC:12080 ESTABLISHED
TCP 127.0.0.1:59432 Stephen-PC:12080 ESTABLISHED
TCP 127.0.0.1:59434 Stephen-PC:12080 ESTABLISHED
TCP 127.0.0.1:59435 Stephen-PC:12080 ESTABLISHED
TCP 127.0.0.1:59439 Stephen-PC:12080 ESTABLISHED
TCP 192.168.1.5:50126 fcds94:http CLOSE_WAIT
TCP 192.168.1.5:52934 api-read-13-06-prn1:https ESTABLISHED
TCP 192.168.1.5:56049 110.44.26.158:6667 ESTABLISHED
TCP 192.168.1.5:56068 irc:6667 ESTABLISHED
TCP 192.168.1.5:56086 202:http CLOSE_WAIT
TCP 192.168.1.5:56156 api-read-11-06-prn1:https ESTABLISHED
TCP 192.168.1.5:57966 221.123.176.68:12345 ESTABLISHED
TCP 192.168.1.5:59417 yfrog:http CLOSE_WAIT
TCP 192.168.1.5:59420 desmond:http CLOSE_WAIT
TCP 192.168.1.5:59433 www:http ESTABLISHED
TCP 192.168.1.5:59445 www:http ESTABLISHED
TCP 192.168.1.5:59446 www:http ESTABLISHED
TCP 192.168.1.5:59447 www:http ESTABLISHED
TCP 192.168.1.5:59449 www:http ESTABLISHED
TCP 192.168.1.5:59450 www:http ESTABLISHED
TCP 192.168.1.5:59451 c:http ESTABLISHED
TCP 192.168.1.5:59452 js:http ESTABLISHED
TCP 192.168.1.5:59453 js:http ESTABLISHED
TCP 192.168.1.5:61350 74.125.237.53:https ESTABLISHED

C:\Users\Stephen>

C:\Users\Stephen>ping dailymail.co.uk

Pinging dailymail.co.uk [195.234.240.212] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 195.234.240.212:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Users\Stephen>tracert dailymail.co.uk

Tracing route to dailymail.co.uk [195.234.240.212]
over a maximum of 30 hops:

1 4 ms 2 ms 2 ms mygateway1.ar7 [192.168.1.1]
2 * * * Request timed out.
3 22 ms 20 ms 21 ms 3.3.96.58.static.exetel.com.au [58.96.3.3]
4 22 ms 23 ms 21 ms 98.3.96.58.static.exetel.com.au [58.96.3.98]
5 24 ms 24 ms 24 ms 119.225.28.205
6 50 ms 37 ms 41 ms 10.251.24.3
7 * * * Request timed out.
8 196 ms 194 ms 194 ms 203.208.191.157
9 287 ms 196 ms 195 ms ae1-108.sjc12.ip4.tinet.net [77.67.79.1]
10 345 ms 344 ms 349 ms xe-5-2-0.lon11.ip4.tinet.net [89.149.187.110]
11 345 ms 345 ms 347 ms xe-11-3-0.BR2.LND18.ALTER.NET [146.188.112.5]
12 348 ms 345 ms 345 ms ge-7-0-0.XT1.LND2.ALTER.NET [146.188.4.217]
13 348 ms 346 ms 345 ms so-1-0-0.XT1.LND9.ALTER.NET [146.188.14.218]
14 347 ms 346 ms 345 ms POS1-0.GW2.LND9.ALTER.NET [158.43.150.158]
15 352 ms 347 ms 345 ms uuk203860.uk.customer.alter.net [158.43.17.134]

16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

I get different results if I add "www." It seems to connect to an australian server.

C:\Users\Stephen>ping www.dailymail.co.uk

Pinging a1613.g.akamai.net [220.233.2.202] with 32 bytes of data:
Reply from 220.233.2.202: bytes=32 time=43ms TTL=60
Reply from 220.233.2.202: bytes=32 time=43ms TTL=60
Reply from 220.233.2.202: bytes=32 time=42ms TTL=60
Reply from 220.233.2.202: bytes=32 time=44ms TTL=60

Ping statistics for 220.233.2.202:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 42ms, Maximum = 44ms, Average = 43ms

C:\Users\Stephen>tracert www.dailymail.co.uk

Tracing route to www.dailymail.co.uk [220.233.2.202]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms mygateway1.ar7 [192.168.1.1]
2 * * * Request timed out.
3 44 ms 41 ms 42 ms 1.3.96.58.static.exetel.com.au [58.96.3.1]
4 45 ms 42 ms 43 ms static.ak.fbcdn.net [220.233.2.202]

Trace complete.


here is a ping and tracert from the europhase UK mirror server.
C:\Users\Stephen>ping uk1.ozspeedtest.com

Pinging uk1.ozspeedtest.com [95.154.200.254] with 32 bytes of data:
Reply from 95.154.200.254: bytes=32 time=328ms TTL=53
Reply from 95.154.200.254: bytes=32 time=328ms TTL=53
Reply from 95.154.200.254: bytes=32 time=330ms TTL=53
Reply from 95.154.200.254: bytes=32 time=329ms TTL=53

Ping statistics for 95.154.200.254:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 328ms, Maximum = 330ms, Average = 328ms

C:\Users\Stephen>tracert uk1.ozspeedtest.com

Tracing route to uk1.ozspeedtest.com [95.154.200.254]
over a maximum of 30 hops:

1 2 ms 1 ms 2 ms mygateway1.ar7 [192.168.1.1]
2 * * * Request timed out.
3 21 ms 21 ms 21 ms 3.3.96.58.static.exetel.com.au [58.96.3.3]
4 21 ms 22 ms 23 ms 98.3.96.58.static.exetel.com.au [58.96.3.98]
5 21 ms 21 ms 21 ms 119.225.28.205
6 38 ms 36 ms 37 ms 10.249.24.3
7 * * * Request timed out.
8 193 ms 194 ms 194 ms 203.208.191.157
9 231 ms 228 ms 200 ms 67.17.192.141
10 330 ms 327 ms 328 ms IOMART.TenGigabitEthernet7-1.ar4.LON3.gblx.net [
64.211.1.190]
11 328 ms 349 ms 329 ms 62-233-127-182.as20860.net [62.233.127.182]
12 329 ms 329 ms 330 ms epukvps14.europhase.net [95.154.200.205]
13 329 ms 329 ms 328 ms uk1.ozspeedtest.com [95.154.200.254]

Trace complete.

There isn't anything wrong with my line or my setup. I can easily receive full speeds pretty much whenever I want as long as I multi-thread the download.

Thejeg, do you have access to internet from exetel? Why don't you try the europhase ozspeedtest test and post your results here. I'm curious to see if you would achieve over 250KB/s.

Here are my current results: as you can see I can achieve 720KB/s from a gold coast (QLD) hosted site, yet only 27KB/s from europhase.
http://whrl.pl/RcRPg4

[thejeg]

There isn't anything wrong with my line or my setup. I can easily receive full speeds pretty much whenever I want as long as I multi-thread the download.

Thejeg, do you have access to internet from exetel? Why don't you try the europhase ozspeedtest test and post your results here. I'm curious to see if you would achieve over 250KB/s.

Here are my current results: as you can see I can achieve 720KB/s from a gold coast (QLD) hosted site, yet only 27KB/s from europhase.
http://whrl.pl/RcRPg4

I have checked your past usage records and It appears that your line is being saturated.

For testing purposes, can you please stop doing any uploads (P2P torrent, Software updates, etc...) and provide me few more speed test results?

[IMSancho]

Is there any update on my incident?

[IMSancho]

Still waiting to hear anything about my incident...

[Musicinbed]

I have checked your past usage records and It appears that your line is being saturated.

For testing purposes, can you please stop doing any uploads (P2P torrent, Software updates, etc...) and provide me few more speed test results?

Do you know what the term saturated means thejeg? If my line was 'saturated' then it would be downloading at 1.2MB/s constantly, having only downloaded <110GB this month though shows my line is far from 'saturated'. The usage that you saw on my account was simply my regular usage, yes I allow things to upload during the day if that's what you mean?
I usually make sure to exit P2P clients before I do a speed test, if not, I don't see the harm with it trickle uploading 7KB/s whilst I run a test like this.

I don't have anything downloading whilst I test my speed if that's what you mean, or anything uploading (usually..).
ANYWAY, here are some fresh speed tests: http://whrl.pl/RcR3ij I made sure to exit all P2P and stop all downloads before conducting them.

At the moment my broadband is horrible, it has been horrible for most of the day. We've also discovered that at the moment it hits midnight both of our speeds spring back up to almost full speed again. I don't think anyone but exetel has the power to make such a drastic change in performance in such a swift immediate move. Have you seen IMSancho's chart? http://home.exetel.com.au/imsancho/speedresults.html
We get good speeds from midnight till around 9:30am and then they plummet, and from 6pm onwards it's absolutely terrible.
I really hope exetel can figure out what is wrong.

[slave1]

At the moment my broadband is horrible, it has been horrible for most of the day.

Same here, QLD, Middle Ridge exchange. Ticket #4362942.

Response: advised to power cycle modem. Did so, speeds still crap as at time of this post.

Not a huge downloader, sitting on 27.5GB this month on an OCV200/35 plan. I'd average around 40GB a month since changing to this plan in Feb '11. Same results on 3 different modems.

[IMSancho]

I have finally had a response, asking me to disconnect all devices for a line test. I've done so and am waiting to hear back so I can reconnect. The only upside is that the speeds I am getting using my iPhone as a 3g modem are considerably higher than I was getting on my ADSL2 connection --__--

All I can do is keep going through the motions, but It is very apparent what the problem here is: Exetel have much too little international capacity for the amount of users they currently have subscribed. The results we are seeing are not going to be caused by my line, or Slave1's modem, or a problem local to anyone else's set-up. More and more people are reporting the same thing, and there are probably many more that either don't know how to test or just accept that it is slow.

I'm pretty unimpressed with the performance of the helpdesk, after the initial response to my ticket completely disregarding the information I'd provided, it took a further 4 days to hear anything more back, and they want to test my line although the symptoms presented point glaringly to capacity problems...

[shoner]

I'm pretty unimpressed with the performance of the helpdesk, after the initial response to my ticket completely disregarding the information I'd provided, it took a further 4 days to hear anything more back, and they want to test my line although the symptoms presented point glaringly to capacity problems...

Can you please Pm me your help desk ticket number.

[IMSancho]

PM sent with ticket number.

I was asked to disconnect all devices and advise when done so the line could be tested, I did so straight away and have now been waiting for over 2 days with everything disconnected with no response despite emailing back 2 more times. Perhaps this was just a ploy to stop my graph updating

[IMSancho]

Tests finally run, router reconnected and graph updating once again from 1830: http://home.exetel.com.au/imsancho/speedresults.html

[IMSancho]

I've had to do a little bit of uploading to prepare for a trip (in London now) and surprise surprise get an email from support blaming that for the slow speeds over the last 2 weeks ---___---

Then, they insist I reply in 24 hours when they can't get around to doing a line test despite having all equipment disconnected for several days?

My reply:

This response is pretty infuriating.

It took exetel support 4 days to get back to me initially, then 3 days to conduct a line test, and now I have to respond in 24 hours?

I had been refraining from any uploads at all to provide better data on this issue for over a week, yet when I do upload a little bit to prepare for a trip, that is blamed? Were support taking so long just because they were waiting for something to come along to blame this on instead of addressing the obvious issue of insufficient capacity? I'm not sure if this is through malice or incompetence, but either way I will definitely be moving to a different ISP once my contract is up.

However unfortunately I am still stuck with exetel for another 2 months, so no the issue is not resolved, and is not being caused by saturation of my uplink. I am now out of the country and there will be very minimal use of my connection from scheduled systems, yet I can see right now that international speeds have yet again dived to around 30KB/s: http://home.exetel.com.au/imsancho/speedresults.html

Can't wait for churn, but will keep trying to get something done about this until then.

[IMSancho]

Now a reply asking for ping and traceroutes, I reply with these, and receive another reply asking to do a line test

Already did a line test, remember how I had everything disconnected for 3 days and had to chase it up 4 times before it was finally done? Seems none of the support staff talk to each other either.

Round and round we go....

[KavindaS]

Now a reply asking for ping and traceroutes, I reply with these, and receive another reply asking to do a line test

Already did a line test, remember how I had everything disconnected for 3 days and had to chase it up 4 times before it was finally done? Seems none of the support staff talk to each other either.

Round and round we go....

Hi,
I have replied to you through the email ticket with the reason why one of our support engineers did contact you. As confirmed through the email we will update you once we receive the update from the supplier.

[IMSancho]

After having the ticket escalated to provider, I've received a reply from Thuthimal advising an issue has been found. And looking at my speedtest graph, no peak time dip yesterday!

http://home.exetel.com.au/imsancho/speedresults.html

Hopefully this could be the issue being resolved, I'll be out of the country for a few more weeks so won't know for sure, but the change in the graph is very encouraging.

[ShaminG]

After having the ticket escalated to provider, I've received a reply from Thuthimal advising an issue has been found. And looking at my speedtest graph, no peak time dip yesterday!

http://home.exetel.com.au/imsancho/speedresults.html

Hopefully this could be the issue being resolved, I'll be out of the country for a few more weeks so won't know for sure, but the change in the graph is very encouraging.

I can confirm that the issue has been rectified yesterday .