Whirlpool

I'm getting really crap speeds today, i'm getting constant 512K speeds when i usually have a stable 2-3mb connection.

I was getting around 200k+ all of yesterday but today i'm getting constant dropouts and really slow speeds.

Does anyone know the root of this problem? Or does anyone have any similar problems?

Is any one willing to put theory to the test?

I have to agree at least in part with the OP's complaint.

In my case I am trying to enjoy a HD vimeo in this paid for period - without it buffering. No success.

From the site -

Do I need a fast internet connection?

Most residential cable and DSL connections should be more than adequate. If HD feels slow to load, trying turning off any background downloads or peer-to-peer sharing applications.
vimeo.com/help/hd

I figure 4 Mbps ought to be enough for a streaming site.

I have to absolutely agree, packets are dropping left right and center. I've done a tracert and there seems to be a problem at 34.2.233.220.exetel.com.au [220.233.2.34]. Its pinging out 1 out of 4 times. Please explain.


C:\>ping -t 220.233.2.34

Pinging 220.233.2.34 with 32 bytes of data:

Reply from 220.233.2.34: bytes=32 time=64ms TTL=250
Reply from 220.233.2.34: bytes=32 time=65ms TTL=250
Reply from 220.233.2.34: bytes=32 time=65ms TTL=250
Reply from 220.233.2.34: bytes=32 time=65ms TTL=250
Reply from 220.233.2.34: bytes=32 time=64ms TTL=250
Request timed out.
Request timed out.
Request timed out.
Reply from 220.233.2.34: bytes=32 time=66ms TTL=250
Reply from 220.233.2.34: bytes=32 time=63ms TTL=250
Reply from 220.233.2.34: bytes=32 time=65ms TTL=250
Reply from 220.233.2.34: bytes=32 time=66ms TTL=250
Request timed out.
Reply from 220.233.2.34: bytes=32 time=65ms TTL=250
Reply from 220.233.2.34: bytes=32 time=64ms TTL=250
Reply from 220.233.2.34: bytes=32 time=64ms TTL=250

Ping statistics for 220.233.2.34:
Packets: Sent = 16, Received = 12, Lost = 4 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 63ms, Maximum = 66ms, Average = 64ms

C:\>ping -t 220.233.2.34 > ping.txt
Pinging 220.233.2.34 with 32 bytes of data:

Request timed out.
Reply from 220.233.2.34: bytes=32 time=51ms TTL=250
Request timed out.
Reply from 220.233.2.34: bytes=32 time=53ms TTL=250
Reply from 220.233.2.34: bytes=32 time=52ms TTL=250
Request timed out.
Request timed out.
Reply from 220.233.2.34: bytes=32 time=53ms TTL=250
Reply from 220.233.2.34: bytes=32 time=53ms TTL=250
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 220.233.2.34: bytes=32 time=52ms TTL=250
Reply from 220.233.2.34: bytes=32 time=52ms TTL=250
Reply from 220.233.2.34: bytes=32 time=53ms TTL=250
Reply from 220.233.2.34: bytes=32 time=53ms TTL=250
Reply from 220.233.2.34: bytes=32 time=53ms TTL=250
Reply from 220.233.2.34: bytes=32 time=53ms TTL=250
Reply from 220.233.2.34: bytes=32 time=53ms TTL=250
Reply from 220.233.2.34: bytes=32 time=52ms TTL=250
Request timed out.
Reply from 220.233.2.34: bytes=32 time=53ms TTL=250
Reply from 220.233.2.34: bytes=32 time=56ms TTL=250
Reply from 220.233.2.34: bytes=32 time=53ms TTL=250
Reply from 220.233.2.34: bytes=32 time=53ms TTL=250
Reply from 220.233.2.34: bytes=32 time=55ms TTL=250
Reply from 220.233.2.34: bytes=32 time=55ms TTL=250

Ping statistics for 220.233.2.34:
Packets: Sent = 29, Received = 19, Lost = 10 (34% loss),
Approximate round trip times in milli-seconds:
Minimum = 51ms, Maximum = 56ms, Average = 53ms

WHY am I losing 1/3 of my Data???

I'm no wiz with pings, but I typed in the exact same thing as hibernator, and still haven't got any kind of response while writing this.

Hehe, he's told that command to output to a text file. Check ping.txt 's content :D

I get lots of disconnects and slow speed as well.
been like that since thursday

ARGH! What am I doing wrong? It says reply from 220.233.2.33 instead of 34?

Pinging 220.233.2.34 with 32 bytes of data:

Reply from 220.233.2.33: TTL expired in transit.

Reply from 220.233.2.33: TTL expired in transit.

Reply from 220.233.2.33: TTL expired in transit.

Reply from 220.233.2.33: TTL expired in transit.

Reply from 220.233.2.33: TTL expired in transit.

Reply from 220.233.2.33: TTL expired in transit.

Reply from 220.233.2.33: TTL expired in transit.

Reply from 220.233.2.33: TTL expired in transit.

Reply from 220.233.2.33: TTL expired in transit.

Reply from 220.233.2.33: TTL expired in transit.

Reply from 220.233.2.33: TTL expired in transit.

Request timed out.

Reply from 220.233.2.33: TTL expired in transit.

Reply from 220.233.2.33: TTL expired in transit.

Reply from 220.233.2.33: TTL expired in transit.

Reply from 220.233.2.33: TTL expired in transit.

Reply from 220.233.2.33: TTL expired in transit.

Reply from 220.233.2.33: TTL expired in transit.

Reply from 220.233.2.33: TTL expired in transit.

Reply from 220.233.2.33: TTL expired in transit.

Reply from 220.233.2.33: TTL expired in transit.

Reply from 220.233.2.33: TTL expired in transit.

Reply from 220.233.2.33: TTL expired in transit.

Reply from 220.233.2.33: TTL expired in transit.

Reply from 220.233.2.33: TTL expired in transit.

Reply from 220.233.2.33: TTL expired in transit.

Reply from 220.233.2.33: TTL expired in transit.

Reply from 220.233.2.33: TTL expired in transit.

Reply from 220.233.2.33: TTL expired in transit.

Reply from 220.233.2.33: TTL expired in transit.

Reply from 220.233.2.33: TTL expired in transit.

Reply from 220.233.2.33: TTL expired in transit.

Reply from 220.233.2.33: TTL expired in transit.

Reply from 220.233.2.33: TTL expired in transit.

Request timed out.

