Does anyone have issue with Orcon Gigabit Fibre this morning?

I live in Kapiti, this morning my lady at home reported our Internet was down. The interesting part is when I got to the office at Wellington CBD, I can still VPN back home, and my Ubuntu server is happily updating packages just fine.

This is some pings/traceroutes I've been looking at:

Pinging ubuntu's NZ mirror: Success

$ ping nz.archive.ubuntu.com
PING mirror.fsmg.org.nz (163.7.134.112) 56(84) bytes of data.
64 bytes from 163.7.134.112 (163.7.134.112): icmp_seq=1 ttl=59 time=1.88 ms
64 bytes from 163.7.134.112 (163.7.134.112): icmp_seq=2 ttl=59 time=1.76 ms
64 bytes from 163.7.134.112 (163.7.134.112): icmp_seq=3 ttl=59 time=1.79 ms

Tracerouting ubuntu's NZ mirror: Success

$ traceroute nz.archive.ubuntu.com

traceroute to nz.archive.ubuntu.com (163.7.134.112), 30 hops max, 60 byte packets
 1  setup.ubnt.com (192.168.11.1)  0.444 ms  0.578 ms  0.549 ms
 2  * * *
 3  dynamic-cpe-pool.callplus.net.nz (203.184.5.249)  4.246 ms  4.454 ms  4.294 ms
 4  op.mdr-cre1.orcon.net.nz (101.98.5.17)  5.247 ms  5.116 ms  5.223 ms
 5  163.7.134.122 (163.7.134.122)  6.781 ms  5.244 ms  6.181 ms

Pinging www.google.com: Timeout

Tracerouting www.google.com: Timeout

$ traceroute www.google.com
traceroute to www.google.com (172.217.167.100), 30 hops max, 60 byte packets
 1  setup.ubnt.com (192.168.11.1)  0.397 ms  0.499 ms  0.615 ms
 2  * * *
 3  * * *
 4  * * *

Pinging www.trademe.co.nz: Timeout

Tracerouting www.trademe.co.nz: Timeout

$ traceroute www.trademe.co.nz
traceroute to www.trademe.co.nz (202.162.73.2), 30 hops max, 60 byte packets
 1  setup.ubnt.com (192.168.11.1)  0.407 ms  0.487 ms  0.610 ms
 2  * * *
 3  * * *
 4  * * *

I think my access is restricted to Wellington region only. I called Orcon's tech support, the guy thought it was just my router and insisted me to use Orcon's one, otherwise he didn't know what happened.

I mean in theory I could have put some obscure firewall rules to block some but not all of NZ's IPs, but I hadn't touched my router for a while and unless it has been hacked and made to do these weird things, I still think it's probably more a ISP's routing problem. Anyone has any insight?