Unusable during peak time.

Connection issues, drop outs or speed related faults for ADSL and ADSL2+ services
Post Reply
StAUG
Posts: 3
Joined: Sat Jul 26, 2008 1:56 pm
Location: Ballarat

Unusable during peak time.

Post by StAUG » Sat Jul 26, 2008 2:29 pm

Hello, I got my ADSL2 connected about a week back, and during peak/day time it has so far been slow to the point where it basically doesn't work.
Once midnight hits, though, it runs fine. Strange thing is exetel's main site (and this forum) always loads more or less instantly (no matter time of day it is), and the speed test (either exetels internal one or www.ozspeedtest.com) will never give a dl speed of less that 150kB/s and usually sits around the 180-190kB/s mark. A 1MB update through windows at the same time of day takes at least 20 minutes, and downloading anything from internet explorer won't give me a speed above 3kB/s. Since for the other 12 hours a day the net works fine I don't see how it can be a hardware or set up fault, it's almost like my service was activated with peak time throttling built in.

Line attenuation is 48.0dB and the attainable rate on the line is only about 3000kbp/s, but I live a ways from the exchange and my house is long way in off the road, so I kinda expectated that. A max download speed of 200kB/s doesn't bother me, but it only works exactly half the time. Anyone had issues like this?

James D

Re: Unusable during peak time.

Post by James D » Sat Jul 26, 2008 5:41 pm

Can you please complete a couple of tracerts and pings to a few sites and post them here.

CoreyPlover
Volunteer Site Admin
Posts: 5922
Joined: Sat Nov 04, 2006 2:24 pm
Location: Melbourne, VIC

Re: Unusable during peak time.

Post by CoreyPlover » Sun Jul 27, 2008 12:28 am

...perhaps one set during peak and another set during offpeak would be incredibly useful for comparison too.

StAUG
Posts: 3
Joined: Sat Jul 26, 2008 1:56 pm
Location: Ballarat

Re: Unusable during peak time.

Post by StAUG » Sun Jul 27, 2008 1:32 pm

C:\Users\StAUG>ping www.exetel.com.au

Pinging www.exetel.com.au [220.233.0.9] with 32 bytes of data:
Reply from 220.233.0.9: bytes=32 time=50ms TTL=61
Reply from 220.233.0.9: bytes=32 time=49ms TTL=61
Reply from 220.233.0.9: bytes=32 time=49ms TTL=61
Reply from 220.233.0.9: bytes=32 time=49ms TTL=61

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

C:\Users\StAUG>ping www.facebook.com

Pinging www.facebook.com [69.63.178.14] with 32 bytes of data:
Reply from 69.63.178.14: bytes=32 time=214ms TTL=242
Reply from 69.63.178.14: bytes=32 time=212ms TTL=242
Reply from 69.63.178.14: bytes=32 time=211ms TTL=242
Reply from 69.63.178.14: bytes=32 time=210ms TTL=242

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

C:\Users\StAUG>ping www.purepwnage.com

Pinging www.purepwnage.com [69.17.116.124] with 32 bytes of data:
Reply from 69.17.116.124: bytes=32 time=230ms TTL=45
Reply from 69.17.116.124: bytes=32 time=229ms TTL=45
Reply from 69.17.116.124: bytes=32 time=226ms TTL=45
Reply from 69.17.116.124: bytes=32 time=227ms TTL=45

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

C:\Users\StAUG>ping www.ozspeedtest.com

Pinging ozspeedtest.com [122.201.80.100] with 32 bytes of data:
Reply from 122.201.80.100: bytes=32 time=51ms TTL=57
Reply from 122.201.80.100: bytes=32 time=58ms TTL=57
Reply from 122.201.80.100: bytes=32 time=52ms TTL=57
Reply from 122.201.80.100: bytes=32 time=64ms TTL=57

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

C:\Users\StAUG>ping www.google.com

Pinging www.l.google.com [74.125.19.103] with 32 bytes of data:
Reply from 74.125.19.103: bytes=32 time=210ms TTL=242
Reply from 74.125.19.103: bytes=32 time=209ms TTL=242
Reply from 74.125.19.103: bytes=32 time=215ms TTL=242
Reply from 74.125.19.103: bytes=32 time=212ms TTL=242

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

C:\Users\StAUG>ping www.google.com.au

Pinging www.l.google.com [74.125.19.147] with 32 bytes of data:
Reply from 74.125.19.147: bytes=32 time=210ms TTL=242
Reply from 74.125.19.147: bytes=32 time=210ms TTL=242
Reply from 74.125.19.147: bytes=32 time=210ms TTL=242
Reply from 74.125.19.147: bytes=32 time=210ms TTL=242

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

C:\Users\StAUG>ping www.telstra.com