Ping statistics for 220.233.2.34:

Packets: Sent = 35, Received = 33, Lost = 2 (5% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

Try this chunderman:

tracert yahoo.com.

do that 3 times and post em here.

skeep writes...

Try this chunderman:

tracert yahoo.com.

do that 3 times and post em here.

I prefer Google.

Tracing route to google.com [72.14.207.99]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms home.gateway [192.168.1.254]

2 29 ms 27 ms 27 ms 202.3.96.58.exetel.com.au [58.96.3.202]

3 41 ms 42 ms 42 ms 1.3.96.58.exetel.com.au [58.96.3.1]

4 41 ms 44 ms 44 ms 241.0.233.220.exetel.com.au [220.233.0.241]

5 162 ms 52 ms 44 ms 10.0.1.2

6 42 ms 43 ms 41 ms 34.2.233.220.exetel.com.au [220.233.2.34]

7 44 ms 42 ms 43 ms Vlan366.o2gsc76f03.optus.net.au [203.202.84.65]

8 193 ms 192 ms 192 ms 203.208.169.154

9 219 ms 218 ms 219 ms 64.233.174.115

10 223 ms 221 ms 223 ms 216.239.46.51

11 292 ms 293 ms 294 ms 209.85.130.23

12 285 ms 285 ms 285 ms 72.14.233.113

13 286 ms 289 ms 285 ms 66.249.94.92

14 297 ms 288 ms 288 ms 72.14.236.130

15 288 ms 285 ms 287 ms eh-in-f99.google.com [72.14.207.99]

Trace complete.

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

1 <1 ms <1 ms 1 ms 192.168.1.1
2 36 ms 35 ms 36 ms 3.1.233.220.exetel.com.au [220.233.1.3]
3 36 ms 36 ms 35 ms 61.1.96.58.exetel.com.au [58.96.1.61]
4 36 ms 36 ms 36 ms 1.4.96.58.exetel.com.au [58.96.4.1]
5 37 ms 36 ms 38 ms 241.0.233.220.exetel.com.au [220.233.0.241]
6 478 ms 898 ms 893 ms 10.0.1.2
7 * 36 ms 37 ms 34.2.233.220.exetel.com.au [220.233.2.34]
8 37 ms 38 ms 37 ms Vlan366.o2gsc76f03.optus.net.au [203.202.84.65]

9 187 ms 187 ms 187 ms 203.208.169.154
10 226 ms 224 ms 224 ms 64.233.174.115
11 258 ms 227 ms 227 ms 216.239.46.51
12 288 ms 287 ms 288 ms 209.85.130.23
13 293 ms 292 ms 290 ms 72.14.233.113
14 291 ms 291 ms 290 ms 66.249.94.92
15 297 ms 293 ms 302 ms 66.249.94.118
16 292 ms 294 ms 293 ms eh-in-f99.google.com [72.14.207.99]

Trace complete.

I smell something fishy with exetel's part of the network, can u spot it 0_o

WHY the heck is hop 7 losing Data???
WHAT's up with that private machine 10.x taking 800ms!? :o

.~-hibernator time

C:\>tracert google.com >tracert.txt
Tracing route to google.com [64.233.167.99]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.254
2 25 ms 25 ms 26 ms 4.1.233.220.exetel.com.au [220.233.1.4]
3 26 ms 25 ms 25 ms 61.1.96.58.exetel.com.au [58.96.1.61]
4 25 ms 26 ms 26 ms 1.4.96.58.exetel.com.au [58.96.4.1]
5 26 ms 26 ms 27 ms 241.0.233.220.exetel.com.au [220.233.0.241]
6 26 ms 26 ms 26 ms 10.0.1.2
7 27 ms 26 ms 26 ms 34.2.233.220.exetel.com.au [220.233.2.34]
8 26 ms 26 ms 27 ms Vlan366.o2gsc76f03.optus.net.au [203.202.84.65]
9 185 ms 186 ms 185 ms 203.208.169.154
10 198 ms 198 ms 218 ms 64.233.174.115
11 198 ms 198 ms 205 ms 216.239.46.51
12 236 ms 228 ms 285 ms 209.85.130.23
13 264 ms 247 ms 239 ms 64.233.175.26
14 264 ms 287 ms 268 ms 216.239.46.48
15 262 ms 259 ms 268 ms 66.249.95.245
16 229 ms 234 ms 269 ms 72.14.232.53
17 266 ms 271 ms 270 ms 72.14.232.74
18 260 ms 267 ms 269 ms py-in-f99.google.com [64.233.167.99]

Trace complete.

Ping each hop continuously starting with the top. ping -t hopip and stop it after 60 seconds. The first IP to report several bad spikes or timeouts is the first point of failure.

We have our first point of failure:
220.233.0.241. hop 5.

I don't know if this helps anyone, but here's my results from Maitland 8192/384....

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

1 1 ms 1 ms 1 ms home.gateway [192.168.1.254]
2 27 ms 28 ms 27 ms 41.1.233.220.exetel.com.au [220.233.1.41]
3 29 ms 29 ms 28 ms 241.0.233.220.exetel.com.au [220.233.0.241]
4 28 ms 28 ms 28 ms 10.0.1.2
5 28 ms 29 ms 28 ms 34.2.233.220.exetel.com.au [220.233.2.34]
6 29 ms 28 ms 28 ms Vlan366.o2gsc76f03.optus.net.au [203.202.84.65]

7 187 ms 188 ms 187 ms 203.208.149.130
8 185 ms 186 ms 184 ms 209.85.253.178
9 197 ms 198 ms 184 ms 209.85.251.94
10 185 ms 185 ms 185 ms cf-in-f99.google.com [74.125.19.99]

Trace complete.

Tracing route to www.yahoo-ht3.akadns.net [209.131.36.158]
over a maximum of 30 hops:

1 1 ms <1 ms 1 ms home.gateway [192.168.1.254]
2 27 ms 27 ms 27 ms 41.1.233.220.exetel.com.au [220.233.1.41]
3 28 ms 28 ms 29 ms 241.0.233.220.exetel.com.au [220.233.0.241]
4 46 ms 27 ms 29 ms 10.0.1.2
5 30 ms 28 ms 28 ms 34.2.233.220.exetel.com.au [220.233.2.34]
6 28 ms 29 ms 28 ms Vlan366.o2gsc76f03.optus.net.au [203.202.84.65]

7 188 ms 187 ms 187 ms 203.208.186.10
8 188 ms 188 ms 190 ms g-1-0-0-p140.msr1.sp1.yahoo.com [216.115.107.53]

9 188 ms 188 ms 189 ms te-8-1.bas-a1.sp1.yahoo.com [209.131.32.17]
10 188 ms 189 ms 189 ms f1.www.vip.sp1.yahoo.com [209.131.36.158]

Trace complete.

I'm not experiencing any problems.

chunderman89 writes...

ARGH! What am I doing wrong? It says reply from 220.233.2.33 instead of 34?

Pinging 220.233.2.34 with 32 bytes of data:

i'm not wiz when it comes to networking (that course was over 2 years ago)
but I think basically TTL(time to live) expired at 220.233.2.33 before it reaches 34

every time it goes from 1 hop to another ttl is deducted (whether by one or more... my memory is blurry)

as for how ttl was initially determined - I think when it goes from 1 router to the next, the router determines the ttl (by adding or subtracted from the original value)

so my guess is the problem lies in the router's config (somewhere along the line)
but of course...pls do take my rambling with a grain of salt :)

