ClearWire in ****e tonight?!

sisyphus · 11-11-2005 10:58pm #1

Anybody else getting laudible response times tonight using ClearWire? I'm off FitzWilliam Square mast....
Any ideas what's up?

Pinging 83.134.128.1 with 32 bytes of data:

Reply from 83.134.128.1: bytes=32 time=198ms TTL=54
Reply from 83.134.128.1: bytes=32 time=219ms TTL=54
Reply from 83.134.128.1: bytes=32 time=189ms TTL=54
Reply from 83.134.128.1: bytes=32 time=138ms TTL=54
Reply from 83.134.128.1: bytes=32 time=124ms TTL=54
Reply from 83.134.128.1: bytes=32 time=177ms TTL=54
Reply from 83.134.128.1: bytes=32 time=197ms TTL=54
Reply from 83.134.128.1: bytes=32 time=158ms TTL=54
Reply from 83.134.128.1: bytes=32 time=269ms TTL=54
Reply from 83.134.128.1: bytes=32 time=138ms TTL=54
Reply from 83.134.128.1: bytes=32 time=224ms TTL=54
Reply from 83.134.128.1: bytes=32 time=185ms TTL=54
Reply from 83.134.128.1: bytes=32 time=222ms TTL=54
Reply from 83.134.128.1: bytes=32 time=208ms TTL=54
Reply from 83.134.128.1: bytes=32 time=260ms TTL=54
Reply from 83.134.128.1: bytes=32 time=213ms TTL=54
Reply from 83.134.128.1: bytes=32 time=199ms TTL=54
Reply from 83.134.128.1: bytes=32 time=269ms TTL=54
Reply from 83.134.128.1: bytes=32 time=273ms TTL=54
Reply from 83.134.128.1: bytes=32 time=293ms TTL=54
Reply from 83.134.128.1: bytes=32 time=396ms TTL=54
Reply from 83.134.128.1: bytes=32 time=440ms TTL=54
Reply from 83.134.128.1: bytes=32 time=426ms TTL=54
Reply from 83.134.128.1: bytes=32 time=479ms TTL=54
Reply from 83.134.128.1: bytes=32 time=449ms TTL=54
Reply from 83.134.128.1: bytes=32 time=468ms TTL=54
Reply from 83.134.128.1: bytes=32 time=320ms TTL=54
Reply from 83.134.128.1: bytes=32 time=373ms TTL=54
Reply from 83.134.128.1: bytes=32 time=426ms TTL=54
Reply from 83.134.128.1: bytes=32 time=487ms TTL=54
Reply from 83.134.128.1: bytes=32 time=381ms TTL=54
Reply from 83.134.128.1: bytes=32 time=409ms TTL=54
Reply from 83.134.128.1: bytes=32 time=428ms TTL=54
Reply from 83.134.128.1: bytes=32 time=456ms TTL=54
Reply from 83.134.128.1: bytes=32 time=359ms TTL=54
Reply from 83.134.128.1: bytes=32 time=345ms TTL=54
Reply from 83.134.128.1: bytes=32 time=356ms TTL=54
Reply from 83.134.128.1: bytes=32 time=425ms TTL=54
Reply from 83.134.128.1: bytes=32 time=411ms TTL=54
Reply from 83.134.128.1: bytes=32 time=389ms TTL=54

Ping statistics for 83.134.128.1:
    Packets: Sent = 40, Received = 40, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 124ms, Maximum = 487ms, Average = 309ms


ping ftp.heanet.ie &#8211;n 50

Pinging ftp.heanet.ie [193.1.193.64] with 32 bytes of data:

Reply from 193.1.193.64: bytes=32 time=440ms TTL=59
Reply from 193.1.193.64: bytes=32 time=355ms TTL=59
Reply from 193.1.193.64: bytes=32 time=282ms TTL=59
Reply from 193.1.193.64: bytes=32 time=210ms TTL=59
Reply from 193.1.193.64: bytes=32 time=313ms TTL=59
Reply from 193.1.193.64: bytes=32 time=307ms TTL=59
Reply from 193.1.193.64: bytes=32 time=193ms TTL=59
Reply from 193.1.193.64: bytes=32 time=329ms TTL=59
Reply from 193.1.193.64: bytes=32 time=272ms TTL=59
Reply from 193.1.193.64: bytes=32 time=275ms TTL=59
Reply from 193.1.193.64: bytes=32 time=269ms TTL=59
Reply from 193.1.193.64: bytes=32 time=306ms TTL=59
Reply from 193.1.193.64: bytes=32 time=117ms TTL=59
Reply from 193.1.193.64: bytes=32 time=321ms TTL=59
Reply from 193.1.193.64: bytes=32 time=256ms TTL=59
Reply from 193.1.193.64: bytes=32 time=176ms TTL=59
Reply from 193.1.193.64: bytes=32 time=354ms TTL=59
Reply from 193.1.193.64: bytes=32 time=289ms TTL=59
Reply from 193.1.193.64: bytes=32 time=317ms TTL=59
Reply from 193.1.193.64: bytes=32 time=303ms TTL=59
Reply from 193.1.193.64: bytes=32 time=348ms TTL=59
Reply from 193.1.193.64: bytes=32 time=326ms TTL=59
Reply from 193.1.193.64: bytes=32 time=228ms TTL=59
Reply from 193.1.193.64: bytes=32 time=218ms TTL=59
Reply from 193.1.193.64: bytes=32 time=215ms TTL=59
Request timed out.
Reply from 193.1.193.64: bytes=32 time=304ms TTL=59
Reply from 193.1.193.64: bytes=32 time=340ms TTL=59
Reply from 193.1.193.64: bytes=32 time=84ms TTL=59
Reply from 193.1.193.64: bytes=32 time=333ms TTL=59
Reply from 193.1.193.64: bytes=32 time=363ms TTL=59
Reply from 193.1.193.64: bytes=32 time=317ms TTL=59
Reply from 193.1.193.64: bytes=32 time=255ms TTL=59
Reply from 193.1.193.64: bytes=32 time=216ms TTL=59
Reply from 193.1.193.64: bytes=32 time=236ms TTL=59
Reply from 193.1.193.64: bytes=32 time=335ms TTL=59
Reply from 193.1.193.64: bytes=32 time=237ms TTL=59
Reply from 193.1.193.64: bytes=32 time=257ms TTL=59
Reply from 193.1.193.64: bytes=32 time=218ms TTL=59
Reply from 193.1.193.64: bytes=32 time=119ms TTL=59
Reply from 193.1.193.64: bytes=32 time=56ms TTL=59
Reply from 193.1.193.64: bytes=32 time=101ms TTL=59
Reply from 193.1.193.64: bytes=32 time=141ms TTL=59
Reply from 193.1.193.64: bytes=32 time=211ms TTL=59
Reply from 193.1.193.64: bytes=32 time=188ms TTL=59
Reply from 193.1.193.64: bytes=32 time=174ms TTL=59
Reply from 193.1.193.64: bytes=32 time=185ms TTL=59
Reply from 193.1.193.64: bytes=32 time=221ms TTL=59
Reply from 193.1.193.64: bytes=32 time=258ms TTL=59
Reply from 193.1.193.64: bytes=32 time=216ms TTL=59

Ping statistics for 193.1.193.64:
    Packets: Sent = 50, Received = 49, Lost = 1 (2% loss),
Approximate round trip times in milli-seconds:
    Minimum = 56ms, Maximum = 440ms, Average = 252ms

Tracing route to ftp.heanet.ie [193.1.193.64]
over a maximum of 30 hops:

  1   239 ms    74 ms    58 ms  85.134.128.3
  2   161 ms    91 ms   159 ms  fe-0-0-0_0.bdr002.dublin.clearwire.ie [85.134.25
5.12]
  3   161 ms   242 ms   192 ms  hyperion-gige6-1.cwt.core.hea.net [193.242.111.1
6]
  4   186 ms   217 ms   208 ms  193.1.195.136
  5   220 ms   301 ms   317 ms  portia-po1.bh.access.hea.net [193.1.196.218]
  6   328 ms   334 ms   342 ms  ftp.heanet.ie [193.1.193.64]

Trace complete.