Pinging www.telstra.com [144.135.19.10] with 32 bytes of data:
Reply from 144.135.19.10: bytes=32 time=108ms TTL=245
Reply from 144.135.19.10: bytes=32 time=108ms TTL=245
Reply from 144.135.19.10: bytes=32 time=123ms TTL=245
Reply from 144.135.19.10: bytes=32 time=85ms TTL=245

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

C:\Users\StAUG>tracert www.exetel.com.au

Tracing route to www.exetel.com.au [220.233.0.9]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 52 ms 50 ms 48 ms candlenut-web.exetel.com.au [220.233.0.9]

Trace complete.

C:\Users\StAUG>
C:\Users\StAUG>tracert www.google.com

Tracing route to www.l.google.com [74.125.19.99]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 49 ms 408 ms 52 ms 252.0.233.220.exetel.com.au [220.233.0.252]
4 48 ms 50 ms 48 ms 10.0.1.2
5 53 ms 49 ms 50 ms 34.2.233.220.exetel.com.au [220.233.2.34]
6 50 ms 50 ms 52 ms Vlan366.o2gsc76f03.optus.net.au [203.202.84.65]

7 202 ms 203 ms 199 ms 203.208.169.58
8 201 ms 203 ms 199 ms 216.239.46.180
9 219 ms 210 ms 210 ms 209.85.253.178
10 214 ms 217 ms 215 ms 209.85.251.94
11 212 ms 208 ms 209 ms cf-in-f99.google.com [74.125.19.99]

Trace complete.


Not sure how useful that is, since I don't know a goddamn thing about tracerts, although the request time out seems a bit suss. Anyways, hope that helps. I'll try and get another set after midnight tonight if I'm still up.

StAUG
Posts: 3
Joined: Sat Jul 26, 2008 1:56 pm
Location: Ballarat

Re: Unusable during peak time.

Post by StAUG » Mon Jul 28, 2008 1:22 am

Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\StAUG>ping www.exetel.com.au

Pinging www.exetel.com.au [220.233.0.9] with 32 bytes of data:
Reply from 220.233.0.9: bytes=32 time=52ms TTL=61
Reply from 220.233.0.9: bytes=32 time=52ms TTL=61
Reply from 220.233.0.9: bytes=32 time=52ms TTL=61
Reply from 220.233.0.9: bytes=32 time=50ms TTL=61

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

C:\Users\StAUG>ping www.telstra.com

Pinging www.telstra.com [144.135.19.10] with 32 bytes of data:
Request timed out.
Reply from 144.135.19.10: bytes=32 time=51ms TTL=245
Reply from 144.135.19.10: bytes=32 time=51ms TTL=245
Reply from 144.135.19.10: bytes=32 time=51ms TTL=245

Ping statistics for 144.135.19.10:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 51ms, Maximum = 51ms, Average = 51ms

C:\Users\StAUG>ping www.telstra.com.au

Pinging www.telstra.com.au [144.135.18.41] with 32 bytes of data:
Reply from 144.135.18.41: bytes=32 time=55ms TTL=244
Reply from 144.135.18.41: bytes=32 time=52ms TTL=244
Reply from 144.135.18.41: bytes=32 time=51ms TTL=244
Reply from 144.135.18.41: bytes=32 time=52ms TTL=244

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

C:\Users\StAUG>ping www.purepwnage.com

Pinging www.purepwnage.com [69.17.116.124] with 32 bytes of data:
Reply from 69.17.116.124: bytes=32 time=229ms TTL=45
Reply from 69.17.116.124: bytes=32 time=229ms TTL=45
Reply from 69.17.116.124: bytes=32 time=229ms TTL=45
Reply from 69.17.116.124: bytes=32 time=226ms TTL=45

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

C:\Users\StAUG>ping www.facebook.com

Pinging www.facebook.com [69.63.178.14] with 32 bytes of data:
Reply from 69.63.178.14: bytes=32 time=212ms TTL=242
Reply from 69.63.178.14: bytes=32 time=211ms TTL=242
Reply from 69.63.178.14: bytes=32 time=210ms TTL=242
Reply from 69.63.178.14: bytes=32 time=209ms TTL=242

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

C:\Users\StAUG>ping www.google.com.au

Pinging www.l.google.com [74.125.19.99] with 32 bytes of data:
Reply from 74.125.19.99: bytes=32 time=210ms TTL=242
Reply from 74.125.19.99: bytes=32 time=209ms TTL=242
Reply from 74.125.19.99: bytes=32 time=209ms TTL=242
Reply from 74.125.19.99: bytes=32 time=210ms TTL=242

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

C:\Users\StAUG>ping www.microsoft.com

Pinging lb1.www.ms.akadns.net [207.46.19.190] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

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

C:\Users\StAUG>tracert www.exetel.com.au

Tracing route to www.exetel.com.au [220.233.0.9]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 51 ms 50 ms 48 ms candlenut-web.exetel.com.au [220.233.0.9]