edit: I've just completed my application a few days ago...thanks a lot guys, now I'm nervous about my decision to go naked with exetel :)

Their is definitely something going on with Exetel's network at the moment.

I'm on 1500/ 256 and tried download from www.ubuntu.com/download kUbuntu .iso download from the MIT* site and the largest download speed we could get was about 65-70 kB/s

Tried various other sites like download.com to microsoft and speeds seem to be consistently slow

This site always maxes my connection.

Doing tracert to the DNS 18.85.21.55 revealed clear path and expected pings. Yet download speeds are shocking. More like 512 kBps.

img401.imageshack.us/my....=80178375pn8.jpg

Anyone else?
Edited from here--------
* MIT= Massachusetts's Institute of Technology in USA

Bigbros writes...

Anyone else?

Pretty much maxing out my connection... 8192/384 at Maitland.

i179.photobucket.com/alb...WP/ubuntu710.jpg

Midnight Rider writes...

Pretty much maxing out my connection... 8192/384 at Maitland.

i179.photobucket.com/alb...WP/ubuntu710.jpg

Hi Thanks for that download test.

But that download you are showing is from Internode and would be through PIPE I was interested in downloads for OS*- Overseas.

Such as-

University Of Utah In America-

ubuntu.cs.utah.edu/relea...desktop-i386.iso

or Media Lab Massachusetts Institute of technology--

ubuntu.media.mit.edu/ubu...desktop-i386.iso

Using PIPE as measure as you did is irrelevant(edited from here-- to measure overseas download speeds)

Thanks.

Bigbros writes...

I was interested in downloads for OS*- Overseas.

Using PIPE as measure as you did is irrelevant

Sorry, I thought you were actually trying to download the file. I didn't realise this was just an academic thing.

My results from those two OS sources are a bit slower than the local mirror, but still OK I think...

i179.photobucket.com/alb...P/ubuntu-mit.jpg

i179.photobucket.com/alb.../ubuntu-utah.jpg

free period last night and tonight has been shockingly slow

Midnight Rider writes...

Sorry,

No problem.

this was just an academic thing.

Yes they are academic institues that the downloads are coming from with very reliable and consisently fast download speeds. They are good measure and start to determine if their is problem with an ISP provider.

Already done usual isolation test etc.

Exetel with my connection ATM is having problems. Glad yours is not.

Was wondering if anyone else is having problems?

Bigbros writes...

They are good measure and start to determine if their is problem with an ISP provider.

Exetel with my connection ATM is having problems.

One would think that if there was a problem with an ISP, then that problem would affect all the users, not just random individuals from here, there, and everywhere.

It also might follow that if random individuals were experiencing problems, then those problems might be due to random circumstances affecting those random user's connections.

the price can either go up or bonus come down to 24 gb. And I won't be voting for either option.

So slow tonight going at a crawl

Midnight Rider writes...

One would think that if there was a problem with an ISP, then that problem would affect all the users

Just because your internet connection is good does not mean that everyone's internet connection is perfect.

Your connection is only your connection experience.

Please look at my previous posts. Which show that 1500/256 connection is only achieving 512k speed.

Do you consider that satisfactory?

Yeah i'm the same, going really slow tonight :(

I will have to ask local xnor (if I get the chance) whether he thinks being able to stream HD video, from an overseas source, is expecting too much of an Australian provider @ 95 buckeroonies.
(refer: www.vimeo.com/hd)

Bigbros writes...

Just because your internet connection is good does not mean that everyone's internet connection is perfect.

Very true.

Please look at my previous posts. Which show that 1500/256 connection is only achieving 512k speed.

Do you consider that satisfactory?

Not at all, but please try to understand what I'm saying. I'm certainly not saying that you don't have a problem.

However, you're suggesting that because your connection is not performing at it's maximum (along with a few others), then that must mean that Exetel's network is experiencing problems. I'm suggesting that this is not necessarily the case.

The fact that I'm not having problems (along with a multitude of others), means that your problem(s) probably exists somewhere between your own system or premises, and your link with Exetel.... and most likely between your own system and premises, and your local exchange.

Two of the most important things that I have learned over the years when troubleshooting, is not to assume anything, and to triple-check everything.

hibernator writes...

I will have to ask local xnor (if I get the chance) whether he thinks being able to stream HD video, from an overseas source, is expecting too much of an Australian provider @ 95 buckeroonies.

I'm still able to stream these videos at 1:47am, at about the same rate as earlier on my 8192/384 connection.

Sorry if that's not what you wanted to hear... just trying to add input.

(They sure do look purdy) :-)

Is it better to discuss this on exetel forum so that they see that there's a problem?

WHOA, ok, this has gone far enough.

Left on Torrent from 12am to 8.45am until now and all it downloaded was 200MB.

WTH? By now I usually have downloaded about 3GB's the least.

What.The.Hell. is going on Exetel? Wait I don't care...

Just FIX it !!!

People, a certain torrent that usually mazes out my connection and has 15,000 seeds is only going at 15kb/s.

sp0radic writes...

Is it better to discuss this on exetel forum so that they see that there's a problem?

And have it deleted by them ??

Well, I'm still getting slow speeds this morning.

Kevin writes...

WHOA, ok, this has gone far enough.

Left on Torrent from 12am to 8.45am until now and all it downloaded was 200MB.