Tracing route to www.l.google.com [64.233.183.104]
over a maximum of 30 hops:

  1   398 ms   409 ms   384 ms  85.134.128.3
  2   311 ms   317 ms   351 ms  fe-0-0-0_0.bdr001.dublin.clearwire.ie [85.134.25
5.13]
  3   320 ms   359 ms   309 ms  ge-5-0-0.403.ar1.dub1.gblx.net [67.17.211.53]
  4   329 ms   434 ms   334 ms  so0-0-0-2488M.ar3.LON2.gblx.net [67.17.71.25]
  5   310 ms   334 ms   334 ms  ldn-b1-pos2-0.telia.net [213.248.100.1]
  6   421 ms   434 ms   351 ms  google-104716-ldn-b1.c.telia.net [213.248.74.194
]
  7   412 ms   418 ms   510 ms  72.14.238.246
  8   412 ms   427 ms   451 ms  216.239.43.91
  9   479 ms   535 ms   452 ms  216.239.48.146
 10   463 ms   435 ms   426 ms  216.239.43.30
 11   437 ms   342 ms   309 ms  216.239.43.34
 12   333 ms   342 ms   334 ms  216.239.43.84
 13   337 ms   409 ms   309 ms  64.233.183.104

Trace complete.

sisyphus · 11-11-2005 11:13pm

Oh, slight improvement!! Still though, what the hell is going on here?!!

ping 83.134.128.1 -n 50

Pinging 83.134.128.1 with 32 bytes of data:

Reply from 83.134.128.1: bytes=32 time=137ms TTL=54
Reply from 83.134.128.1: bytes=32 time=174ms TTL=54
Reply from 83.134.128.1: bytes=32 time=202ms TTL=54
Reply from 83.134.128.1: bytes=32 time=179ms TTL=54
Reply from 83.134.128.1: bytes=32 time=48ms TTL=54
Reply from 83.134.128.1: bytes=32 time=94ms TTL=54
Reply from 83.134.128.1: bytes=32 time=159ms TTL=54
Reply from 83.134.128.1: bytes=32 time=62ms TTL=54
Reply from 83.134.128.1: bytes=32 time=77ms TTL=54
Reply from 83.134.128.1: bytes=32 time=135ms TTL=54
Reply from 83.134.128.1: bytes=32 time=150ms TTL=54
Reply from 83.134.128.1: bytes=32 time=61ms TTL=54
Reply from 83.134.128.1: bytes=32 time=144ms TTL=54
Reply from 83.134.128.1: bytes=32 time=68ms TTL=54
Reply from 83.134.128.1: bytes=32 time=193ms TTL=54
Reply from 83.134.128.1: bytes=32 time=67ms TTL=54
Reply from 83.134.128.1: bytes=32 time=65ms TTL=54
Reply from 83.134.128.1: bytes=32 time=88ms TTL=54
Reply from 83.134.128.1: bytes=32 time=74ms TTL=54
Reply from 83.134.128.1: bytes=32 time=68ms TTL=54
Reply from 83.134.128.1: bytes=32 time=92ms TTL=54
Reply from 83.134.128.1: bytes=32 time=65ms TTL=54
Reply from 83.134.128.1: bytes=32 time=135ms TTL=54
Reply from 83.134.128.1: bytes=32 time=129ms TTL=54
Reply from 83.134.128.1: bytes=32 time=183ms TTL=54
Reply from 83.134.128.1: bytes=32 time=52ms TTL=54
Reply from 83.134.128.1: bytes=32 time=72ms TTL=54
Reply from 83.134.128.1: bytes=32 time=62ms TTL=54
Reply from 83.134.128.1: bytes=32 time=70ms TTL=54
Reply from 83.134.128.1: bytes=32 time=106ms TTL=54
Reply from 83.134.128.1: bytes=32 time=142ms TTL=54
Reply from 83.134.128.1: bytes=32 time=145ms TTL=54
Reply from 83.134.128.1: bytes=32 time=56ms TTL=54
Reply from 83.134.128.1: bytes=32 time=46ms TTL=54
Reply from 83.134.128.1: bytes=32 time=66ms TTL=54
Reply from 83.134.128.1: bytes=32 time=106ms TTL=54
Reply from 83.134.128.1: bytes=32 time=84ms TTL=54
Reply from 83.134.128.1: bytes=32 time=66ms TTL=54
Reply from 83.134.128.1: bytes=32 time=52ms TTL=54
Reply from 83.134.128.1: bytes=32 time=68ms TTL=54
Reply from 83.134.128.1: bytes=32 time=49ms TTL=54
Reply from 83.134.128.1: bytes=32 time=70ms TTL=54
Reply from 83.134.128.1: bytes=32 time=68ms TTL=54
Reply from 83.134.128.1: bytes=32 time=53ms TTL=54
Reply from 83.134.128.1: bytes=32 time=77ms TTL=54
Reply from 83.134.128.1: bytes=32 time=51ms TTL=54
Reply from 83.134.128.1: bytes=32 time=46ms TTL=54
Reply from 83.134.128.1: bytes=32 time=66ms TTL=54
Reply from 83.134.128.1: bytes=32 time=48ms TTL=54
Reply from 83.134.128.1: bytes=32 time=47ms TTL=54

Ping statistics for 83.134.128.1:
    Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 46ms, Maximum = 202ms, Average = 92ms

sisyphus · 11-11-2005 11:19pm

Oh, another slight improvement (23:20):

Pinging 83.134.128.1 with 32 bytes of data:

Reply from 83.134.128.1: bytes=32 time=49ms TTL=54
Reply from 83.134.128.1: bytes=32 time=53ms TTL=54
Reply from 83.134.128.1: bytes=32 time=57ms TTL=54
Reply from 83.134.128.1: bytes=32 time=52ms TTL=54
Reply from 83.134.128.1: bytes=32 time=51ms TTL=54
Reply from 83.134.128.1: bytes=32 time=75ms TTL=54
Reply from 83.134.128.1: bytes=32 time=61ms TTL=54
Reply from 83.134.128.1: bytes=32 time=47ms TTL=54
Reply from 83.134.128.1: bytes=32 time=47ms TTL=54
Reply from 83.134.128.1: bytes=32 time=50ms TTL=54
Reply from 83.134.128.1: bytes=32 time=66ms TTL=54
Reply from 83.134.128.1: bytes=32 time=52ms TTL=54
Reply from 83.134.128.1: bytes=32 time=60ms TTL=54
Reply from 83.134.128.1: bytes=32 time=54ms TTL=54
Reply from 83.134.128.1: bytes=32 time=54ms TTL=54
Reply from 83.134.128.1: bytes=32 time=49ms TTL=54
Reply from 83.134.128.1: bytes=32 time=52ms TTL=54
Reply from 83.134.128.1: bytes=32 time=51ms TTL=54
Reply from 83.134.128.1: bytes=32 time=67ms TTL=54
Reply from 83.134.128.1: bytes=32 time=78ms TTL=54
Reply from 83.134.128.1: bytes=32 time=51ms TTL=54
Reply from 83.134.128.1: bytes=32 time=50ms TTL=54
Reply from 83.134.128.1: bytes=32 time=74ms TTL=54
Reply from 83.134.128.1: bytes=32 time=53ms TTL=54
Reply from 83.134.128.1: bytes=32 time=57ms TTL=54
Reply from 83.134.128.1: bytes=32 time=69ms TTL=54
Reply from 83.134.128.1: bytes=32 time=72ms TTL=54
Reply from 83.134.128.1: bytes=32 time=54ms TTL=54
Reply from 83.134.128.1: bytes=32 time=75ms TTL=54
Reply from 83.134.128.1: bytes=32 time=48ms TTL=54
Reply from 83.134.128.1: bytes=32 time=47ms TTL=54
Reply from 83.134.128.1: bytes=32 time=74ms TTL=54
Reply from 83.134.128.1: bytes=32 time=47ms TTL=54
Reply from 83.134.128.1: bytes=32 time=50ms TTL=54
Reply from 83.134.128.1: bytes=32 time=74ms TTL=54
Reply from 83.134.128.1: bytes=32 time=48ms TTL=54
Reply from 83.134.128.1: bytes=32 time=51ms TTL=54

Ping statistics for 83.134.128.1:
    Packets: Sent = 37, Received = 37, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 47ms, Maximum = 78ms, Average = 57ms

MickH503 · 12-11-2005 12:15am

I didn't notice any problems earlier - I'm in Maynooth

Pinging 83.134.128.1 with 32 bytes of data:

Reply from 83.134.128.1: bytes=32 time=46ms TTL=54
Reply from 83.134.128.1: bytes=32 time=45ms TTL=54
Reply from 83.134.128.1: bytes=32 time=56ms TTL=54
Reply from 83.134.128.1: bytes=32 time=38ms TTL=54
Reply from 83.134.128.1: bytes=32 time=41ms TTL=54
Reply from 83.134.128.1: bytes=32 time=65ms TTL=54
Reply from 83.134.128.1: bytes=32 time=147ms TTL=54
Reply from 83.134.128.1: bytes=32 time=49ms TTL=54
Reply from 83.134.128.1: bytes=32 time=52ms TTL=54
Reply from 83.134.128.1: bytes=32 time=66ms TTL=54
Reply from 83.134.128.1: bytes=32 time=43ms TTL=54
Reply from 83.134.128.1: bytes=32 time=42ms TTL=54
Reply from 83.134.128.1: bytes=32 time=166ms TTL=54
Reply from 83.134.128.1: bytes=32 time=63ms TTL=54
Reply from 83.134.128.1: bytes=32 time=44ms TTL=54
Reply from 83.134.128.1: bytes=32 time=39ms TTL=54
Reply from 83.134.128.1: bytes=32 time=42ms TTL=54
Reply from 83.134.128.1: bytes=32 time=49ms TTL=54
Reply from 83.134.128.1: bytes=32 time=40ms TTL=54
Reply from 83.134.128.1: bytes=32 time=47ms TTL=54
Reply from 83.134.128.1: bytes=32 time=68ms TTL=54
Reply from 83.134.128.1: bytes=32 time=49ms TTL=54
Reply from 83.134.128.1: bytes=32 time=48ms TTL=54
Reply from 83.134.128.1: bytes=32 time=47ms TTL=54
Reply from 83.134.128.1: bytes=32 time=50ms TTL=54
Reply from 83.134.128.1: bytes=32 time=86ms TTL=54
Reply from 83.134.128.1: bytes=32 time=42ms TTL=54
Reply from 83.134.128.1: bytes=32 time=45ms TTL=54
Reply from 83.134.128.1: bytes=32 time=52ms TTL=54
Reply from 83.134.128.1: bytes=32 time=51ms TTL=54
Reply from 83.134.128.1: bytes=32 time=46ms TTL=54
Reply from 83.134.128.1: bytes=32 time=74ms TTL=54
Reply from 83.134.128.1: bytes=32 time=54ms TTL=54
Reply from 83.134.128.1: bytes=32 time=53ms TTL=54
Reply from 83.134.128.1: bytes=32 time=47ms TTL=54
Reply from 83.134.128.1: bytes=32 time=92ms TTL=54
Reply from 83.134.128.1: bytes=32 time=56ms TTL=54
Reply from 83.134.128.1: bytes=32 time=67ms TTL=54
Reply from 83.134.128.1: bytes=32 time=43ms TTL=54
Reply from 83.134.128.1: bytes=32 time=58ms TTL=54
Reply from 83.134.128.1: bytes=32 time=49ms TTL=54

Ping statistics for 83.134.128.1:
Packets: Sent = 41, Received = 41, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 38ms, Maximum = 166ms, Average = 57ms

oscarBravo · 12-11-2005 1:40am

sisyphus wrote:

... laudible response times...

I don't think that word means what you think it means...

sisyphus · 12-11-2005 2:58am

I don't think that word means what you think it means...

True enough. Well spotted, thought it meant laughable, but I've since learned otherwise. My bad....

eth0_ · 13-11-2005 4:08pm

sisyphus, I don't live too far from you, we're possibly on the same transmitter.
I emailed clearwire on thursday and they said they're investigating but i've heard nothing more from them

eth0_ · 14-11-2005 5:27pm

Just sent this to support after they emailed me earlier for my modem s/n. It's quite clear the problem is not with my modem.

As you can see below, pings and traceroutes to hosts in Ireland, the UK and the USA, there's massive packet loss - even to www.clearwire.ie!

Last login: Mon Nov 14 16:44:41 on console
Welcome to Darwin!

ping www.heanet.ie
PING heanet.webhost.heanet.ie (193.1.219.79): 56 data bytes
64 bytes from 193.1.219.79: icmp_seq=0 ttl=58 time=204.415 ms
64 bytes from 193.1.219.79: icmp_seq=1 ttl=58 time=461.035 ms
64 bytes from 193.1.219.79: icmp_seq=2 ttl=58 time=306.242 ms
64 bytes from 193.1.219.79: icmp_seq=3 ttl=58 time=199.128 ms
64 bytes from 193.1.219.79: icmp_seq=4 ttl=58 time=199.242 ms
64 bytes from 193.1.219.79: icmp_seq=5 ttl=58 time=382.937 ms
64 bytes from 193.1.219.79: icmp_seq=7 ttl=58 time=47.972 ms
64 bytes from 193.1.219.79: icmp_seq=8 ttl=58 time=51.732 ms
64 bytes from 193.1.219.79: icmp_seq=9 ttl=58 time=85.038 ms
64 bytes from 193.1.219.79: icmp_seq=10 ttl=58 time=197.995 ms
64 bytes from 193.1.219.79: icmp_seq=11 ttl=58 time=84.546 ms
64 bytes from 193.1.219.79: icmp_seq=12 ttl=58 time=51.071 ms
64 bytes from 193.1.219.79: icmp_seq=13 ttl=58 time=96.686 ms
64 bytes from 193.1.219.79: icmp_seq=14 ttl=58 time=163.661 ms
64 bytes from 193.1.219.79: icmp_seq=16 ttl=58 time=92.175 ms
64 bytes from 193.1.219.79: icmp_seq=17 ttl=58 time=112.500 ms
64 bytes from 193.1.219.79: icmp_seq=18 ttl=58 time=104.527 ms
64 bytes from 193.1.219.79: icmp_seq=20 ttl=58 time=33.683 ms
64 bytes from 193.1.219.79: icmp_seq=21 ttl=58 time=117.127 ms
64 bytes from 193.1.219.79: icmp_seq=22 ttl=58 time=137.702 ms
^C
--- heanet.webhost.heanet.ie ping statistics ---
23 packets transmitted, 20 packets received, 13% packet loss
round-trip min/avg/max/stddev = 33.683/156.471/461.035/111.276 ms

traceroute www.heanet.ie
traceroute to heanet.webhost.heanet.ie (193.1.219.79), 64 hops max, 40 byte packets
1 192.168.2.1 (192.168.2.1) 2.505 ms 1.334 ms 1.275 ms
2 85.134.128.3 (85.134.128.3) 107.176 ms 108.429 ms *
3 * fe-0-0-0_0.bdr002.dublin.clearwire.ie (85.134.255.12) 256.139 ms 39.057 ms
4 hyperion-gige6-1.cwt.core.hea.net (193.242.111.16) 94.730 ms 156.332 ms *
5 * 193.1.195.136 (193.1.195.136) 84.240 ms 46.805 ms
6 portia-po1.bh.access.hea.net (193.1.196.218) 44.835 ms * 130.908 ms
7 www.heanet.ie (193.1.219.79) 61.054 ms 85.534 ms 49.352 ms

ping www.bbc.co.uk
PING www.bbc.net.uk (212.58.224.87): 56 data bytes
64 bytes from 212.58.224.87: icmp_seq=1 ttl=248 time=110.335 ms
64 bytes from 212.58.224.87: icmp_seq=2 ttl=248 time=164.672 ms
64 bytes from 212.58.224.87: icmp_seq=3 ttl=248 time=176.769 ms
64 bytes from 212.58.224.87: icmp_seq=4 ttl=248 time=117.856 ms
64 bytes from 212.58.224.87: icmp_seq=7 ttl=248 time=66.699 ms
64 bytes from 212.58.224.87: icmp_seq=9 ttl=248 time=145.646 ms
64 bytes from 212.58.224.87: icmp_seq=10 ttl=248 time=225.832 ms
64 bytes from 212.58.224.87: icmp_seq=12 ttl=248 time=115.273 ms
64 bytes from 212.58.224.87: icmp_seq=13 ttl=248 time=60.681 ms
64 bytes from 212.58.224.87: icmp_seq=18 ttl=248 time=172.707 ms
64 bytes from 212.58.224.87: icmp_seq=19 ttl=248 time=204.842 ms
64 bytes from 212.58.224.87: icmp_seq=20 ttl=248 time=76.308 ms
64 bytes from 212.58.224.87: icmp_seq=21 ttl=248 time=98.676 ms
64 bytes from 212.58.224.87: icmp_seq=22 ttl=248 time=87.297 ms
64 bytes from 212.58.224.87: icmp_seq=23 ttl=248 time=237.357 ms
64 bytes from 212.58.224.87: icmp_seq=24 ttl=248 time=295.575 ms
64 bytes from 212.58.224.87: icmp_seq=25 ttl=248 time=307.231 ms
64 bytes from 212.58.224.87: icmp_seq=26 ttl=248 time=286.427 ms
64 bytes from 212.58.224.87: icmp_seq=27 ttl=248 time=356.925 ms
64 bytes from 212.58.224.87: icmp_seq=28 ttl=248 time=406.660 ms
^C
--- www.bbc.net.uk ping statistics ---
29 packets transmitted, 20 packets received, 31% packet loss
round-trip min/avg/max/stddev = 60.681/185.688/406.660/99.077 ms

