* Originally in NZ_FIDONET
* Crossposted in FN_SYSOP

+++++
There is a submarine fiber cut (PPC-1) which started on the 7th of February.

Please allow IP transit providers and peering partners to reroute traffic over Japan and Southern Cross.


News reference: http://www.theregister.co.uk/2016/02/07/cable_cut_lops_terabits_off_australias_net_connectivity/

Submarine cable cut lops Terabits off Australia's data bridge
| The PPC-1 cable us out of service until March ... if a ship to fix it can be found |

Another of the submarine cables connecting Australia to the world, for data, has broken.

PPC-1, which stretches from Sydney to Guam and has 1.92 terabits per second capacity, is out of service until at least March 7.

TPG's announcement says the fault is around 4,590 km from the cable's Guam landing, which means it's around 3,000 metres below the surface.

The fault notice says engineers first logged a report that “alarms indicated that a submarine line card had lost its payload”, and the company is trying to establish when a repair ship can be dispatched to the location.

In the meantime, traffic is using alternate routes including the Australia-Japan Cable and Southern Cross.

Last year, the SeaMeWe-3 cable which runs from Perth to Asia via Indonesia suffered multiple outages.

The situation is complicated by the Basslink cable outage. As Vulture South reported last week, a repairing the electrical cable connecting Tasmania to the mainland is going to necessitate a visit by cable repair ship the Ile de Re, because Basslink's communication fibre is going to be cut during the operation.

The Ile de Re would be the default repair ship for PPC-1, so there's likely to be a lot of messages flying around working out whether it can fit a trip to Guam into its schedule, or if another ship has to be called in.

The cut also represents a challenge to PPC-1's owner, TPG, as the telco and ISP has recently offered vastly increased download allowances for its customers. That's the kind of thing an integrated carrier that owns a submarine cable can do. TPG's investors will be hoping its also invested in lots of local caching and contracts for backup bandwidth, as if it hasn't the cost of landing data promised to users will soon stack up. ®
+++++

Will this affect New Zealand too?


--- FMail-W32-1.69.12.145-B20160204
* Origin: FMail development HQ (2:280/464)

On 02/08/16, Wilfred van Velzen pondered and said...

* Originally in NZ_FIDONET
* Crossposted in FN_SYSOP

+++++
There is a submarine fiber cut (PPC-1) which started on the 7th of February.

Please allow IP transit providers and peering partners to reroute
traffic over Japan and Southern Cross.

I bet thats why my Netfix got a little worse today!

--- Mystic BBS v1.11 (Windows)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (3:770/100)

Hi Paul,

On 2016-02-08 22:54:21, you wrote to me:

+++++
There is a submarine fiber cut (PPC-1) which started on the 7th of
February.

Please allow IP transit providers and peering partners to reroute
traffic over Japan and Southern Cross.

I bet thats why my Netfix got a little worse today!

It wouldn't surprise me. ;)

Bye, Wilfred.

--- FMail-W32-1.69.12.145-B20160204
* Origin: FMail development HQ (2:280/464)

Hi Wilfred

If you ping agency.fsxnet.nz what do you see?

You could also try f101.n1.z21.fsxnet.nz

Best, Paul

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)

Hi Paul.

17 Jul 18 21:21, you wrote to Wilfred van Velzen:

Hi Wilfred

Hmm.. ;)

If you ping agency.fsxnet.nz what do you see?

tommi@pin:~$ ping -c5 agency.fsxnet.nz
PING agency.fsxnet.nz(2001:470:d:123::50 (2001:470:d:123::50)) 56 data bytes
64 bytes from 2001:470:d:123::50 (2001:470:d:123::50): icmp_seq=1 ttl=53 time=348 ms
64 bytes from 2001:470:d:123::50 (2001:470:d:123::50): icmp_seq=2 ttl=53 time=348 ms
64 bytes from 2001:470:d:123::50 (2001:470:d:123::50): icmp_seq=3 ttl=53 time=348 ms
64 bytes from 2001:470:d:123::50 (2001:470:d:123::50): icmp_seq=4 ttl=53 time=352 ms
64 bytes from 2001:470:d:123::50 (2001:470:d:123::50): icmp_seq=5 ttl=53 time=347 ms

-+- agency.fsxnet.nz ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4004ms
rtt min/avg/max/mdev = 347.572/349.118/352.716/1.979 ms

You could also try f101.n1.z21.fsxnet.nz

tommi@pin:~$ ping -c5 f101.n1.z21.fsxnet.nz
PING ipv4.agency.bbs.nz (219.89.83.33) 56(84) bytes of data.
64 bytes from 219-89-83-33.adsl.xtra.co.nz (219.89.83.33): icmp_seq=1 ttl=47 time=347 ms
64 bytes from 219-89-83-33.adsl.xtra.co.nz (219.89.83.33): icmp_seq=2 ttl=47 time=346 ms
64 bytes from 219-89-83-33.adsl.xtra.co.nz (219.89.83.33): icmp_seq=3 ttl=47 time=347 ms
64 bytes from 219-89-83-33.adsl.xtra.co.nz (219.89.83.33): icmp_seq=4 ttl=47 time=347 ms
64 bytes from 219-89-83-33.adsl.xtra.co.nz (219.89.83.33): icmp_seq=5 ttl=47 time=349 ms