Yes, I'm the same. Friday morn (1st March after 12am) around 147kb/s, Sat 25kb/s and this morning around 20kb/s.

HOWEVER... downloaded something during peak time last night and it maxed out the connection at 152kb/s!!!

Now either they fixed the underwater cable for a few minutes during peak time, or I was just lucky?!

Midnight Rider writes...

The fact that I'm not having problems (along with a multitude of others), means that your problem(s) probably exists somewhere between your own system or premises, and your link with Exetel....

You are trying to blame my network set up at home. Something have seen you do quite often on Whirlpool.

If it was my families connection setup or problem with computers on the premises- why is it possible for us to download(grab data) from the Exetel mirror at full speed.

img207.imageshack.us/my....=24948063av3.jpg

Yet not from the rest of the WWW(internet).

Why? Because it is not local set up issue.

Bigbros writes...

You are trying to blame my network set up at home. Something have seen you do quite often on Whirlpool.

Perhaps he has a point?

Midnight Rider writes...

Sorry if that's not what you wanted to hear... just trying to add input.

Also meant to sat Thanks for your input. :-) Good to know it's not everyone.

For me.

Cache is broken at the moment?

Jaike writes...

Cache is broken at the moment?

Same with my 10kb/s speeds.

WTF? Off-peak just ended quite literally and my speeds went to 150kb/s.

DOUBLE EDIT: My speeds just went back to 10kb/s.

Yeah my websites are loading very slowly at the moment (nothing running in the background using an ethernet cable). Checked the graph looks like its maxing.

UPDATE: Turned encrytion on, and speeds went to 50kb/s. Must be something to do with the cache and something else Exetel.

Yeah, hopefully - Legend - Steve Waddington is stuffing an extra 12 tb in as an enhancement setting.

C:\>tracert 220.233.2.34 tracert.txt
Tracing route to 220.223.2.34 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.254
2 25 ms 25 ms 25 ms 4.1.233.220.exetel.com.au [220.233.1.4]
3 26 ms 25 ms 25 ms 61.1.96.58.exetel.com.au [58.96.1.61]
4 25 ms 25 ms 25 ms 1.4.96.58.exetel.com.au [58.96.4.1]
5 27 ms 26 ms 26 ms 241.0.233.220.exetel.com.au [220.233.0.241]
6 26 ms 26 ms 26 ms 10.0.1.1
7 * * 27 ms 38.2.233.220.exetel.com.au [220.233.2.38]
8 * * * Request timed out (to hop 30).

Trace complete.

My GAWD, what is the meaning of this??

Yes speeds are verrrrry slow today

maybe the excess load with everyone at home due to the rainy weather in Sydney is straining the steam-powered exetel network

remember "bandwidth upgrades"?

funny how they stopped announcing or talking about those over a year ago

chunderman89 writes...

People, a certain torrent that usually mazes out my connection and has 15,000 seeds is only going at 15kb/s

ha now who's at the other end of the stick. It doesn't feel nice does it?.

My dropputs seem to have dropped to only a few per day now. But my speed is still bad. Sync speed max of 1600. Even the noise in my line has fallen to about %50 over night.

My speed is now at a steady 140-160k/s

mojom@@n writes...

my speed is still bad. Sync speed max of 1600. Even the noise in my line has fallen to about %50 over night.


Your sync speed fluctuates wildly, you are getting drop-outs and you have noise on your line. Does that tell you anything other than Exetel is a crap ISP?

mojom@@n writes...

ha now who's at the other end of the stick. It doesn't feel nice does it?.

My dropputs seem to have dropped to only a few per day now

I only said torrents weren't working, nothing else.

this sucks

i'm getting like 10kbps from HTML and 5kbps from torrents.

TPG here i come.

xnor writes...

Your sync speed fluctuates wildly, you are getting drop-outs and you have noise on your line. Does that tell you anything other than Exetel is a crap ISP?

Exetel is a great ISP. When did i say they were crap?

By the way if you read just above i think 2 or 3 post above i have stated that things are getting bit better . atleast speed is about 4 times faster now.

C:\>tracert vimeo.com >tracert.txt

Tracing route to vimeo.com [72.3.218.217]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.254
2 25 ms 25 ms 25 ms 4.1.233.220.exetel.com.au [220.233.1.4]
3 26 ms 25 ms 25 ms 61.1.96.58.exetel.com.au [58.96.1.61]
4 25 ms 25 ms 26 ms 1.4.96.58.exetel.com.au [58.96.4.1]
5 26 ms 26 ms 27 ms 241.0.233.220.exetel.com.au [220.233.0.241]
6 26 ms 26 ms 26 ms 10.0.1.1
7 26 ms 26 ms 26 ms 38.2.233.220.exetel.com.au [220.233.2.38]

8 26 ms 26 ms 26 ms 359-ge-0-0-0.GW5.SYD2.ALTER.NET [203.166.92.57]
9 26 ms 26 ms 26 ms 0.so-0-2-0.XT1.SYD2.ALTER.NET [210.80.33.189]
10 182 ms 181 ms 182 ms 0.so-1-3-0.IR1.LAX12.Alter.Net [210.80.48.125]
11 181 ms 182 ms 182 ms 0.so-5-0-0.IL1.LAX9.ALTER.NET [152.63.48.65]
12 189 ms 189 ms 189 ms 0.so-3-0-0.XL1.SJC7.ALTER.NET [152.63.0.150]
13 191 ms 191 ms 190 ms POS6-0-0.GW4.SJC7.ALTER.NET [152.63.48.241]
14 190 ms 191 ms 190 ms teliasonera-test-gw.customer.alter­ .net [157.130.215.70]
15 203 ms 202 ms 202 ms las-bb1-link.telia.net [213.248.80.17]
16 236 ms 235 ms 236 ms dls-bb1-link.telia.net [213.248.80.14]
17 276 ms 402 ms 424 ms rackspace-114734-dls-bb1.c.telia.n­ et [213.248.92.30]
18 232 ms 230 ms 232 ms vlan903.core3.dfw1.rackspace.com [72.3.128.53]
19 232 ms 231 ms 233 ms aggr107a.dfw1.rackspace.net [72.3.129.77]
20 231 ms 232 ms 232 ms vimeo.com [72.3.218.217]

Trace complete.

I just want to be able to stream my www.vimeo.com/hd videos properly. Is it TOO MUCH???

Only site I can get a valid speed result from is
www.speedtest.net/result/229846858.png
= 5932 Kbps
Others I've tested are sub MegaBit! :O gRRR