traceroute www.bbc.co.uk
traceroute to www.bbc.net.uk (212.58.224.87), 64 hops max, 40 byte packets
1 192.168.2.1 (192.168.2.1) 10.842 ms 1.444 ms 1.306 ms
2 85.134.128.3 (85.134.128.3) 176.322 ms * 403.108 ms
3 fe-0-0-0_0.bdr001.dublin.clearwire.ie (85.134.255.13) 282.926 ms 342.000 ms 404.396 ms
4 ge-5-0-0.403.ar1.dub1.gblx.net (67.17.211.53) 328.712 ms 485.008 ms 608.366 ms
5 * 67.17.71.25 (67.17.71.25) 94.214 ms 79.532 ms
6 bbc-gw0-linx.prt0.thdoe.bbc.co.uk (195.66.224.103) 100.870 ms 169.382 ms *
7 212.58.238.129 (212.58.238.129) 154.819 ms 257.361 ms 93.581 ms
8 www50.thdo.bbc.co.uk (212.58.224.87) 132.228 ms 71.758 ms 85.044 ms

ping www.clearwire.ie
PING www.clearwire.ie (85.134.255.242): 56 data bytes
64 bytes from 85.134.255.242: icmp_seq=1 ttl=61 time=252.098 ms
64 bytes from 85.134.255.242: icmp_seq=2 ttl=61 time=207.046 ms
64 bytes from 85.134.255.242: icmp_seq=3 ttl=61 time=412.309 ms
64 bytes from 85.134.255.242: icmp_seq=4 ttl=61 time=224.176 ms
64 bytes from 85.134.255.242: icmp_seq=5 ttl=61 time=587.110 ms
64 bytes from 85.134.255.242: icmp_seq=6 ttl=61 time=473.879 ms
64 bytes from 85.134.255.242: icmp_seq=7 ttl=61 time=210.292 ms
64 bytes from 85.134.255.242: icmp_seq=8 ttl=61 time=339.218 ms
64 bytes from 85.134.255.242: icmp_seq=10 ttl=61 time=72.523 ms
64 bytes from 85.134.255.242: icmp_seq=12 ttl=61 time=86.189 ms
64 bytes from 85.134.255.242: icmp_seq=13 ttl=61 time=160.866 ms
64 bytes from 85.134.255.242: icmp_seq=14 ttl=61 time=261.246 ms
64 bytes from 85.134.255.242: icmp_seq=15 ttl=61 time=185.832 ms
64 bytes from 85.134.255.242: icmp_seq=16 ttl=61 time=146.400 ms
64 bytes from 85.134.255.242: icmp_seq=17 ttl=61 time=200.156 ms
64 bytes from 85.134.255.242: icmp_seq=18 ttl=61 time=189.762 ms
64 bytes from 85.134.255.242: icmp_seq=19 ttl=61 time=84.800 ms
64 bytes from 85.134.255.242: icmp_seq=20 ttl=61 time=143.020 ms
64 bytes from 85.134.255.242: icmp_seq=21 ttl=61 time=75.922 ms
64 bytes from 85.134.255.242: icmp_seq=22 ttl=61 time=282.473 ms
64 bytes from 85.134.255.242: icmp_seq=25 ttl=61 time=65.706 ms
64 bytes from 85.134.255.242: icmp_seq=26 ttl=61 time=161.673 ms
64 bytes from 85.134.255.242: icmp_seq=27 ttl=61 time=105.331 ms
64 bytes from 85.134.255.242: icmp_seq=29 ttl=61 time=117.079 ms
64 bytes from 85.134.255.242: icmp_seq=30 ttl=61 time=158.653 ms
64 bytes from 85.134.255.242: icmp_seq=31 ttl=61 time=187.603 ms
64 bytes from 85.134.255.242: icmp_seq=32 ttl=61 time=45.168 ms
64 bytes from 85.134.255.242: icmp_seq=34 ttl=61 time=82.447 ms
64 bytes from 85.134.255.242: icmp_seq=35 ttl=61 time=119.828 ms
64 bytes from 85.134.255.242: icmp_seq=36 ttl=61 time=182.525 ms
64 bytes from 85.134.255.242: icmp_seq=39 ttl=61 time=175.434 ms
64 bytes from 85.134.255.242: icmp_seq=40 ttl=61 time=212.935 ms
^C
--- www.clearwire.ie ping statistics ---
41 packets transmitted, 32 packets received, 21% packet loss
round-trip min/avg/max/stddev = 45.168/194.053/587.110/118.654 ms

traceroute www.clearwire.ie
traceroute to www.clearwire.ie (85.134.255.242), 64 hops max, 40 byte packets
1 192.168.2.1 (192.168.2.1) 10.858 ms 1.407 ms 1.361 ms
2 85.134.128.3 (85.134.128.3) 58.594 ms 170.299 ms 266.909 ms
3 85.134.255.37 (85.134.255.37) 261.777 ms 150.152 ms 416.272 ms
4 cwi001.clearwire.ie (85.134.255.242) 124.504 ms 616.843 ms 144.785 ms

eth0_ · 14-11-2005 5:35pm

ping www.cnet.com
PING c10-ssa-xw-lb.cnet.com (216.239.115.173): 56 data bytes
64 bytes from 216.239.115.173: icmp_seq=1 ttl=243 time=352.583 ms
64 bytes from 216.239.115.173: icmp_seq=2 ttl=243 time=242.911 ms
64 bytes from 216.239.115.173: icmp_seq=3 ttl=243 time=371.162 ms
64 bytes from 216.239.115.173: icmp_seq=4 ttl=243 time=219.942 ms
64 bytes from 216.239.115.173: icmp_seq=5 ttl=243 time=307.391 ms
64 bytes from 216.239.115.173: icmp_seq=6 ttl=243 time=214.973 ms
64 bytes from 216.239.115.173: icmp_seq=7 ttl=243 time=198.499 ms
64 bytes from 216.239.115.173: icmp_seq=8 ttl=243 time=310.976 ms
64 bytes from 216.239.115.173: icmp_seq=9 ttl=243 time=210.106 ms
64 bytes from 216.239.115.173: icmp_seq=10 ttl=243 time=222.114 ms
64 bytes from 216.239.115.173: icmp_seq=11 ttl=243 time=226.076 ms
64 bytes from 216.239.115.173: icmp_seq=12 ttl=243 time=223.977 ms
64 bytes from 216.239.115.173: icmp_seq=14 ttl=243 time=223.672 ms
64 bytes from 216.239.115.173: icmp_seq=15 ttl=243 time=265.233 ms
64 bytes from 216.239.115.173: icmp_seq=16 ttl=243 time=257.987 ms
64 bytes from 216.239.115.173: icmp_seq=19 ttl=243 time=214.149 ms
64 bytes from 216.239.115.173: icmp_seq=20 ttl=243 time=297.933 ms
^C
--- c10-ssa-xw-lb.cnet.com ping statistics ---
21 packets transmitted, 17 packets received, 19% packet loss
round-trip min/avg/max/stddev = 198.499/256.452/371.162/51.181 ms