-+- ipv4.agency.bbs.nz ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4004ms
rtt min/avg/max/mdev = 346.927/347.776/349.709/1.071 ms



'Tommi

---
* Origin: ================================== (2:221/360.10)

Hi Paul,

On 2018-07-17 21:21:46, you wrote to me:

@MSGID: 3:770/100 04132045
@REPLY: 2:280/464 56b86d60
@TID: Mystic BBS 1.12 A39
@TZUTC: 1200
Hi Wilfred

If you ping agency.fsxnet.nz what do you see?

PING agency.fsxnet.nz (219.89.83.33) 56(84) bytes of data.
64 bytes from 219-89-83-33.adsl.xtra.co.nz (219.89.83.33): icmp_seq=1 ttl=45 time=297 ms
64 bytes from 219-89-83-33.adsl.xtra.co.nz (219.89.83.33): icmp_seq=2 ttl=45 time=297 ms
64 bytes from 219-89-83-33.adsl.xtra.co.nz (219.89.83.33): icmp_seq=3 ttl=45 time=296 ms
64 bytes from 219-89-83-33.adsl.xtra.co.nz (219.89.83.33): icmp_seq=4 ttl=45 time=296 ms
64 bytes from 219-89-83-33.adsl.xtra.co.nz (219.89.83.33): icmp_seq=5 ttl=45 time=298 ms

-+- agency.fsxnet.nz ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4006ms
rtt min/avg/max/mdev = 296.743/297.405/298.289/0.900 ms

You could also try f101.n1.z21.fsxnet.nz

I could, but I didn't... ;)

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

Hi Tommi,

On 2018-07-17 13:59:06, you wrote to Paul Hayton:

If you ping agency.fsxnet.nz what do you see?

tommi@pin:~$ ping -c5 agency.fsxnet.nz

-+- agency.fsxnet.nz ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4004ms
rtt min/avg/max/mdev = 347.572/349.118/352.716/1.979 ms

That's even slower then my test...

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

Hi Wilfred

If you ping agency.fsxnet.nz what do you see?

You could also try f101.n1.z21.fsxnet.nz

C:\Users\Nick>ping agency.fsxnet.nz

Pinging agency.fsxnet.nz [2001:470:d:123::50] with 32 bytes of data:
Reply from 2001:470:d:123::50: time=360ms
Reply from 2001:470:d:123::50: time=360ms
Reply from 2001:470:d:123::50: time=360ms
Reply from 2001:470:d:123::50: time=360ms

Ping statistics for 2001:470:d:123::50:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 360ms, Maximum = 360ms, Average = 360ms

C:\Users\Nick>ping agency.fsxnet.nz -4

Pinging agency.fsxnet.nz [219.89.83.33] with 32 bytes of data:
Reply from 219.89.83.33: bytes=32 time=37ms TTL=55
Reply from 219.89.83.33: bytes=32 time=37ms TTL=55
Reply from 219.89.83.33: bytes=32 time=37ms TTL=55
Reply from 219.89.83.33: bytes=32 time=37ms TTL=55

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

C:\Users\Nick>ping f101.n1.z21.fsxnet.nz

Pinging ipv4.agency.bbs.nz [219.89.83.33] with 32 bytes of data:
Reply from 219.89.83.33: bytes=32 time=37ms TTL=55
Reply from 219.89.83.33: bytes=32 time=38ms TTL=55
Reply from 219.89.83.33: bytes=32 time=37ms TTL=55
Reply from 219.89.83.33: bytes=32 time=37ms TTL=55

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

Nick

--- SLMAIL v5.1 (#SLO409KEDG15G098)
* Origin: The Trashcan - The BEST rubbish * bbs.thenet.gen.nz (3:772/210)

On 07/17/18, Paul Hayton pondered and said...

If you ping agency.fsxnet.nz what do you see?
You could also try f101.n1.z21.fsxnet.nz

Thanks Wilfred, Tommi and Nick - looks like so far so good in my DNS / domain name setup.

Best, Paul

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)

Hello Paul!

18 Jul 2018 12:26, Paul Hayton wrote to All:

If you ping agency.fsxnet.nz what do you see?
You could also try f101.n1.z21.fsxnet.nz

Thanks Wilfred, Tommi and Nick - looks like so far so good in my DNS / domain name setup.

its la la la :)


Regards Benny

... there can only be one way of life, and it works :)

--- Msged/LNX 6.1.2 (Linux/4.18.5-gentoo (x86_64))
* Origin: I will always keep a PC running CPM 3.0 (2:230/0)

On 09/07/18, Benny Pedersen pondered and said...

domain name setup.

its la la la :)

its a broadway musical?

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)

Hello Paul!

08 Sep 2018 22:32, Paul Hayton wrote to Benny Pedersen:

domain name setup.

its la la la :)

its a broadway musical?

vengaboys


Regards Benny

... there can only be one way of life, and it works :)

--- Msged/LNX 6.1.2 (Linux/4.18.7-gentoo (x86_64))
* Origin: I will always keep a PC running CPM 3.0 (2:230/0)