Terrible spark service, need help with VDSL

Forums › Spark New Zealand (including Skinny and BigPipe) › Terrible spark service, need help with VDSL

1 | 2 | 3 | 4

4792 posts

Uber Geek

Trusted

#1418954 2-Nov-2015 16:19

jeeg: Yes I use adblockers, but the issues happen on twitter app on my iPhone as well.

I did a quick continuous ping to 219.88.188.5, not sure how long I was supposed to leave that running.

Pinging 219.88.188.5 with 32 bytes of data:
Reply from 219.88.188.5: bytes=32 time=7ms TTL=61
Reply from 219.88.188.5: bytes=32 time=29ms TTL=61
[snip]
Reply from 219.88.188.5: bytes=32 time=7ms TTL=61
Ping statistics for 219.88.188.5: Packets: Sent = 70, Received = 70, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 7ms, Maximum = 29ms, Average = 8ms
Control-C
^C

Can you try using a browser with no adblocker please? I'm not saying forever, I just want to see if that has an impact. (Yes I saw your comment about twitter on your phone being affected as well)

And for the continuous Ping, I meant to leave that running for a long time, so that when you experience issues you can flip to that window and see if there are pings being dropped or if the latency is going through the roof.

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.

thefunkysoulone

59 posts

Master Geek

Trusted

#1419247 2-Nov-2015 20:50

Finally someone with the same issue. I am just up the road in sunnynook

I am having exactly the same issue. I have the technicolor router with an additional router running the lan.

I have vdsl and have never had any issues until about 3 or 4 weeks ago. Consistently intermittent on every website, the majority of them won't load without constant refreshing, then everything works for a few minutes then stops again.

It seemed to be worse on apple devices and have also bought a new router but have the same issues.

However, I am sat here now streaming bc iplayer with no issue, although Netflix US doesn't work too well.

I am getting 28 up, 9 down with 9ms ping from the Spark Auckland speediest server so something else must be up.

I have thought that it could be dns and have updated all of the devices, but this still doesn't explain why it just changed a few weeks ago.

Any ideas would great, I was about to ring Spark but found this post.

jeeg

351 posts

Ultimate Geek

#1419248 2-Nov-2015 20:50

I've tried using Firefox with no extensions (fresh install) and it's still happening. When I check the pingtest when the problem occurs, I still get the same pings with no drops and no big spikes.

cbrpilot

955 posts

Ultimate Geek

Trusted

Spark NZ

#1419256 2-Nov-2015 21:14

Can anyone who is experiencing this issue please post up the first 3 octets of your IP address. You WAN IP please.

My views are my own, and may not necessarily represent those of my employer.

jeeg

351 posts

Ultimate Geek

#1419266 2-Nov-2015 21:32

222.152.162.xx

PRH

8 posts

Wannabe Geek

#1419287 2-Nov-2015 21:47

222.152.170.**

aurora2

5 posts

Wannabe Geek

#1419297 2-Nov-2015 21:55

222.152.168.**

AliExpress

Shop now on AliExpress (affiliate link).

thefunkysoulone

59 posts

Master Geek

Trusted

#1419349 2-Nov-2015 22:38

222.152.165.xx

jeeg

351 posts

Ultimate Geek

#1419571 3-Nov-2015 10:42

The problem seems to have worsened this morning. Now I'm getting very high pings to every server.

Pinging 219.88.188.5 with 32 bytes of data:
Reply from 219.88.188.5: bytes=32 time=2256ms TTL=61
Reply from 219.88.188.5: bytes=32 time=2523ms TTL=61
Reply from 219.88.188.5: bytes=32 time=2757ms TTL=61
Reply from 219.88.188.5: bytes=32 time=2277ms TTL=61
Reply from 219.88.188.5: bytes=32 time=2289ms TTL=61
Reply from 219.88.188.5: bytes=32 time=2298ms TTL=61
Reply from 219.88.188.5: bytes=32 time=2298ms TTL=61
Reply from 219.88.188.5: bytes=32 time=2450ms TTL=61
Reply from 219.88.188.5: bytes=32 time=2305ms TTL=61
Reply from 219.88.188.5: bytes=32 time=2293ms TTL=61
Reply from 219.88.188.5: bytes=32 time=2314ms TTL=61
Reply from 219.88.188.5: bytes=32 time=2295ms TTL=61
Reply from 219.88.188.5: bytes=32 time=2334ms TTL=61
Reply from 219.88.188.5: bytes=32 time=2326ms TTL=61
Reply from 219.88.188.5: bytes=32 time=2305ms TTL=61

Ping statistics for 219.88.188.5:
Packets: Sent = 15, Received = 15, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2256ms, Maximum = 2757ms, Average = 2354ms
Control-C

Heres results from a trace route command.

Tracing route to cache.google.com [219.88.188.5]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.1.1
2 2604 ms 2337 ms 2295 ms 122-62-240-1.jetstream.xtra.co.nz [122.62.240.1]

3 * * * Request timed out.
4 2290 ms 2274 ms 2292 ms cache.google.com [219.88.188.5]

Trace complete.

Talkiet

4792 posts

Uber Geek

Trusted

#1419578 3-Nov-2015 10:47

jeeg: The problem seems to have worsened this morning. Now I'm getting very high pings to every server.

Please answer my PM and supply your phone number so we can have a look at something... We've got something to try but we need customer details.

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.

jrobbio

3 posts

Wannabe Geek

#1419598 3-Nov-2015 11:05

222.152.169.*

All the IPs I am seeing listed are part of the 16K addresses of 222.152.128.0/18 i.e. between 222.152.128.1 and 222.152.191.254. That is the AS4771 BGP announcement https://www.robtex.com/route/222.152.128.0-18.html

PRH

8 posts

Wannabe Geek

#1419639 3-Nov-2015 11:30

As of first thing this morning, this seems to be resolved for me. Am monitoring.....

Talkiet

4792 posts

Uber Geek

Trusted

#1419852 3-Nov-2015 14:14

Well, I'm glad it seems to be better for everyone reporting these specific symptoms today, but I have to admit that we didn't find a root cause or make any changes that are likely to have fixed what did look like an issue.

We localised the issue to a single BNG and were in the process of collecting details of affected customers so we could make some changes to their individual configurations to see if we could restore performance (and isolate the root cause at the same time) when the issue stopped.

If any of the same users experience a recurrence of the issue, please drop me a line and we can carry on with the troubleshooting. There is absolutely no point in trying anything while the performance is ok though.

Thanks for your patience and the details provided so far.

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.

jeeg

351 posts

Ultimate Geek

#1419883 3-Nov-2015 14:41

Still having issues here, sent you a PM with details.

cbrpilot

955 posts

Ultimate Geek

Trusted

Spark NZ

#1419904 3-Nov-2015 15:01

jeeq can you confirm that it was working ok between 10:47:23am and 13:00:42 today?
And it is back to not working again?

My views are my own, and may not necessarily represent those of my employer.

1 | 2 | 3 | 4