traceroute www.cnet.com
traceroute to c10-ssa-xw-lb.cnet.com (216.239.115.173), 64 hops max, 40 byte packets
1 192.168.2.1 (192.168.2.1) 58.658 ms 1.351 ms 1.279 ms
2 85.134.128.3 (85.134.128.3) 104.832 ms 50.780 ms 242.013 ms
3 fe-0-0-0_0.bdr001.dublin.clearwire.ie (85.134.255.13) 116.347 ms 139.958 ms 94.103 ms
4 ge-5-0-0.403.ar1.dub1.gblx.net (67.17.211.53) 57.291 ms 126.305 ms *
5 so0-0-0-2488m.ar3.lon2.gblx.net (67.17.71.25) 87.184 ms 156.153 ms 119.035 ms
6 pos7-1.mpr2.lhr1.uk.above.net (208.185.188.65) 102.682 ms 55.451 ms 103.845 ms
7 so-4-1-0.cr2.lhr3.uk.above.net (208.185.156.2) 72.712 ms 64.078 ms 82.854 ms
8 * so-0-0-0.cr1.lhr3.uk.above.net (208.184.231.145) 93.234 ms 141.724 ms
9 so-7-0-0.cr1.dca2.us.above.net (64.125.31.186) 166.346 ms 186.185 ms 165.875 ms
10 so-6-1-0.cr2.ord2.us.above.net (64.125.27.13) 157.137 ms * 151.864 ms
11 * so-0-0-0.cr1.ord2.us.above.net (64.125.29.185) 194.525 ms 148.911 ms
12 so-4-0-0.mpr3.sjc2.us.above.net (64.125.30.213) 228.756 ms 236.213 ms 237.405 ms
13 so-4-0-0.mpr1.sfo3.us.above.net (64.125.31.122) 408.252 ms * *
14 64.124.44.37.available.above.net (64.124.44.37) 256.876 ms 298.291 ms 264.833 ms
15 * vlan700.365-sfo1-6506-1.cnet.com (216.239.127.41) 231.395 ms *
16 ge5-2.xch-sfo1-6506-1.cnet.com (216.239.127.22) 242.834 ms 382.303 ms 221.049 ms
17 vlan509.xch-sfo1-6506-2.cnet.com (216.239.127.30) 235.612 ms 228.910 ms *
18 ge5-2.att-sql1-6506-2.cnet.com (216.239.127.25) 236.483 ms * 200.953 ms
19 c10-ssa-xw-lb.cnet.com (216.239.115.173) 203.270 ms 256.437 ms 207.951 ms

DamoVOTF · 14-11-2005 8:04pm

I am seeing the same sort of results. I dont mind a slightly higher ping but it is also the packet also I am getting.

My signal has dropped while I was away at the weekend from 2/3 to 1/2. And getting lots of dropped packets. Got on to clearwire and they said they would get back to me?

PS anyone elses modem have trouble with double glazed windows?

Shougeki · 14-11-2005 8:35pm

I was playing WoW all weekend on it and must say i was pretty impressed.

However last night between 6ish and 9ish it dropped to laughable speeds. Same again when i came home today. Too afraid to log on to see what th latency is like.

I mailed clearwire today, and they said it shoulkd be resolved. However my speed is about 280 on irishisptest.

Ridiculous. When the line is up and working what are your speeds on irishisptest?

Im on Parliamnet St near the river. Have a constant 5 bars signal strength. The odd time itg drops to 4 - but about 80% 5.

I have this service since friday, and its good when not just after dinner. Clearwire havent taken anything from my bank acc yet, so i think i might just jack it in asap, but i dont want the hassel of a phone line.......

Blaster99 · 14-11-2005 9:52pm

Forget irishisptest, it's useless. Use something like adslguide.co.uk instead.

DamoVOTF · 15-11-2005 12:14pm

I am in Black Rock and generally get 2/1 bars of signal (but have to keep my window open or no service at all). Most of the time my WoW service is ok, around 180ms, which is decent enough to be playable but I get the occasional lag spike up to 2 seconds.

I phoned them twice last night and they said they would contact me back but no luck so far.

I really want this sorted as WiMax is my only available service.

Hoodle · 15-11-2005 3:19pm

Anybody got any idea where the nearest Clearwire mast to Clanbrassil St. Lower is? Thinking of signing up to the service.

Shougeki · 15-11-2005 8:47pm

Shocking connection again. Contacted support. Nice guy on the phone checked everything as usual blah blah blah.

Finally dealing with a tech who knew what he was doing and talking about.

Admitted couldnt be signal strength ect with the 4/5 bars, and could confirm from his end.

Apparently there is radio interference on the line, and they are going to do diags. They use irishisptest (which i was told is now crfap and relayed to the tech). He told me to use whatever and asked for the ones i use - adslguide and giganews.

Asked for me to mail if there is a drop or gain in the line during the night.

B

eth0_ · 15-11-2005 9:27pm

Me too.
There was intereference causing problems for me about a month ago.
As it's not really up to Clearwire to locate and stop the interference - it's Comreg's job - I don't hold out a lot of hope.

Shougeki · 15-11-2005 10:35pm

Was it resolved? My speed all night has kinda improved, but only to 300-400kbps on giganews........

Whats the process here? Do i wait for clearwire to solve this or just pul the plug?

My problem here is the connection was fine all weekend.....

eth0_ · 15-11-2005 10:41pm

No, it's still sh*gged.
I've sent them an email again.

JimmySmith · 15-11-2005 11:12pm

Shougeki wrote:

Was it resolved? My speed all night has kinda improved, but only to 300-400kbps on giganews........

Whats the process here? Do i wait for clearwire to solve this or just pul the plug?

My problem here is the connection was fine all weekend.....

It should be fine all of the time not at the weekend. It should also work at broadband speed not the measly speed you're getting. Dont accept less than what you paid for.
Thats the problem with ISPs. People pay for a 2meg connection and get 56k and then are delighted when it goes to 1meg speed even though this is less than what they are paying for.
Dont let any ISP prey on you

eth0_ · 16-11-2005 7:02am

As I expected, again at 7am my connection is pretty much perfect. Although why am I getting packet loss to clearwire.ie? It looks to me like this problem is occuring because they have too many customers on the one base station. I'm loathe to mention ripwave but...

ping www.boards.ie
PING www.boards.ie (82.195.136.250): 56 data bytes
64 bytes from 82.195.136.250: icmp_seq=0 ttl=59 time=72.152 ms
64 bytes from 82.195.136.250: icmp_seq=1 ttl=59 time=108.795 ms
64 bytes from 82.195.136.250: icmp_seq=2 ttl=59 time=35.321 ms
64 bytes from 82.195.136.250: icmp_seq=3 ttl=59 time=39.213 ms
64 bytes from 82.195.136.250: icmp_seq=4 ttl=59 time=34.838 ms
64 bytes from 82.195.136.250: icmp_seq=5 ttl=59 time=55.643 ms
64 bytes from 82.195.136.250: icmp_seq=6 ttl=59 time=61.039 ms
64 bytes from 82.195.136.250: icmp_seq=7 ttl=59 time=38.897 ms
64 bytes from 82.195.136.250: icmp_seq=8 ttl=59 time=42.359 ms
64 bytes from 82.195.136.250: icmp_seq=9 ttl=59 time=37.984 ms
64 bytes from 82.195.136.250: icmp_seq=10 ttl=59 time=67.083 ms
64 bytes from 82.195.136.250: icmp_seq=11 ttl=59 time=37.132 ms
64 bytes from 82.195.136.250: icmp_seq=12 ttl=59 time=49.545 ms
64 bytes from 82.195.136.250: icmp_seq=13 ttl=59 time=53.387 ms
^C
--- www.boards.ie ping statistics ---
14 packets transmitted, 14 packets received, 0% packet loss
round-trip min/avg/max/stddev = 34.838/52.385/108.795/19.600 ms

traceroute www.boards.ie
traceroute to www.boards.ie (82.195.136.250), 64 hops max, 40 byte packets
1 192.168.2.1 (192.168.2.1) 2.821 ms 1.376 ms 1.223 ms
2 85.134.128.3 (85.134.128.3) 65.471 ms 36.044 ms 32.764 ms
3 fe-0-0-0_0.bdr002.dublin.clearwire.ie (85.134.255.12) 32.058 ms 80.687 ms 66.046 ms
4 panama-inex.hosting365.ie (193.242.111.87) 66.910 ms 51.105 ms *
5 corerouter1.hosting365.ie (82.195.128.7) 60.369 ms 214.666 ms 161.018 ms
6 boards.ie (82.195.136.250) 46.514 ms 38.948 ms 41.051 ms

