Spark issues last two weeks VDSL

Forums › Spark New Zealand (including Skinny and BigPipe) › Spark issues last two weeks VDSL

1 | 2

andrewk

48 posts

Geek

#1413156 24-Oct-2015 13:11

Talkiet: That ip is from a chch based Google cache node. I chose it because I know how traffic for chch vdsl users is routed there. It's interesting that other places aren't visible. I'm out and about only on mobile at the moment so can't do any more troubleshooting right now sorry.

N

tried plugging 219.88.188.134 in the browser but timed out. Appreciate the input, its gone to sleep about three times today so at least it should show something in the monitoring

Talkiet

4792 posts

Uber Geek

Trusted

#1413219 24-Oct-2015 16:54

Unfortunately no... If you have uninterrupted access to the IP above, then there won't be anything wrong with your VDSL line. I do note however that your latency to the CHCH Google server was higher than I would expect so you appear to be on a profile with a little bit of interleaving (That's not a bad thing).

Next time you have an outage, please try pinging

219.88.188.68 (a wellington based google server)
219.88.188.4 (an auckland based Google server)

122.56.115.4 (a google server JUST outside of the Spark network)

and

news.com.au (a server in aussie that responds to ICMP)

I'm trying to see how far you can see during an outage.

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.

andrewk

48 posts

Geek

#1413225 24-Oct-2015 17:02

Talkiet: Unfortunately no... If you have uninterrupted access to the IP above, then there won't be anything wrong with your VDSL line. I do note however that your latency to the CHCH Google server was higher than I would expect so you appear to be on a profile with a little bit of interleaving (That's not a bad thing).

Next time you have an outage, please try pinging

219.88.188.68 (a wellington based google server)
219.88.188.4 (an auckland based Google server)

122.56.115.4 (a google server JUST outside of the Spark network)

and

news.com.au (a server in aussie that responds to ICMP)

I'm trying to see how far you can see during an outage.

Cheers - N

just had a message from the helpdesk to say the monitoring ended and they cant see any problems on the connection, ie no disconnections occurred

case# is 231341070109 if its any use...

I'll run those checks next time, it been ok for a couple of hours so it shouldn't be too far off

Cheers

andrewk

48 posts

Geek

#1413306 24-Oct-2015 20:41

Wouldn't you know it, its been running fine since I last posted...

yitz

2078 posts

Uber Geek

#1413309 24-Oct-2015 20:58

Perhaps your connection is being DDoS'd and your ISP automatically blackholes your IP or something.

Edit: oh you mentioned you have been DoS'd before... sure you haven't pissed someone off somewhere lately :/

andrewk

48 posts

Geek

#1413318 24-Oct-2015 21:31

yitz: Perhaps your connection is being DDoS'd and your ISP automatically blackholes your IP or something.

Edit: oh you mentioned you have been DoS'd before... sure you haven't pissed someone off somewhere lately :/

Yes I was wondering about that, last time though I had extraordinarily large data usage which is absent this time

andrewk

48 posts

Geek

#1413404 25-Oct-2015 10:21

Talkiet: Unfortunately no... If you have uninterrupted access to the IP above, then there won't be anything wrong with your VDSL line. I do note however that your latency to the CHCH Google server was higher than I would expect so you appear to be on a profile with a little bit of interleaving (That's not a bad thing).

Next time you have an outage, please try pinging

219.88.188.68 (a wellington based google server)
219.88.188.4 (an auckland based Google server)

122.56.115.4 (a google server JUST outside of the Spark network)

and

news.com.au (a server in aussie that responds to ICMP)

I'm trying to see how far you can see during an outage.

Cheers - N

Results are in - do I read this as traffic is unable to exit the spark network for some reason?
Appreciate you having a look, where to from here?

C:\WINDOWS\system32>ping 219.88.188.68

Pinging 219.88.188.68 with 32 bytes of data:
Reply from 219.88.188.68: bytes=32 time=25ms TTL=61
Reply from 219.88.188.68: bytes=32 time=24ms TTL=61
Reply from 219.88.188.68: bytes=32 time=25ms TTL=61
Reply from 219.88.188.68: bytes=32 time=25ms TTL=61

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

C:\WINDOWS\system32>ping 219.88.188.4

Pinging 219.88.188.4 with 32 bytes of data:
Reply from 219.88.188.4: bytes=32 time=32ms TTL=61
Reply from 219.88.188.4: bytes=32 time=32ms TTL=61
Reply from 219.88.188.4: bytes=32 time=33ms TTL=61
Reply from 219.88.188.4: bytes=32 time=32ms TTL=61

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

C:\WINDOWS\system32>ping 122.56.115.4

Pinging 122.56.115.4 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

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

C:\WINDOWS\system32>ping news.com.au
Ping request could not find host news.com.au. Please check the name and try agai
n.

C:\WINDOWS\system32>

Sharesies

Trade NZ and US shares and funds with Sharesies (affiliate link).

Talkiet

4792 posts

Uber Geek

Trusted

#1413406 25-Oct-2015 10:24

That's slightly stranger than I expected.

I don't know why you're missing name resolution as the DNS servers are within our network (unless for some reason you are using an external DNS server at the moment).

At this stage I'll have to engage someone directly on .. um, Tuesday sorry. It would be really helpful if you could PM me any known times of failure and restoration of service.

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.

andrewk

48 posts

Geek

#1413413 25-Oct-2015 10:50

Talkiet: That's slightly stranger than I expected.

I don't know why you're missing name resolution as the DNS servers are within our network (unless for some reason you are using an external DNS server at the moment).

At this stage I'll have to engage someone directly on .. um, Tuesday sorry. It would be really helpful if you could PM me any known times of failure and restoration of service.

Cheers - N

Umm sorry, yes DNS was still set to 8.8.8.8 from the last test

I'll keep a note of times for now, was dead this morning when I switched on just after 10 and has just now come back on.

and i'll rerun the pings using the spark DNS servers next time

Many thanks

andrewk

48 posts

Geek

#1414356 27-Oct-2015 08:59

Quick update, relatively stable connection yesterday until around 11pm - run pings at that time seem to be a difference there as couldn't even ping that chch google cache, results below.

C:\WINDOWS\system32>ping 219.88.188.134

Pinging 219.88.188.134 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

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

C:\WINDOWS\system32>ping 219.88.188.68

Pinging 219.88.188.68 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

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

C:\WINDOWS\system32>ping 219.88.188.4

Pinging 219.88.188.4 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

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

C:\WINDOWS\system32>ping news.com.au
Ping request could not find host news.com.au. Please check the name and try agai
n.

C:\WINDOWS\system32>ping 122.56.115.4

Pinging 122.56.115.4 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

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

Talkiet

4792 posts

Uber Geek

Trusted

#1416904 30-Oct-2015 12:12

Problem isolated: Customer static IP was being infrequently DDOSed and part of the mitigation strategy (to protect our network, other customers, and the billing of the targeted customer) is to blackhole them for a little while at the international gateway.

This resulted in an initial period of bad service while the attack started, and when the DDOS mitigation kicked in, the customer was able to see the national network just fine, but nothing internationally until the attack stopped.

This is just a part of being on the Internet, and it's made a lot worse if you have a static IP and host websites yourself on your BB connection.

We've given the customer a new IP and hope that it doesn't recur.

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.

1 | 2