[WXC/VFX] Recent Xnet Speed Woes

Forums › Vodafone New Zealand › [WXC/VFX] Recent Xnet Speed Woes

ajobbins

Awesome
4843 posts

Uber Geek
+1 received by user: 1099

Trusted

Subscriber

# 19130 6-Feb-2008 12:27

Over the last couple of weeks I have noticed a dramatic slowdown in my Xnet HSI speeds. Speed tests seem to confirm this.

I have a 16663/945Kbps sync (Down from the 19m or so I was able to easily sync at when our ADSL2+ first went live).

Here are the results from some speed tests today:

Auckland:

Wellington:

Sydney:

As you can see from this one, I can upload to Sydney at about the same rate I can download.

Is anyone else on Xnet having similar issues?

grant_k

3539 posts

Uber Geek
+1 received by user: 125

Trusted

# 108874 6-Feb-2008 12:36

Here is my Xnet FLOOD connection via the Avondale exchange:

So it seems that your connection has some specific issue which is not affecting Xnet as a whole.

Detruire

1266 posts

Uber Geek
+1 received by user: 66

# 108875 6-Feb-2008 12:37

Yes, but only internationally. National speeds are about the same (although less, but that's probably exchange related)
Oh, and the wellington server is always better than the Auckland one.

rm *

ajobbins

Awesome
4843 posts

Uber Geek
+1 received by user: 1099

Trusted

Subscriber

# 108877 6-Feb-2008 12:45

A couple weeks ago I was easily getting 6-7mbit down (Sometimes even higher) from both Wellington and Auckland and a good couple of mbits down from Sydney.

Even the Xnet VFX speedtest is only giving me 983kbps down and QoS of 68% :(

grant_k

3539 posts

Uber Geek
+1 received by user: 125

Trusted

# 108879 6-Feb-2008 12:49

Have you checked the CRC Error Counters in your modem to see if something is amiss there?

What about others in your neighbourhood on the same exchange -- are they having similar issues?

Niel

3267 posts

Uber Geek
+1 received by user: 77

Trusted

# 108880 6-Feb-2008 12:49

My speed to Sydney is 2.5Mbps via Speedtest.Net and 3.6Mbps to XNet using their own test. I'm in Pakuranga. My speed is what it normally is on weekends/evenings/holidays.

You can never have enough Volvos!

ajobbins

Awesome
4843 posts

Uber Geek
+1 received by user: 1099

Trusted

Subscriber

# 108881 6-Feb-2008 12:53

Below are the line stats. Only people we know who are on the same exchange are the neigbours and they are on a 256/128 plan where as we are on FS/FS. We are on the Courtney Place exchange BTW.

Line Mode	ADSL2+	Line State	Show Time
Line Power State	L0	Line Up Time	00:01:37:40
Line Coding	Trellis On	Line Up Count	1

Statistics	Downstream	Upstream
Line Rate	16663 Kbps	945 Kbps
Attainable Line Rate	18812 Kbps	945 Kbps
Noise Margin	11.9 dB	16.4 dB
Line Attenuation	15.5 dB	4.7 dB
Output Power	16.8 dBm	12.4 dBm
MSGC (number of bytes in overhead channel message)	59	14
B (number of bytes in Mux Data Frame)	46	13
M (number of Mux Data Frames in FEC Data Frame)	1	16
T (Mux Data Frames over sync bytes)	11	7
R (number of check bytes in FEC Data Frame)	10	16
S (ratio of FEC over PMD Data Frame length)	0.0901	7.5000
L (number of bits in PMD Data Frame)	5062	256
D (interleave depth)	256	8
Delay	5	15
Super Frames	363954	363952
Super Frame Errors	0	0
RS Words	260227770	1546796
RS Correctable Errors	0	4250
RS Uncorrectable Errors	0	0
HEC Errors	0	528
OCD Errors	0	0
LCD Errors	0	0
Total Cells	230319808	1388783829
Data Cells	1756077	164462354
Bit Errors	0	24180
Total ES	0	0
Total SES	0	0
Total UAS	16	0

grant_k

3539 posts

Uber Geek
+1 received by user: 125

Trusted

# 108883 6-Feb-2008 13:00

The Error Count looks to be minimal, with just a few errors happening on your Upstream link.

It doesn't appear as though there are any problems with your router or line as the Noise Margin and Attenuation look great.

Given that your neighbours are on such a slow plan, it probably won't be of any help comparing Speed Tests from their connection. It looks to me as though it could be:

- A faulty port on your ISAM at the exchange/roadside cabinet

- A wider exchange or backhaul issue

Really, you will have to enlist Xnet's help to solve this one. Post back any comments once you have contacted them, and it will be interesting to see what the solution is.