ping www.bbc.co.uk
PING www.bbc.net.uk (212.58.224.126): 56 data bytes
64 bytes from 212.58.224.126: icmp_seq=0 ttl=248 time=55.607 ms
64 bytes from 212.58.224.126: icmp_seq=1 ttl=248 time=49.172 ms
64 bytes from 212.58.224.126: icmp_seq=2 ttl=248 time=44.737 ms
64 bytes from 212.58.224.126: icmp_seq=3 ttl=248 time=57.020 ms
64 bytes from 212.58.224.126: icmp_seq=4 ttl=248 time=52.658 ms
64 bytes from 212.58.224.126: icmp_seq=5 ttl=248 time=48.239 ms
64 bytes from 212.58.224.126: icmp_seq=6 ttl=248 time=85.676 ms
64 bytes from 212.58.224.126: icmp_seq=7 ttl=248 time=47.788 ms
64 bytes from 212.58.224.126: icmp_seq=8 ttl=248 time=43.026 ms
64 bytes from 212.58.224.126: icmp_seq=9 ttl=248 time=66.863 ms
64 bytes from 212.58.224.126: icmp_seq=10 ttl=248 time=45.769 ms
64 bytes from 212.58.224.126: icmp_seq=11 ttl=248 time=47.609 ms
64 bytes from 212.58.224.126: icmp_seq=12 ttl=248 time=43.231 ms
64 bytes from 212.58.224.126: icmp_seq=13 ttl=248 time=41.210 ms
64 bytes from 212.58.224.126: icmp_seq=14 ttl=248 time=39.991 ms
^C
--- www.bbc.net.uk ping statistics ---
15 packets transmitted, 15 packets received, 0% packet loss
round-trip min/avg/max/stddev = 39.991/51.240/85.676/11.413 ms

traceroute www.bbc.co.uk
traceroute to www.bbc.net.uk (212.58.224.126), 64 hops max, 40 byte packets
1 192.168.2.1 (192.168.2.1) 4.729 ms 1.340 ms 1.220 ms
2 85.134.128.3 (85.134.128.3) 40.440 ms 34.838 ms 49.403 ms
3 fe-0-0-0_0.bdr001.dublin.clearwire.ie (85.134.255.13) 31.876 ms 58.111 ms 38.635 ms
4 ge-5-0-0.403.ar1.dub1.gblx.net (67.17.211.53) 98.498 ms 38.516 ms 32.663 ms
5 so0-0-0-2488m.ar3.lon2.gblx.net (67.17.71.25) 48.707 ms 52.150 ms 59.905 ms
6 bbc-gw0-linx.prt0.thdoe.bbc.co.uk (195.66.224.103) 98.981 ms * 129.496 ms
7 212.58.238.129 (212.58.238.129) 49.683 ms 48.155 ms 54.874 ms
8 www26.thdo.bbc.co.uk (212.58.224.126) 82.364 ms 46.002 ms 57.417 ms

ping www.clearwire.ie
\PING www.clearwire.ie (85.134.255.242): 56 data bytes
64 bytes from 85.134.255.242: icmp_seq=0 ttl=61 time=33.875 ms
64 bytes from 85.134.255.242: icmp_seq=1 ttl=61 time=94.234 ms
64 bytes from 85.134.255.242: icmp_seq=2 ttl=61 time=31.316 ms
64 bytes from 85.134.255.242: icmp_seq=3 ttl=61 time=93.845 ms
64 bytes from 85.134.255.242: icmp_seq=4 ttl=61 time=30.922 ms
64 bytes from 85.134.255.242: icmp_seq=5 ttl=61 time=70.539 ms
64 bytes from 85.134.255.242: icmp_seq=6 ttl=61 time=30.474 ms
64 bytes from 85.134.255.242: icmp_seq=7 ttl=61 time=34.542 ms
64 bytes from 85.134.255.242: icmp_seq=8 ttl=61 time=38.555 ms
64 bytes from 85.134.255.242: icmp_seq=9 ttl=61 time=84.327 ms
64 bytes from 85.134.255.242: icmp_seq=10 ttl=61 time=46.525 ms
64 bytes from 85.134.255.242: icmp_seq=11 ttl=61 time=50.518 ms
64 bytes from 85.134.255.242: icmp_seq=13 ttl=61 time=218.784 ms
64 bytes from 85.134.255.242: icmp_seq=14 ttl=61 time=112.508 ms
64 bytes from 85.134.255.242: icmp_seq=15 ttl=61 time=49.668 ms
64 bytes from 85.134.255.242: icmp_seq=16 ttl=61 time=46.078 ms
^C
--- www.clearwire.ie ping statistics ---
17 packets transmitted, 16 packets received, 5% packet loss
round-trip min/avg/max/stddev = 30.474/66.669/218.784/46.891 ms

traceroute www.clearwire.ie
traceroute to www.clearwire.ie (85.134.255.242), 64 hops max, 40 byte packets
1 192.168.2.1 (192.168.2.1) 4.147 ms 1.370 ms 1.273 ms
2 85.134.128.3 (85.134.128.3) 47.739 ms 30.847 ms 225.024 ms
3 85.134.255.37 (85.134.255.37) 266.437 ms 45.693 ms 32.921 ms
4 cwi001.clearwire.ie (85.134.255.242) 40.423 ms * 33.639 ms

ping www.google.com
PING www.l.google.com (66.249.93.104): 56 data bytes
64 bytes from 66.249.93.104: icmp_seq=0 ttl=244 time=88.075 ms
64 bytes from 66.249.93.104: icmp_seq=1 ttl=244 time=57.799 ms
64 bytes from 66.249.93.104: icmp_seq=2 ttl=244 time=53.389 ms
64 bytes from 66.249.93.104: icmp_seq=3 ttl=244 time=57.682 ms
64 bytes from 66.249.93.104: icmp_seq=4 ttl=244 time=53.019 ms
64 bytes from 66.249.93.104: icmp_seq=5 ttl=244 time=57.012 ms
64 bytes from 66.249.93.104: icmp_seq=6 ttl=244 time=52.644 ms
64 bytes from 66.249.93.104: icmp_seq=7 ttl=244 time=99.393 ms
64 bytes from 66.249.93.104: icmp_seq=8 ttl=244 time=52.352 ms
64 bytes from 66.249.93.104: icmp_seq=9 ttl=244 time=64.702 ms
64 bytes from 66.249.93.104: icmp_seq=10 ttl=244 time=345.001 ms
64 bytes from 66.249.93.104: icmp_seq=11 ttl=244 time=56.016 ms
^C
--- www.l.google.com ping statistics ---
12 packets transmitted, 12 packets received, 0% packet loss
round-trip min/avg/max/stddev = 52.352/86.424/345.001/79.293 ms

traceroute www.google.com
traceroute: Warning: www.google.com has multiple addresses; using 66.249.93.104
traceroute to www.l.google.com (66.249.93.104), 64 hops max, 40 byte packets
1 192.168.2.1 (192.168.2.1) 8.600 ms 1.408 ms 18.094 ms
2 85.134.128.3 (85.134.128.3) 41.761 ms 32.796 ms 32.605 ms
3 fe-0-0-0_0.bdr001.dublin.clearwire.ie (85.134.255.13) 48.704 ms 61.905 ms 40.739 ms
4 ge-5-0-0.403.ar1.dub1.gblx.net (67.17.211.53) 57.086 ms 56.465 ms 32.557 ms
5 so0-0-0-2488m.ar3.lon2.gblx.net (67.17.71.25) 57.074 ms 71.134 ms 76.707 ms
6 ldn-b1-pos2-0.telia.net (213.248.100.1) 57.072 ms 54.616 ms 50.326 ms
7 google-104716-ldn-b1.c.telia.net (213.248.74.194) 283.186 ms 114.281 ms 49.082 ms
8 72.14.238.242 (72.14.238.242) 174.266 ms 62.448 ms 72.14.238.246 (72.14.238.246) 55.761 ms
9 216.239.43.91 (216.239.43.91) 60.822 ms 62.387 ms 65.945 ms
10 216.239.43.88 (216.239.43.88) 82.232 ms 54.212 ms 216.239.43.96 (216.239.43.96) 74.512 ms
11 66.249.94.54 (66.249.94.54) 61.380 ms 66.249.94.50 (66.249.94.50) 70.796 ms 66.249.94.54 (66.249.94.54) 154.701 ms
12 66.249.94.58 (66.249.94.58) 71.723 ms 66.249.94.46 (66.249.94.46) 71.124 ms 66.249.93.104 (66.249.93.104) 53.659 ms

Shougeki · 16-11-2005 7:51am