Trace complete.

C:\Users\StAUG>tracert www.microsoft.com

Tracing route to lb1.www.ms.akadns.net [207.46.19.190]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 56 ms 48 ms 49 ms 252.0.233.220.exetel.com.au [220.233.0.252]
4 51 ms 50 ms 67 ms 38.2.233.220.exetel.com.au [220.233.2.38]
5 50 ms 52 ms 50 ms 359-ge-0-0-0.GW5.SYD2.ALTER.NET [203.166.92.57]

6 51 ms 137 ms 52 ms 0.so-7-2-0.XT3.SYD2.ALTER.NET [210.80.33.189]
7 202 ms 198 ms 200 ms 0.so-4-3-0.IR1.LAX12.ALTER.NET [210.80.50.249]
8 200 ms 199 ms 198 ms 0.so-5-0-0.IL1.LAX9.ALTER.NET [152.63.48.65]
9 208 ms 209 ms 217 ms 0.so-1-3-0.XL1.PAO1.ALTER.NET [152.63.50.205]
10 222 ms 269 ms 255 ms 0.so-6-0-0.GW11.PAO1.ALTER.NET [152.63.48.169]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
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.

This was a bit after 12, I could download from www.microsoft.com at about 200kb/s. What the hell?

WilliamC
Posts: 369
Joined: Tue May 02, 2006 10:50 pm

Re: Unusable during peak time.

Post by WilliamC » Tue Jul 29, 2008 11:43 pm

Dear Sir,

Can i kindly suggest you email residentialsupport@exetel.com.au and attention this to william c, As i see this is an issue we will need to investigate in the networking team.

Regards

William C

WilliamC
Posts: 369
Joined: Tue May 02, 2006 10:50 pm

Re: Unusable during peak time.

Post by WilliamC » Wed Jul 30, 2008 10:27 pm

Dear Sir,

Can you kindly check your email as i have looked into your service and made some changes. Please test the service and get back to us if you still have any issues

Regards

William C

Tastech
Posts: 15
Joined: Sun Feb 29, 2004 11:07 pm

Re: Unusable during peak time.

Post by Tastech » Wed Aug 06, 2008 10:04 pm

HI
I am getting dl speeds of <400kbits per sec. even as low as 120kbps

At times i have had as high as 10Mbps but this slowness is becoming the norm.

time is 10.06pm 6 aug 08.
C:\Users\tastech>ping exetel.com.au

Pinging exetel.com.au [220.233.0.9] with 32 bytes of data:
Reply from 220.233.0.9: bytes=32 time=168ms TTL=61
Request timed out.
Reply from 220.233.0.9: bytes=32 time=199ms TTL=61
Reply from 220.233.0.9: bytes=32 time=112ms TTL=61

Ping statistics for 220.233.0.9:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 112ms, Maximum = 199ms, Average = 159ms


here is a tracert, time is 10pm 6 aug 2008.
C:\Users\tastech>tracert google.com

Tracing route to google.com [64.233.187.99]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms tastech2.gateway [192.168.1.254]
2 * * * Request timed out.
3 388 ms 139 ms 122 ms 252.0.233.220.exetel.com.au [220.233.0.252]
4 147 ms 121 ms 140 ms 38.2.233.220.exetel.com.au [220.233.2.38]
5 128 ms 149 ms 184 ms 359-ge-0-0-0.GW5.SYD2.ALTER.NET [203.166.92.57]

6 203 ms 134 ms 147 ms 0.so-7-2-0.XT4.SYD2.ALTER.NET [210.80.33.193]
7 302 ms 283 ms 301 ms 0.so-1-3-0.IR2.LAX12.Alter.Net [210.80.48.69]
8 * 392 ms 340 ms 0.so-5-0-0.IL2.LAX9.ALTER.NET [152.63.48.69]
9 351 ms 304 ms 269 ms 0.so-6-3-0.XT2.LAX7.ALTER.NET [152.63.112.69]
10 210 ms 228 ms 309 ms 0.so-7-0-0.BR1.LAX7.ALTER.NET [152.63.112.153]
11 272 ms 288 ms 268 ms 204.255.169.194
12 244 ms 209 ms 184 ms los-core-01.inet.qwest.net [205.171.32.9]
13 412 ms 391 ms 386 ms atl-core-01.inet.qwest.net [67.14.14.2]
14 360 ms 352 ms 360 ms atl-edge-18.inet.qwest.net [205.171.21.162]
15 414 ms 400 ms 368 ms 63.144.1.6
16 411 ms 338 ms 297 ms 64.233.174.2
17 355 ms 373 ms 374 ms 72.14.236.175
18 372 ms 332 ms 326 ms 216.239.49.222
19 374 ms 336 ms 580 ms jc-in-f99.google.com [64.233.187.99]

Trace complete.

Post Reply