![]() ![]() ![]() |
|
For the Telstra problem changing to a static IP on an unaffected range might be a viable workaround.
I've only ran a few matches of overwatch tonight, certainly had no issues over my spark link.
VF Link had some jitter.. i digress though..
Some jitter is to be expected, other systems etc do operate on my link.
Vodafone ADSL: interleaving off.
--- 203.36.148.11 ping statistics --- 10 packets transmitted, 10 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 45.783/46.128/47.540/0.504 ms
Spark VDSL: G.INP (Basically interleaving off)
--- 203.36.148.11 ping statistics --- 10 packets transmitted, 10 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 43.959/44.387/45.630/0.499 ms
to me, for a work around that's not so bad at all.
#include <std_disclaimer>
Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.
Hi
Tonight my Spark NZ Fibre 100 show the below ping 158 ms
My Spark 4G Hotspot show a much better ping 79 ms
Looking at Talkinet Spark VDSL Latency of 40 ms I am very happy with his result, is it something you could use for my IP to be the same as Spark VDSL Subnet? (Or any other unaffected Sub). That could solve my issue I think?
It is really unfair for me to continue to pay Spark Fibre 100 and not getting an acceptable performance working remotely and most of other connection works very well e.g. Vodafone VDSL, Spark 4G Hotspot, Internet Cafe, Auckland City Library........ I just feel it is just my Fibre 100 that got that issue.
First, when Chorus set up my Fibre, Spark brand new Huawei modem was dead and I didn't get my fibre installed and had to ordered a new box,
Second I am not getting a faster access for my remote work.
Argggggg....!!!!!
I have tried again at Vodafone VDSL and they are getting 28 ms....... :S
e.g. 222.152.x.x reboot 122.57.x.x reboot 219.89.x.x
yitz: Seems whatever change they made this morning has resulted in some of their Aus peering links running at 100% utilisation for the last few hours. For the Telstra problem changing to a static IP on an unaffected range might be a viable workaround.
Any idea what unaffected ranges we could try?
Talkiet:
I'm sorry no, we don't have a timeframe on when Telstra will address the issue. Unfortunately it's an upstream network and not one we have any direct control over.
As for decisions to engineer traffic around it - I'm not sure how feasible that is since the affected traffic is predominantly from within Telstra (I think). I'm certainly not in a position to evaluate what options we might have to mitigate their problem.
As to your example - a lot of devices within networks are lazy in answering ICMP or throttled, so you really shouldn't pay too much attention to a lot of interim hops. The Telstra server looks a stable 40ms away from you which seems about right.
There may certainly be an issue, but that screenshot doesn't necessarily illustrate one, and the WoW 'ping' meter hasn't been accurate a day in it's life.
Cheers -N
Ping displayed in WoW may not be accurate but the lag experienced is definitely noticeable by the user. Getting large spikes in latency in other games such as PoE also
I'm guessing that only certain areas are affected and I understand that this issue is not on Sparks end but is there anything spark can do (i.e. give new IP) for individual users affected by the Telstra issue?
Or are we supposed to just wait for an unknown period of time for Telstra to fix this on their end?
by keen for any resolution for no cost to make me a happy customer. All I need is a fastest telstra for my remote work now.
Looking at a quick solve, having a IP on a non sub affected ranged seems to be a quick fix.
If you're on a static IP already, you can temporarily get a dynamic by putting "NoStatic" in your PPP username field... If you're on a dynamic IP, then any dynamic IP you are given is going to be routed the same (on our end - I don't know what the telstra fault is precisely and whether it would be affected just by getting a different IP hosted on the same BNG).
Out of interest, what's the packet loss like?
Cheers - N
Please note all comments are from my own brain and don't necessarily represent the position or opinions of my employer, previous employers, colleagues, friends or pets.
noroad:
Nothing wrong on my Southern Cross Sydney links, smooth 26.5ms all the way.
Bit late for a reply but there was another issue with SX on the ground link in Sydney last Wed/Thu. I was actually in Samoa working at Digicell and they were impacted by this.
Their normal traffic routing of the new SSCC to Fiji and then SX to Sydney was impacted and all traffic was taking their diverse path of SSCC to Fiji then SX to Hawaii and then SX to Auckland and then SX to Sydney which added about another 120ms
sbiddle:
Bit late for a reply but there was another issue with SX on the ground link in Sydney last Wed/Thu. I was actually in Samoa working at Digicell and they were impacted by this.
Their normal traffic routing of the new SSCC to Fiji and then SX to Sydney was impacted and all traffic was taking their diverse path of SSCC to Fiji then SX to Hawaii and then SX to Auckland and then SX to Sydney which added about another 120ms
I would be a little careful saying there is an issue on SX. SX itself is normally fine, most of the issues come from how companies pick up the SX circuits from the landing stations from my experience. We have dual protected SX paths to Australia (and TGA) and while it is not uncommon to lose one or the other due to the terrestrial component the other path pretty much always maintains the short path as the sub-sea component is still working just fine. I think SX takes a lot of flack for what is quite often third parties choosing less than fully diverse terrestrial backhaul options from the landing stations. I fully understand why companies architect in this way, but its a bit rough to just blame SX when their part in the service is fine.
FYI Vodafone VDSL:
Out of interest, what's the packet loss like?
Cheers - N
Please note all comments are from my own brain and don't necessarily represent the position or opinions of my employer, previous employers, colleagues, friends or pets.
|
![]() ![]() ![]() |