hibernator writes...

Is it TOO MUCH???

Of course it is.

Guessing it's Optus Wholesale not Exetel

forum-replies.cfm?t=910933
forum-replies.cfm?t=910060

Chaase writes...

Guessing it's Optus Wholesale not Exetel

Optus Wholesale don't supply ADSL1, which is what most of the users in this thread are on.

GAWD it's TERRIBLE

C:\>ping -n 20 220.233.2.34 >ping.txt

Pinging 220.233.2.34 with 32 bytes of data:

Reply from 220.233.2.34: bytes=32 time=57ms TTL=250
Reply from 220.233.2.34: bytes=32 time=52ms TTL=250
Request timed out.
Reply from 220.233.2.34: bytes=32 time=55ms TTL=250
Reply from 220.233.2.34: bytes=32 time=52ms TTL=250
Request timed out.
Reply from 220.233.2.34: bytes=32 time=52ms TTL=250
Reply from 220.233.2.34: bytes=32 time=53ms TTL=250
Reply from 220.233.2.34: bytes=32 time=58ms TTL=250
Request timed out.
Reply from 220.233.2.34: bytes=32 time=53ms TTL=250
Request timed out.
Reply from 220.233.2.34: bytes=32 time=54ms TTL=250
Reply from 220.233.2.34: bytes=32 time=54ms TTL=250
Reply from 220.233.2.34: bytes=32 time=54ms TTL=250
Reply from 220.233.2.34: bytes=32 time=54ms TTL=250
Reply from 220.233.2.34: bytes=32 time=52ms TTL=250
Reply from 220.233.2.34: bytes=32 time=53ms TTL=250
Reply from 220.233.2.34: bytes=32 time=53ms TTL=250
Reply from 220.233.2.34: bytes=32 time=53ms TTL=250

Ping statistics for 220.233.2.34:
Packets: Sent = 20, Received = 16, Lost = 4 (20% loss),
Approximate round trip times in milli-seconds:
Minimum = 52ms, Maximum = 58ms, Average = 53ms

They don't give a damn...aaaAAAAHHHHHH

speeds, pings etc are up and down like a yoyo for me, I am going to log a support ticket. Will see how I go

Edit: ARRRGGGGGGGHHHHH timeouts on whirlpool as well....

Chaase writes...

Guessing it's Optus Wholesale not Exetel

forum-replies.cfm?t=910933
forum-replies.cfm?t=910060

Theres always someone to blame.. Exetel seems to be never at fault.

Either way, you PAY Exetel for their services NOT Optus.

Exete and Optus must have a SLA in place to combat any speed/performance issues between the two... but either way, you pay Exetel for internet service and not Optus.

MY Internet has been real slow of late.. html browsing goes to a crawl, and watching videos off YOUTUBE is a joke.. it just buffers.

P2P speeds however seemed to be ok.. thats probably due to the p2p cache packets.

Dense

hibernator writes...

I just want to be able to stream my www.vimeo.com/hd videos properly. Is it TOO MUCH???

I can't even do this tonight.

Last night a speed test to San Francisco resulted in over 12000 kb/s.
www.speedtest.net/result/229528449.png

Tonight I'm lucky to get over 1000 kb/s!!!
www.speedtest.net/result/229890986.png

Dense \/\/arrior writes...

Either way, you PAY Exetel for their services NOT Optus.

True. But Exetel can't do anything about it when their supplier decides to spill the the milk. If Exetel had to reimburse customers everytime they had an outage because of Optus or Telstra, there would be no Exetel.

Getting the same problem here. Except ADSL2+ and only getting about 33k. Logged a fault with Exetel but don't expect much to come of it. Line sync is at nearly 16000k but getting slow actual speeds. Can't get games off steam. Can't play online with pings over 800ms. Losing almost 50% of my data too.

Pinging google.com [64.233.167.99] with 32 bytes of data:
Reply from 64.233.167.99: bytes=32 time=396ms TTL=240
Reply from 64.233.167.99: bytes=32 time=361ms TTL=240
Reply from 64.233.167.99: bytes=32 time=348ms TTL=240
Reply from 64.233.167.99: bytes=32 time=493ms TTL=240
Request timed out.
Reply from 64.233.167.99: bytes=32 time=709ms TTL=240
Request timed out.
Reply from 64.233.167.99: bytes=32 time=305ms TTL=240
Request timed out.
Request timed out.
Reply from 64.233.167.99: bytes=32 time=393ms TTL=240
Reply from 64.233.167.99: bytes=32 time=427ms TTL=240
Request timed out.
Request timed out.
Reply from 64.233.167.99: bytes=32 time=408ms TTL=240
Request timed out.

Ping statistics for 64.233.167.99: Packets: Sent = 16, Received = 9, Lost = 7 (43% loss),
Approximate round trip times in milli-seconds: Minimum = 305ms, Maximum = 709ms, Average = 426ms

I'll be very impressed if this even manages to submit. Tested absolutely anything I can think of from here but if anyone has suggestions as to why it's going so slow, please reply.
Maz

xnor writes...

Your sync speed fluctuates wildly, you are getting drop-outs and you have noise on your line. Does that tell you anything other than Exetel is a crap ISP?

1) sync speeds involve only the Telstra copper between the residential premises and the Telstra exchange;

2) dropouts involve the same infrastructure;

3) noise on the line involves the same infrastructure.

None of the above can be caused by Exetel, it's just not possible as they don't even have access to it. Hey, but don't let the facts stand in the way of a good story.

a.c.d writes...

sync speeds involve only the Telstra copper between the residential premises and the Telstra exchange;

I don't think it's only the copper.

My Telstra contract runs out this month, and I've been looking at Exetel ADSL2+ as an option (it's cheaper than the 512 ADSL1 plan I'm on with Telstra atm...lol, but Telstra speeds have always been very reliable). The only thing that puts me off is all this talk of speed issues (in some cases very serious speed issues).

I don't do alot on the internet after midnight. Just the odd bit of browsing, and I sometimes watch some internet tv and sport channels (usually only 200-400kb/s streams, not like HD or anything) and the odd youtube video. I don't download torrents ever or play games online after midnight.

As long as I have good speed during the day, and at the very least 512 speeds (as good as my current plan) after midnight I think I would be quite happy with Exetel. According to the number finder, I believe I'm on a Powertel Exetel exchange (I thought I read somewhere that can make a difference), and I'm only 1km from the exchange.

