Why can’t you run a reliable service? I’m constantly getting timeouts while using your service. Meaning no MSN, no Skype, bearly any web browsing, patchy email…

I’ve contacted you 7 times now…

Click read more to see the support email

From: Henry P. K. Armitage
Sent: 06 December 2005 08:04
To: ‘wirelesssupport@tranzeo.com’
Subject: Frequent Timeouts

Hello,

I�m currently using Tranzeo from the WhistlerBlackcomb HOUSE � Bluevault location (network SSID: WBBLUEVAULT).

While using the network in the later half of last night and this morning, there have been frequent timeouts when trying to access the internet, especially noted when browsing webpages. The timeouts are affecting all programs and services that are using the internet (that includes email and MSN, which are the two ways I communicate home). Some connections however do succeed, but I would estimate 2/3rds of them fail.

Tried so far:
� Repair Connection
� Turn off wireless adaptor and back on again
� Rebooting
� Ipconfig /flushdns

Here are a few pings and tracerts:

Microsoft.com (at about 07:40):

C:\Documents and Settings\H>ping microsoft.com

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

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

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

C:\Documents and Settings\H>tracert microsoft.com

Tracing route to microsoft.com [207.46.130.108]
over a maximum of 30 hops:

1 16 ms 14 ms 11 ms FastEthernet0-1.vgs3.navigata.net [204.244.10.73
]
2 30 ms 7 ms 8 ms 61.17.204.10.in-addr.arpa [10.204.17.61]
3 8 ms 7 ms 11 ms ge-0-1-0-3.vgs1.navigata.net [204.244.12.43]
4 19 ms 8 ms 14 ms navigata-van-gw.peer1.net [216.187.82.17]
5 19 ms 17 ms 12 ms OC48-POS0-0.sea-dis-1.peer1.net [216.187.88.214]

6 19 ms 16 ms 13 ms peer1-gw.hotmail.com [216.187.64.58]
7 16 ms 12 ms 13 ms ten7-1.wst-76cb-1a.ntwk.msn.net [207.46.35.49]
8 16 ms 36 ms 13 ms pos1-0.wst-12ix-1a.ntwk.msn.net [207.46.36.210]

9 18 ms 13 ms 13 ms pos1-0.iuscixwstc1201.ntwk.msn.net [207.46.155.1
7]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Google.co.uk (this one worked) (at about 07:55):
C:\Documents and Settings\H>ping goolge.co.uk

Pinging goolge.co.uk [80.245.197.244] with 32 bytes of data:

Reply from 80.245.197.244: bytes=32 time=183ms TTL=51
Reply from 80.245.197.244: bytes=32 time=188ms TTL=51
Reply from 80.245.197.244: bytes=32 time=192ms TTL=51
Reply from 80.245.197.244: bytes=32 time=193ms TTL=51

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

C:\Documents and Settings\H>tracert google.co.uk

Tracing route to google.co.uk [216.239.59.104]
over a maximum of 30 hops:

1 13 ms 13 ms 11 ms FastEthernet0-1.vgs3.navigata.net [204.244.10.73
]
2 9 ms 9 ms 7 ms 61.17.204.10.in-addr.arpa [10.204.17.61]
3 16 ms 26 ms 48 ms ge-2-0-0-2.vgs1.navigata.net [204.244.12.11]
4 14 ms 8 ms 11 ms navigata-van-gw.peer1.net [216.187.82.17]
5 21 ms 15 ms 19 ms OC48-POS0-0.sea-dis-1.peer1.net [216.187.88.214]

6 37 ms 34 ms 34 ms GIG0-0.sj-dis-a.peer1.net [216.187.88.202]
7 52 ms 35 ms 35 ms core2-1-1-0.pao.net.google.com [198.32.176.31]
8 34 ms 55 ms 40 ms 66.249.94.12
9 41 ms 37 ms 39 ms 72.14.236.8
10 97 ms 85 ms 85 ms 66.249.95.247
11 * 85 ms 85 ms 66.249.95.247
12 * 94 ms 95 ms 66.249.94.232
13 92 ms 176 ms 106 ms 66.249.95.122
14 95 ms 111 ms 98 ms 66.249.94.234
15 107 ms 96 ms 109 ms 35.49.239.216.in-addr.arpa [216.239.49.35]
16 175 ms 178 ms 191 ms 66.249.95.147
17 173 ms 171 ms 176 ms 72.14.238.249
18 193 ms 195 ms 188 ms 254.49.239.216.in-addr.arpa [216.239.49.254]
19 208 ms 193 ms 189 ms 158.48.239.216.in-addr.arpa [216.239.48.158]
20 199 ms 188 ms 192 ms 104.59.239.216.in-addr.arpa [216.239.59.104]

Trace complete.

I would appreciate any advice on this matter

Regards

Henry Armitage

P.s. This, I believe, is the 7th time I have had to contact your support team in order to resolve issues with your network, where Tranzeo was at fault. I do not feel this is value for money at all, nor do I feel you are providing a reliable service. I would appreciate some credit on my account, seeing as I have not been able to use your service for about 12 hours.