Yeah m ines fine too.....

Anychance you can let me know what you are getting on the giganews speed test?

http://www.giganews.com/test_connect.html

stakey · 16-11-2005 10:37am

Best one yet....

Test done on irishisptest.com at 8.50pm last night

1.5 Kbps downstream
14 Kbps upstream

Improved to wait for it....

150 Kbps downstream
75 Kbps upstream

after one hour of foaming at the mouth.

Okay speed earlier in the day but pings in CS:Source were 380 dropping to 125 when they were good

Previous they I noted a consistant ping of 940 in CS:Source and 780 in BF2

Clearwire pull the finger out, now!

When I first got a 1mb connection off of them I had a connection like the following

1.5 Mbps downstream
612 Mbps upstream

(that was fairly regular only dropping a few kilobytes every now and again)

Pings in CS and BF2 were usually around 45, not bad for a wireless connection IMHO.

Getting a tad bit pissed off with this level of 'service'

Blaster99 · 16-11-2005 9:47pm

One thing I'm noticing with Clearwire, now that I have it, is that they don't seem to be peering at INEX. So all traffic goes quite a distance to an Irish server. Hence it's reasonable to expect fluctuations in pings and speed. This may or may not explain the problems in this thread.

Contrary to what I said above, irishisptest.com seems to be a pretty good indicator of Clearwire speeds.

eth0_ · 16-11-2005 10:53pm

No...you don't understand. These problems have only started in the past week.

Not peering at INEX would not cause packet loss and massive pings that people have been getting!

A nice chap at Clearwire rang me tonight to apologise for the issues, he said they've run diagonostics and can't see anything obviously wrong, there's no interference on my radio and the base station hasn't got a lot of users and despite being 'very quiet' tonight, I get these sh*tty pings.

He's going to call me again tomorrow with an update. Which is more than you get from IBB!

xeduCat · 16-11-2005 11:14pm