So what's the current opinion on speeds right now. Do you guys think I'd be alright with Exetel?

cookiezncream writes...

watch some internet tv and sport channels (usually only 200-400kb/s streams, not like HD or anything)

Pity. 400 kbit is a bit of junk. I feel U-Tube needs to up the quality level or it might lose its top spot.

So what's the current opinion on speeds right now. Do you guys think I'd be alright with Exetel?

Well the cache failed to live up to marketed hype, so unless you have a high powered usenet client up your sleeve, or a download manager, you will be facing sub broadband* (*I define as 4 mbps) speeds night OR day. Having said that, PowerTel gives you the best chance. Optus performs like a rotten piece of garbage for many people (for-ged aboud it), while Telstra is o-kaish I guess

I tried all weekend to get a decent video site streaming over E TEL and came up with buffering throughout. "That don't impress me much" - as the pop song goes.

My current test is the brooklyn bridge video on www.vimeo.com/hd/page:19 The video is only 167s length but on ADSL took 407s to load. That is 2.4x longer than 'real' time to load. A typical result for me using this otherwise awesome new site.

Looking at above copy of brooklyn bridge stored in firefox cache I can see it is only a 35 MB data file for the HD video. From the data size, and from tests based on monitoring software, I am able to conclude my streaming rate varied from 5.8 KB/s to 227.5 KB/s, but only averaged 86.9 KB/s - very poor.

I may as well have taken a 1500/256 kbps line speed for browsing that site.

It's a sin to provide bandwidth so poor that video from a decent site such as www.vimeo.com/hd, can't stream properly. It only requires (35 MB / 167s); 210 KB/s to be maintained.

hibernator writes...

It's a sin to provide bandwidth so poor that video from a decent site such as www.vimeo.com/hd, can't stream properly.

As you know from your enquiries in the Internode forum here, even they have issues with your decent site.

that site is not streaming well for me.

my speeds to USA east coast right now are 714/374 on *speed test*.
they were better earlier at 2060/351 .
the latter is the more usual but the former is not unknown.

local speed test has gone from 4496/665 earlier to 6665/654now

none of these speeds, now or earlier, give me clean viewing of that very interesting site

since i dont understand much if anything about this site.............is there a minimum dowload speed that is necessary??

thanks

um
replying to myself

my speeds have been all over the place and the download on that site is also all over the place.

pity

edited to add

well now it works seamlessly with no change in anything.
it dosnt seem speed dependant actually... tho my speeds now are 3500kps down to east coast USA

I don't know how long my internet will last but i will make it quick.

I lost sync at about 8am and just got internet back but it is flaky at best. I have lodged a support ticket with exetel and with telstra. Just have to wait for the tech to come out and fix the problem now.

mojom@@n writes...

I don't know how long my internet will last but i will make it quick.

Man....

Perhaps you should get a TELSTRA techie (disgustingly, disgusting I know) to come out and check your line, from the exchange to your residence, because the cost for it would justify the lack of internet you are being provided.

This just seems really bizarre to me. www.vimeo.com/hd

Internode users have claimed 600 KB/s or no problem
forum-replies.cfm?t=910536#r2
forum-replies.cfm?t=910536#r11
forum-replies.cfm?t=910536#r14
forum-replies.cfm?t=910536#r15
forum-replies.cfm?t=910536#r17
forum-replies.cfm?t=910536#r18

Internode users have claimed a problem eg stuttering
forum-replies.cfm?t=910536#r4
forum-replies.cfm?t=910536#r12
forum-replies.cfm?t=910536#r16
forum-replies.cfm?t=910536#r19
forum-replies.cfm?t=910536#r20

We are now in our evening time slot, and around where the feed is geographically situated the viewers are in bed (see: US time).

So I invite users to visit this page for a manual speed test. www.vimeo.com/hd/page:3

I propose the "Solar" video which is the first link, is a short 90s in length, and 18.9 MB in data size.

IF you can view this wonderful HD video in 90s congratulations, your connection is sustaining the 210 KB/s rate required.

IF you cannot view it in 90s then you've my sympathy, you've had as much luck as myself and several Internode users as provided above. It seems to work for some and not others, so more data would be useful.

If you use Firefox you can clear your cache via Tools->Clear private data, refresh the page, then view the file again. Now use a timer to COUNT how many seconds it actually takes to retrieve the video 18.9 MB from the server.

To determine the severity of the problem; Divide the data '18.9' by the number of seconds '238' (in my case), then multiply by 1000 to get your transfer rate.

I got a DISGRACEFUL (18.9 / 238 x 1000); 79.4 KB/s to deal with as my rate, and am personally disappointed by my 8 mbit connection if 0.64 mbps is all it gets!!

chunderman89 writes...

Perhaps you should get a TELSTRA techie

I said that in the above post.

I have requested a tech from both telstra and from Exetel to find the problem.
Telstra said i only have to pay for the tech if the problem is my equipment. I know there is a problem with the line as you can barely here the dial tone because of the noise distortion. I rang 1194 and i couldn't even understand what the computer time was saying. Exetel said that telstra charge $120 for a false alarm but telstra told me that exetel are wrong and it is only $105.

Solar video

o Exetel (PowerTel Sync 20222/1021Kbps) bad stuttering - gave up.
o aaNet (ADSL 1500/256Kbps) bad stuttering/rebuffering - gave up.
o Aarnet (direct link to Sydney backbone POP "A") 29Kbps!

Given the Aarnet result, I question the reliability of the source site which might explain the variable results.

mojom@@n writes...

I rang 1194 and i couldn't even understand what the computer time was saying.

in that case, forget that you have ADSL and just ring telstra faults and report that your line is noisy. Won't cost anything, especially if when you call you can't hear the call centre clearly and have to ask them to repeat the questions! No need to mention you have any ADSL problems, just stick to the noisy line, can't hear on the phone etc.
When the tech fixs the line so you can use the phone normally, then check you ADSL. It will probably be great!

I had 6 stutters on that video, NONE in the first 50 seconds of the video.

I'm on Exetel, Adsl1-8mb, synched at 7616k.

Normally my speeds haven't been too bad either...

a.c.d writes...

Given the Aarnet result, I question the reliability of the source site which might explain the variable results.

As would I. And with that I searched the www.vimeo.com/forums and there is no post or evidence that would suggest the HD site is performing less than reliably.

