Hey,
Ive been having an issue for a little while accessing both google and some of the youtube services
took a look into it this morning and it appears the routing inside Mynxnet/Vibe's network is a tad broken and is getting lost
the IP's ive found that are broken at present are:
103.13.116.151
103.13.116.157
103.13.116.181
I can happily ping them from other ISP's and a traceroute shows it stopping somewhere inside their network at the 4th hop
Tracing route to 103.13.116.181 over a maximum of 30 hops
1 1 ms 1 ms 1 ms 192.168.0.1
2 6 ms 6 ms 6 ms sub0.MDR-BNG1.layer2.co.nz [120.136.0.248]
3 6 ms 5 ms 4 ms 120.136.0.131
4 * * * Request timed out.
5 * * * Request timed out.
i contacted Mynxnet support and they came back saying that its not odd that the traceroute stops there and that the next hop probably just blocks pings...... which seemed odd to me but i thought ok, lets check that....
Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:
1 1 ms 1 ms 2 ms 192.168.0.1
2 5 ms 6 ms 11 ms sub0.MDR-BNG1.layer2.co.nz [120.136.0.248]
3 6 ms 5 ms 7 ms 120.136.0.131
4 34 ms 28 ms 28 ms xe-0-0-0-sky-cr1-google.layer2.co.nz [120.136.0.
118]
5 29 ms 29 ms 31 ms xe-1-1-26-sy3-tr1-google.layer2.co.nz [120.136.0
.119]
6 29 ms 28 ms 30 ms 216.239.40.223
7 28 ms 30 ms 28 ms 209.85.251.53
8 29 ms 29 ms 28 ms google-public-dns-a.google.com [8.8.8.8]
Trace complete.
so those then show that the 4th hop doesnt block pings so really suggests to me that xe-0-0-0-sky-cr1-google.layer2.co.nz [120.136.0.118]
seems to have something broken with its routing....
any suggestions? Mynxnet told me to check my internal network either way etc, which is just insulting seeing i included all the tests showing it was outside my network to begin with
Is anyone else having any issues like this on either Mynxnet/Vibe etc or that can give suggestions? im currently having to use a ssh tunnel to access google to a different isp at present which is a tad annoying :)