Just got my delivery today; there was a f'up via An Post, but I actually got it handdelivered after they (Clearwire) rang my mobile this evening. So I set it up in my apartment (Ranelagh Road), and at first instance, I wasn't one bit impressed...only got a single bar, and that was lucky. But then I moved it to my other window (where there isn't a 'block' from a nearby building), and I'm at 2/3 bars constant.

No serious packet loss (tried on multiple occasions with different combinations). Irishisptest is showing around 1.6 MB down and 200K up. Pings on HEANet below.

Should I be happy with this?

PING ftp.heanet.ie (193.1.193.64): 56 data bytes
64 bytes from 193.1.193.64: icmp_seq=0 ttl=59 time=38.316 ms
64 bytes from 193.1.193.64: icmp_seq=1 ttl=59 time=42.528 ms
64 bytes from 193.1.193.64: icmp_seq=2 ttl=59 time=36.598 ms
64 bytes from 193.1.193.64: icmp_seq=3 ttl=59 time=65.964 ms
64 bytes from 193.1.193.64: icmp_seq=4 ttl=59 time=36.383 ms
64 bytes from 193.1.193.64: icmp_seq=5 ttl=59 time=53.378 ms
64 bytes from 193.1.193.64: icmp_seq=6 ttl=59 time=94.812 ms
64 bytes from 193.1.193.64: icmp_seq=7 ttl=59 time=36.197 ms
64 bytes from 193.1.193.64: icmp_seq=8 ttl=59 time=48.627 ms
64 bytes from 193.1.193.64: icmp_seq=9 ttl=59 time=51.468 ms
64 bytes from 193.1.193.64: icmp_seq=10 ttl=59 time=51.218 ms
64 bytes from 193.1.193.64: icmp_seq=11 ttl=59 time=38.664 ms
64 bytes from 193.1.193.64: icmp_seq=12 ttl=59 time=33.875 ms
64 bytes from 193.1.193.64: icmp_seq=13 ttl=59 time=33.814 ms
64 bytes from 193.1.193.64: icmp_seq=14 ttl=59 time=33.675 ms
64 bytes from 193.1.193.64: icmp_seq=15 ttl=59 time=96.673 ms
64 bytes from 193.1.193.64: icmp_seq=16 ttl=59 time=33.515 ms
64 bytes from 193.1.193.64: icmp_seq=17 ttl=59 time=62.545 ms
64 bytes from 193.1.193.64: icmp_seq=18 ttl=59 time=62.340 ms
64 bytes from 193.1.193.64: icmp_seq=19 ttl=59 time=70.726 ms
64 bytes from 193.1.193.64: icmp_seq=20 ttl=59 time=62.139 ms
64 bytes from 193.1.193.64: icmp_seq=21 ttl=59 time=58.119 ms
64 bytes from 193.1.193.64: icmp_seq=22 ttl=59 time=45.307 ms
64 bytes from 193.1.193.64: icmp_seq=23 ttl=59 time=55.342 ms
64 bytes from 193.1.193.64: icmp_seq=24 ttl=59 time=61.998 ms
64 bytes from 193.1.193.64: icmp_seq=25 ttl=59 time=74.531 ms
64 bytes from 193.1.193.64: icmp_seq=26 ttl=59 time=34.387 ms
64 bytes from 193.1.193.64: icmp_seq=27 ttl=59 time=51.009 ms
64 bytes from 193.1.193.64: icmp_seq=28 ttl=59 time=42.366 ms
64 bytes from 193.1.193.64: icmp_seq=29 ttl=59 time=34.333 ms
64 bytes from 193.1.193.64: icmp_seq=30 ttl=59 time=34.144 ms
64 bytes from 193.1.193.64: icmp_seq=31 ttl=59 time=34.592 ms
64 bytes from 193.1.193.64: icmp_seq=32 ttl=59 time=34.007 ms
64 bytes from 193.1.193.64: icmp_seq=33 ttl=59 time=37.060 ms
64 bytes from 193.1.193.64: icmp_seq=34 ttl=59 time=41.183 ms
64 bytes from 193.1.193.64: icmp_seq=35 ttl=59 time=41.072 ms
64 bytes from 193.1.193.64: icmp_seq=36 ttl=59 time=36.653 ms
64 bytes from 193.1.193.64: icmp_seq=37 ttl=59 time=33.664 ms
64 bytes from 193.1.193.64: icmp_seq=38 ttl=59 time=37.604 ms
64 bytes from 193.1.193.64: icmp_seq=39 ttl=59 time=41.946 ms
64 bytes from 193.1.193.64: icmp_seq=40 ttl=59 time=37.478 ms
64 bytes from 193.1.193.64: icmp_seq=41 ttl=59 time=33.133 ms
64 bytes from 193.1.193.64: icmp_seq=42 ttl=59 time=33.268 ms
64 bytes from 193.1.193.64: icmp_seq=43 ttl=59 time=32.993 ms
64 bytes from 193.1.193.64: icmp_seq=44 ttl=59 time=37.021 ms
64 bytes from 193.1.193.64: icmp_seq=45 ttl=59 time=41.140 ms
64 bytes from 193.1.193.64: icmp_seq=46 ttl=59 time=36.918 ms
64 bytes from 193.1.193.64: icmp_seq=47 ttl=59 time=41.878 ms
64 bytes from 193.1.193.64: icmp_seq=48 ttl=59 time=36.685 ms
64 bytes from 193.1.193.64: icmp_seq=49 ttl=59 time=40.956 ms

--- ftp.heanet.ie ping statistics ---
50 packets transmitted, 50 packets received, 0% packet loss
round-trip min/avg/max/stddev = 32.993/45.685/96.673/14.999 ms

Ludo · 18-11-2005 10:07pm

ANyone else having trouble with ClearWire this evening..it's been pretty dismal all evening...especially for gaming..terrible pings.

antodeco · 19-11-2005 12:24am

Mine are fine. Running off the guinness mast 2 miles away.

Here are my results

Pinging www.boards.ie [82.195.136.250] with 32 bytes of data:

Reply from 82.195.136.250: bytes=32 time=28ms TTL=60
Reply from 82.195.136.250: bytes=32 time=32ms TTL=60
Reply from 82.195.136.250: bytes=32 time=31ms TTL=60
Reply from 82.195.136.250: bytes=32 time=71ms TTL=60

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

TRACERT

Tracing route to www.boards.ie [82.195.136.250]
over a maximum of 30 hops:

1 33 ms 32 ms 33 ms 85.134.128.3
2 30 ms 33 ms 37 ms fe-0-0-0_0.bdr002.dublin.clearwire.ie [85.134.25
5.12]
3 31 ms 62 ms 33 ms panama-inex.hosting365.ie [193.242.111.87]
4 43 ms 33 ms 50 ms corerouter1.hosting365.ie [82.195.128.7]
5 43 ms 37 ms 28 ms boards.ie [82.195.136.250]

Trace complete.

eth0_ · 19-11-2005 12:56pm

My pings are back to normal but i'm still quite often getting 5% packet loss, which I could ignore apart from the FREQUENT disconnects that keep happening! About ten ti mes in the past hour my connection has cr*pped out, it's really getting beyond a joke now.

PLEASE contact tech support and let them know you're experiencing this too.

Hoodle · 19-11-2005 1:33pm

Just checked irishisptest and I've got the following for ClearWire:

2.34meg downstream
274kb upstream

So why is there major lags in making phone calls on SkypeOut?!

Could it be something to do with the quality of service only being 44%??

EDIT

~this is ridiculous now - streaming music is a joke. Even on Lo-Fi it constantly stutters and rebuffers. Pile of s***e.

Ludo · 19-11-2005 2:13pm

yeah my stats for irish isp test are fantastic but finding servers for call of duty has been a pain in the ass forthe last two evenings.

eth0_ · 19-11-2005 3:03pm

It's absolutely unusable. I can barely get online. I'm supposed to be on call this weekend, if I get called i'll have to drive into work because I can't make a f*cking VPN connection. Really really not cool, clearwire.

PLEASE PHONE OR EMAIL SUPPORT AND LET THEM KNOW WHAT SH*T SERVICE YOU ARE GETTING!!

eth0_ · 19-11-2005 6:58pm

My internet connection stays up for a few minutes and then dies for 5.
This is absolutely crap.
I rang support around 3pm today and the guy said an on-call engineer was on his way in and he would ring me back within an hour. No call.

Looking to change providers now. This is a total joke.

RangeR · 19-11-2005 7:17pm

Yes, I was getting rediculous response today. All tests showed fine. Normal upload and download. 0 ping loss and average of about 30 to 40ms pings to boards. Brilliant. But...

... When I fire up Half Life 2 CTF, which I normally do at the weekends and normally get 40 ping, I was getting pings of 1000 to 3000. Totally unuseable.

However, I COULD download files at full speed. Totally baffeling, unless they are testing traffic shaping.

I was not aware that the support was open today, otherwise I would have called. I shall call them on Monday morning.

I had to switch to my DSL today. Much better response but not as good as a good clearwire.

antodeco · 20-11-2005 12:12am

Heres what I got from irishisptest earlier. Brilliant times. i havent had one outage, or disconnect in about 3 months. Had 2 in total since getting it. Both for about 5 mins at 1am! What mast are people on who are having problems? I wonder is it a mast issue? It seems strange that most people are using it fine, but theres a small amount who have a problem. Ive used skype and theres no problems. I did ring up customer care though, and checked with them first before using it. Whether they did someting with the modem or not is a different story, but it works!

eth0_ · 20-11-2005 10:50am

Are any of you using wireless routers?

if so, please disconnect them and see if you're experiencing the disconnections.

My connection has stayed up all night while my laptop has been connected directly to the modem.

Still getting crappy pings, but no disconnections.

Ludo · 20-11-2005 11:13am

I'm using a wireless router alright. The thing I noticed is that the green light on the ethernet port on the pback of the clearwire box keeps flickering as if the connection is going on and off all the time. I'll try connefting it directly now to see if ti makes a difference.

eth0_ · 20-11-2005 11:29am

Ludo wrote:

I'm using a wireless router alright. The thing I noticed is that the green light on the ethernet port on the pback of the clearwire box keeps flickering as if the connection is going on and off all the time. I'll try connefting it directly now to see if ti makes a difference.

Yes same here.
One of the support guys rang me to say he'd seen my last post on boards, he took a wireless router home yesterday and couldn't get it to sync with the modem either.

I might play around with MTU settings later today, could possibly be a solution.

Shougeki · 20-11-2005 11:37am

Ive had my laptop connected directly for the last week and getting shocking pings. However its gotten better from 130kb to 600-700kbs.

Thats still terrible for a 2meg line.

B

Ludo · 20-11-2005 11:42am

well connecting directly to the laptop made no difference at all. Tried ringing them a while ago but only got an answering machine telling me the office hours...emmm this is office hours.

anyway will ring tomorrow.

eth0_ · 20-11-2005 12:42pm

No they are there, Christian rang me about an hour ago.

Where abouts do you live, Ludo? Do you know if you're on the Guinness mast?

eth0_ · 20-11-2005 1:03pm

This is WEIRD.
In iTunes, I can see (and play music from) a library called "Conor Griffith's music".

I did a netstat and iTunes is connecting to a clearwire subscriber IP.

That's eh....not supposed to happen.

He has great taste in music, though.

Shougeki · 20-11-2005 2:51pm

Yep on the guiness mast. Was just talking to christian too.... Seems to be a nice guy, and really interested in helping solve this problem.

Good signal strength, good quality on the line, but getting a heck of a lot of interference from something.....

Are we all on the guiness mast havin this problem?

Line was fine yesterday (was playing WoW for a few hours with 100ish latency)

B

Shougeki · 20-11-2005 5:16pm

Powered off the modem for a few mins. Turnewd it on and the speed went back to 400/700 Mbs. Not great but better than the 60 i had all day.

B

Ludo · 20-11-2005 9:30pm

Nah,...I'm on the bray mast and getting crap pings since friday night...everything else is fine

eth0_ · 20-11-2005 10:06pm

not getting disconnected now while connected to my wireless router, but pings are all over the place.

--- www.clearwire.ie ping statistics ---
990 packets transmitted, 882 packets received, 10% packet loss
round-trip min/avg/max/stddev = 30.257/89.247/478.581/67.969 ms

Ludo · 21-11-2005 11:04am

Well rang Clearwire customer care there about the latency issues. They said they will run some tests and get back to me. They said they have received some reports about this but dont think there is a problem..emm yes there is...

Mac daddy · 21-11-2005 11:08am

I needed to login into work this morning at 5am and could not get a connection, reset it a couple of times and it was not picking up a Ip adress 3 bars green.

Couple of problems yesterday - crap pings and high latency...
Connecting to Killiney.

Ringing them later on.

Blaster99 · 21-11-2005 12:11pm

I'm admittedly not a very frequent user, particularly not last weekend, but I haven't seen any major problems. I don't play games so the occasional ping spike wouldn't bother me, but if I run ping tests I've never seen ping spikes.

One thing I have noticed, however, is that the speeds to/from various locations vary quite a bit. Just looking at speed test sites, irishisptest tells me 2.25M/243K, adslguide.org.uk tells me 1M/54K. That's a pretty significant difference in speed.

Incidently, why do people even use the ClearWire service? It's no cheaper than BT Ireland's ADSL and certainly not as good. The only reason I signed up for it is that it was available the next day whereas ADSL without a phone line is a two month process and I needed it quickly. The nomadic aspect of the service is useful too.

eth0_ · 21-11-2005 1:05pm

I got clearwire because I don't want a phoneline in my name.

Please RING THEM if you're having problems, rather than mention it on here.

I'm still getting constant disconnects.

Also, seeing another clearwire users iTunes library is quite worrying from a security POV :-(

Blaster99 · 21-11-2005 1:14pm

I incidently just found out that they block VoIP traffic by default. The person I spoke to in Clearwire didn't exactly instill me with confidence that they will enable it, even though I understand from other people that they will. The sales rep told me that VoIP is not blocked.

ZENER · 21-11-2005 1:19pm

They monitor this thread anyway so it's in their own interest to resolve these issues. I'm not a gamer so latency and pings don't bother me but I've had no problems with connection or speed in the 3 months I've had the service here in Swords.

The iTunes thing is interesting, the Clearwire "modem" when connected directly to your computer gives it the clearwire i.p. address, e.g. 83.134.x.x etc instead of a home ip like 192.168.x.x or 10.0.0.X. Doesn't this make your machine part of a LAN with anyone else doing the same without a router and NAT on that same subnet?

Have you tried to "Go >> Connect To Server . . " with that user via SMB or ATP ? Are you able to reach him all the time, maybe he leaves his computer connected 24hrs. Whats his musical taste like

ZEN

ClearWire in ****e tonight?!

Comments