But this does not explain the mixed bag of results experienced by Australian internet users accessing these videos. Further testing required: www.vimeo.com/hd/page:3

hibernator writes...

mixed bag of results experienced by Australian internet users accessing these videos

a couple of nights ago I was streaming these videos fine.
Tonight - heaps of stutters; too many to actually make it worth waiting for the video to download.
I'm on Telstra 8M/386k and everything else seems to be "as it was the other night" (ie other sites are just as fast as they were the other night)
so maybe this site is not be as reliable as we need it to be to do these tests on.

Kevin writes...

Tonight - heaps of stutters; too many to actually make it worth waiting for the video to download.
I'm on Telstra 8M/386k

Then it seems I am not the only one having difficulty pulling video from that site. I don't know. Perhaps you are right.

hibernator writes...

But this does not explain the mixed bag of results experienced by Australian internet users accessing these videos.

Different paths?

Exetel/PowerTel:

traceroute to vimeo.com (72.3.218.217), 64 hops max, 52 byte packets
1 router-3 (192.168.1.253) 0.373 ms 0.345 ms 0.220 ms
2 193.1.233.220.exetel.com.au (220.233.1.193) 25.238 ms 27.400 ms 28.038 ms
3 241.0.233.220.exetel.com.au (220.233.0.241) 27.639 ms 26.394 ms 28.237 ms
4 10.0.1.1 (10.0.1.1) 27.142 ms 26.995 ms 26.337 ms
5 38.2.233.220.exetel.com.au (220.233.2.38) 25.343 ms 25.736 ms *
6 359-ge-0-0-0.GW5.SYD2.ALTER.NET (203.166.92.57) 30.696 ms 27.984 ms 31.029 ms
7 0.so-0-2-0.XT1.SYD2.ALTER.NET (210.80.33.189) 24.941 ms 26.297 ms 25.448 ms
8 0.so-1-3-0.IR1.SAC2.Alter.Net (210.80.48.189) 176.825 ms 178.455 ms 176.078 ms
9 0.so-2-0-0.IL1.SAC1.ALTER.NET (152.63.48.33) 181.105 ms 179.592 ms 176.794 ms
10 0.so-4-0-0.XL1.SJC7.ALTER.NET (152.63.48.6) 182.424 ms 183.005 ms 181.162 ms
11 POS6-0-0.GW4.SJC7.ALTER.NET (152.63.48.241) 184.805 ms 180.288 ms 181.493 ms
12 teliasonera-test-gw.customer.alter­ .net (157.130.215.70) 182.824 ms 183.423 ms 179.604 ms
13 las-bb1-link.telia.net (213.248.80.17) 192.192 ms 194.115 ms 196.095 ms
14 dls-bb1-link.telia.net (213.248.80.14) 230.449 ms 231.256 ms 231.226 ms
15 rackspace-114734-dls-bb1.c.telia.n­ et (213.248.92.30) 227.455 ms 227.144 ms 231.605 ms
16 vlan903.core3.dfw1.rackspace.com (72.3.128.53) 228.128 ms * 229.171 ms
17 aggr107a.dfw1.rackspace.net (72.3.129.77) 228.642 ms 228.760 ms 228.636 ms
18 * * *

aaNet/Telstra ADSL:

traceroute to vimeo.com (72.3.218.217), 64 hops max, 40 byte packets
1 router-4 (192.168.1.201) 0.520 ms 0.343 ms 0.242 ms
2 lo0.core-r1.nsw01.dataco.com.au (202.63.35.1) 10.123 ms 11.230 ms 11.755 ms
3 ge0-1.syd.dft.com.au (202.76.170.242) 12.065 ms 11.571 ms 11.265 ms
4 59.154.21.221 (59.154.21.221) 15.723 ms 11.381 ms 14.483 ms
5 ge-4-0-0-0.plapx-dr1.ix.singtel.co­ m (203.208.149.5) 174.285 ms 171.395 ms 172.167 ms
6 ge-5-2-1.mpr4.pao1.us.above.net (64.125.13.5) 170.691 ms 173.015 ms 172.110 ms
7 so-1-2-2.mpr2.sjc2.us.above.net (64.125.29.126) 177.883 ms 171.222 ms 171.908 ms
8 so-1-0-0.mpr4.lax9.us.above.net (64.125.26.29) 178.765 ms 180.941 ms 180.548 ms
9 so-0-3-0.mpr4.iah1.us.above.net (64.125.25.17) 214.293 ms 211.896 ms 215.026 ms
10 so-1-1-0.mpr2.dfw2.us.above.net (64.125.26.133) 217.269 ms 217.691 ms 216.508 ms
11 64.124.12.6.rackspace.com (64.124.12.6) 254.210 ms 263.293 ms 251.727 ms
12 vlan903.core3.dfw1.rackspace.com (72.3.128.53) 243.885 ms 252.233 ms 243.840 ms
13 aggr107a.dfw1.rackspace.net (72.3.129.77) 239.157 ms 237.389 ms 235.705 ms
14 * * *

Aarnet:

traceroute to vimeo.com (72.3.218.217), 30 hops max, 40 byte packets
1 gateway.xxx.xxx.xx (138.25.xxx.xxx) 0.415 ms 0.327 ms 0.278 ms
2 138.25.252.121 (138.25.252.121) 1.237 ms 1.376 ms 1.099 ms
3 172.16.0.1 (172.16.0.1) 1.355 ms 1.271 ms 2.398 ms
4 172.16.30.254 (172.16.30.254) 1.233 ms 1.336 ms 1.261 ms
5 GW-L2-5052.uts.edu.au (138.25.252.38) 0.969 ms 1.016 ms 1.016 ms
6 gigabitethernet1.er1.uts.cpe.aarne­ t.net.au (202.158.202.217) 2.089 ms 2.448 ms 2.738 ms
7 ge-1-1-2.bb1.a.syd.aarnet.net.au (202.158.202.209) 1.956 ms 1.814 ms 2.133 ms
8 so-2-1-2.bb1.a.pao.aarnet.net.au (202.158.194.174) 166.133 ms 157.136 ms 157.383 ms
9 p4-2-0-0.r05.plalca01.us.bb.gin.nt­ t.net (129.250.10.225) 157.264 ms 157.379 ms 157.127 ms
10 p64-1-0-0.r21.dllstx09.us.bb.gin.n­ tt.net (129.250.3.153) 202.875 ms 203.008 ms 202.578 ms
11 po-2.r02.dllstx09.us.bb.gin.ntt.ne­ t (129.250.2.174) 310.638 ms 362.894 ms 825.985 ms
12 * d1-1-2-1-5.a00.dllstx09.us.ce.veri­ o.net (157.238.225.222) 206.395 ms 207.219 ms
13 vlan903.core3.dfw1.rackspace.com (72.3.128.53) 209.305 ms 207.654 ms 626.995 ms
14 * 72.3.129.77 (72.3.129.77) 208.141 ms 204.753 ms
15 * * *

