jm3: Anyone else still down?

Yeah, we're still down. Lost connection entirely around 15:45 and haven't seen anything since. I do still have PPPoE and can trace as far as 103.139.184.34 - but nada after that.

I still have 2 locations in Akl and 1 in Masterton offline at the moment. PPPoE established and connected but no traffic. :)

@jm3 @Chippo the status update says if you have no connectivity to power down and restart your router. At the very least restart the PPP session and try that.

https://status.quic.nz/issues/6570e55a4a0ebd17a87dde15 

RunningMan:

 

@jm3 @Chippo the status update says if you have no connectivity to power down and restart your router. At the very least restart the PPP session and try that.

 

https://status.quic.nz/issues/6570e55a4a0ebd17a87dde15 

 

For anyone wondering, I have rebooted both the ONT and the RGW.

My bet, is that it's the big loop in their network tracing to my IP from the outside that's causing it.

8  as64073.auckland.megaport.com (43.243.22.105)  21.150 ms  37.164 ms  20.029 ms

9  bng1.quic.net.nz (103.139.184.101)  48.468 ms  38.995 ms  40.226 ms

10  as64073.auckland.megaport.com (43.243.22.105)  40.769 ms  18.618 ms  38.976 ms

11  bng1.quic.net.nz (103.139.184.101)  20.080 ms  39.599 ms  19.917 ms

12  as64073.auckland.megaport.com (43.243.22.105)  39.842 ms  19.359 ms  41.776 ms

13  bng1.quic.net.nz (103.139.184.101)  17.557 ms  46.691 ms  32.510 ms

14  as64073.auckland.megaport.com (43.243.22.105)  39.504 ms  37.798 ms  20.183 ms

...

All good here in AKL....   wife said Teams has been a ***** to use today but otherwise.....

danfaulknor:

 

We've had a couple of people sign up with us for temporary Port 2 connections to tide them over through the outages, happy to do more, with the assumption you go back to Quic when the issues are sorted. (I'm not here to kick Quic while they're down and poach customers!! And we're more expensive :) )

 

Just want to say thanks to Dan, he enabled Port 2 connections in two locations for me within 1.5 hours this afternoon.

I seem to be able to get around this issue (seemingly) by using Cloudflare WARP - which is changing my international routes.

Running speedtest.net from my Quic Walker (50/10) to a deliberately chosen very distant endpoint of Netprotect, Frankfurt, Germany (chosen at "random" because it's distant and we had sausages with dinner the other night). Can't even get 1Mbps down straight but via a WARP tunnel it's 40% line speed.

Results from test 1 / test 2 / test 3 (avg):

Straight: down 0.31 / 0.55 / 0.48 (0.44Mbps), up 8.04 / 6.94 / 8.57 (7.85Mpbs), ping ?ms / 420ms / 382ms (401ms)

CF: down 33.0 / 45.4 / 44.9 (41.1Mbps), up 9.62 / 9.11 / 8.16 (8.96Mpbs) , ping 322ms/ 398ms / 378ms (366ms)

(? = forgot to note the first ping down)
CF is Cloudflare Zero Trust with WARP (not WARP+). I happen to be testing this for work at the moment so it was a very handy tool to reach for. Hopefully the 1.1.1.1 with WARP app yields a similar result, I didn't test that.

Would be interested to know if this workaround works for anyone else!

(edit: added averages in brackets, edit 2: corrected line speed percentage)

mngm:

 

I still have 2 locations in Akl and 1 in Masterton offline at the moment. PPPoE established and connected but no traffic. :)

 

Yeah mines the same PPPoE been connecting successfully for a while but no traffic, I can only ping the quic gateway. I've powered down router and ont multiple times per the quic status page advice earlier in the day. I'm based in the Horowhenua/Manawatu.

My connection has just come back up.

@cjkbarnett Have you logged a fault in the Quic portal? If you haven't, then how will they know to investigate?

michaelmurfy:

@cjkbarnett Have you logged a fault in the Quic portal? If you haven't, then how will they know to investigate?

cjkbarnett: Not yet, was waiting to see if it resolved itself, but i guess not. Will lodge one now 😊

Always do this on the first instance. Pop in the notes it has been down since the maintenance and they'll take care of it. I think what basically has to happen is they force your connection down and when it reconnects things work again. Something around their automation. If it is this then it is a known bug they'll solve with the new network build.