I think its time I added my name to this thread too.
Unfortunatly Ive had problems since Ive signed up with Xnet. Ive been getting very bad national pings/traffic at night and international traffic may as well not exist. Im on the fs/256 plan with no cap.
Ive rung the helpdesk and at first they said they think its telecoms equipment and got me to run a few tests, which revealed some results which looked extremely poor. When I submitted them back Xnet finally admitted they were having problems with congestion etc...
Heres the sort of speed im experiencing, Im sure many of you are familiar with this:
Speed test statistics
---------------------
Download speed: 368736 bps
Upload speed: 65760 bps
Quality of service: 30 %
Download test type: socket
Upload test type: socket
Maximum download pause: 993 ms
Average download pause: 103 ms
Minimum round trip time to server: 254 ms
Average round trip time to server: 346 ms
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 0 | 101 | 101 | 0 | 0 | 10 | 0 |
| int-l35-akl-dsl02.wxnz.net - 3 | 100 | 97 | 100 | 116 | 200 | 121 |
| ge-1-0-0-57-jcore3.wxnz.net - 5 | 100 | 95 | 100 | 113 | 150 | 120 |
| northnet.net.nz - 2 | 100 | 98 | 100 | 112 | 121 | 110 |
|________________________________________________|______|______|______|______|______|______|
However, one other very big problem im currently having is that many servers/websites (international) are just simply not working (well, not within reasonable time limits.) Has anyone else not been able to access MSN Messenger for a few days? I havent. Because it times out before it has a chance, I was actually able to access the webmessenger.msn.com website yesterday and it only took 15 minutes to load.
I did a tracert on messenger.hotmail.com (the msn messenger server) and found this:
tracert messenger.hotmail.com
Tracing route to dp.msnmessenger.akadns.net [65.54.239.140]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 89 ms 77 ms 75 ms int-l35-akl-dsl02.wxnz.net [58.28.15.71]
3 71 ms 72 ms 69 ms ge-1-0-0-57-jcore3.wxnz.net [58.28.13.49]
4 78 ms 71 ms 80 ms ge-0-0-0-akl-core1.wxnz.net [58.28.8.8]
5 74 ms 66 ms 74 ms Gi9-1.gw1.akl1.asianetcom.net [203.192.166.105]
6 75 ms 71 ms 73 ms ge-3-3-0-0.gw4.akl1.asianetcom.net [202.147.55.210]
7 195 ms 196 ms 201 ms po7-3.gw2.sjc1.asianetcom.net [202.147.55.158]
8 * * * Request timed out.
9 * * * Request timed out.
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.
If you have a look at the results, you can see that nothings getting past the asianetcom server (which is known for having ongoing issue after issue). I rang the helpdesk to notify them of this and ask for a timeframe for a fix for the problem with international traffic which they bluntly told me that there was no problem with international traffic that they were aware of.
Is anyone else having problems as major as mine? It would be nice to know im not the only one.
For the meantime though, im getting better pings in counterstrike with dialup than I am for my broadband.