Hmmmm.

a.c.d writes...

Hmmmm.

Hmmm indeed. I get a clear path:

C:\>tracert vimeo.com >tracert.txt

Tracing route to vimeo.com [72.3.218.217]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.254
2 24 ms 25 ms 25 ms 4.1.233.220.exetel.com.au [220.233.1.4]
3 25 ms 24 ms 25 ms 61.1.96.58.exetel.com.au [58.96.1.61]
4 26 ms 26 ms 25 ms 1.4.96.58.exetel.com.au [58.96.4.1]
5 27 ms 26 ms 27 ms 241.0.233.220.exetel.com.au [220.233.0.241]
6 26 ms 26 ms 26 ms 10.0.1.1
7 * 28 ms 27 ms 38.2.233.220.exetel.com.au [220.233.2.38]

8 26 ms 26 ms 26 ms 359-ge-0-0-0.GW5.SYD2.ALTER.NET [203.166.92.57]
9 27 ms 26 ms 26 ms 0.so-0-2-0.XT1.SYD2.ALTER.NET [210.80.33.189]
10 182 ms 181 ms 181 ms 0.so-1-3-0.IR1.LAX12.Alter.Net [210.80.48.125]
11 183 ms 181 ms 180 ms 0.so-5-0-0.IL1.LAX9.ALTER.NET [152.63.48.65]
12 189 ms 190 ms 189 ms 0.so-3-0-0.XL1.SJC7.ALTER.NET [152.63.0.150]
13 191 ms 189 ms 190 ms POS6-0-0.GW4.SJC7.ALTER.NET [152.63.48.241]
14 191 ms 190 ms 194 ms teliasonera-test-gw.customer.alter­ .net [157.130.215.70]
15 202 ms 202 ms 202 ms las-bb1-link.telia.net [213.248.80.17]
16 237 ms 236 ms 236 ms dls-bb1-link.telia.net [213.248.80.14]
17 250 ms 239 ms 239 ms rackspace-114734-dls-bb1.c.telia.n­ et [213.248.92.30]
18 231 ms 232 ms 231 ms vlan903.core3.dfw1.rackspace.com [72.3.128.53]
19 233 ms 232 ms 232 ms aggr107a.dfw1.rackspace.net [72.3.129.77]
20 231 ms 231 ms 231 ms vimeo.com [72.3.218.217]

Trace complete.

And our local Midnight Rider reports continued successful streaming HD via his 8192/384 kbps plan, at least on occasions he has tried.

Saturday:
forum-replies.cfm?t=905830&p=3&u=71962#r58
Sunday:
forum-replies.cfm?t=910431&p=2#r30

But not all is well in Exetel land -

C:\>ping -n 10 microsoft.com >ping.txt

Pinging microsoft.com [207.46.197.32] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 207.46.197.32:
Packets: Sent = 10, Received = 0, Lost = 10 (100% loss), 0:
WTH ???

Exetel/PowerTel:

--- vimeo.com ping statistics ---
102 packets transmitted, 100 packets received, 1% packet loss
round-trip min/avg/max/stddev = 227.456/229.185/233.830/1.244 ms

aaNet:

--- vimeo.com ping statistics ---
102 packets transmitted, 102 packets received, 0% packet loss
round-trip min/avg/max/stddev = 214.576/219.593/240.387/4.438 ms

Aarnet:

----vimeo.com PING Statistics----
102 packets transmitted, 96 packets received, 5% packet loss
round-trip (ms) min/avg/max/stddev = 204./227.9/749.9/91.0

Possibly some packet loss - need more data points though.

hibernator writes...

But not all is well in Exetel land -
100% loss), 0:
WTH ???

I get the same 100% loss [for microsoft.com] from all of Exetel, aaNet and Aarnet, so I don't think that's significant. Probably router load and/or icmp limiting is causing the icmp packets to be simply dropped.

Here's mine

Exetel/Telstra

C:\>ping -n 30 vimeo.com >ping.txt

Pinging vimeo.com [72.3.218.217] with 32 bytes of data:

Ping statistics for 72.3.218.217:
Packets: Sent = 30, Received = 24, Lost = 6 (20% loss),
Approximate round trip times in milli-seconds:
Minimum = 229ms, Maximum = 232ms, Average = 230ms

...Well, more impressive than Microsoft.com ;-)

LOL lucky I don't have these connection problems as bad as you.

Pinging vimeo.com [72.3.218.217] with 32 bytes of data:

Ping statistics for 72.3.218.217:

Packets: Sent = 30, Received = 28, Lost = 2 (6% loss),

Approximate round trip times in milli-seconds:

Minimum = 227ms, Maximum = 231ms, Average = 229ms

My net is dying in the butthole too.

Ping statistics for 72.3.218.217:
Packets: Sent = 30, Received = 17, Lost = 13 (43% loss)
Approximate round trip times in milli-seconds:
Minimum = 220ms, Maximum = 222ms, Average = 221ms

chunderman honestly.

your 1.5 mbps connection and fine incurred for December07 suggests you are more bent on leeching p2p/overnight (via you budget plan) than streaming HD video from a creative/social site.

The reality is I am able to reproduce ~ 20% packet loss to the vimeo.com site. Can't speak for others though..

It would be so nice to just be able to enjoy video a little above the standard of U-Tube through a different site. If the site can't serve at least 210 KB/s to overseas then you know something's not right. But what?

having issues too...there ar actually a few of us in Wow having MAJOR problems.

forums.worldofwarcraft.c...4311217434&sid=1

Hrmm might have to think about chruning to Internode or TPG, a lot more reliable from what I hear.

I am just happy i can see this page...

fun times, hope its gets fixed whoever the problem belongs to :(

Mattyp writes...

Hrmm might have to think about chruning to Internode or TPG, a lot more reliable from what I hear.

Did you not read the Internode results Hibernator posted earlier in this thread? The aaNet and Aarnet results I posted? This particular issue is not confined to Exetel.