Outage with no loss of sync

Recently I've been getting periods of a few hours where the router internet is steady orange, i.e. no internet, no loss of sync.

The timing of this one is interesting, just before 8am (BST), possibly suggests an engineer was working on something.

What is the most likely cause of this? FTTC cabinet issue? Sky internal systems issue? I can understand a sync-affecting issue being recurrent, but this is not that.

Text
1 23 45 6	2024-06-06 06:53:57 syslog: No lease renewal received 2024-06-06 06:53:59 syslog: ptm0.1 - WAN link DOWN.2024-06-06 06:53:59 syslog: DHCP lease expired from server. Connection DOWN. 2024-06-06 06:54:25 syslog: Voice IP Connection Down2024-06-06 06:54:25 syslog: WAN IPV6 DOWN 2024-06-06 06:54:27 syslog: Voice Disconnected

Text
1 2	2024-06-06 10:30:51 syslog: ptm0.1 - WAN link UP. 2024-06-06 10:30:51 syslog: Received valid DHCP lease from server.  Connection UP.

The timing of this one is interesting, just before 8am (BST), possibly suggests an engineer was working on something.

It doesn’t suggest that at all, in the main, they start at 8am, not before. And quite how an Openreach engineer could conjure a loss of session, but no loss of sync, is beyond me.

In reply to a post by Zarjaz:

And quite how an Openreach engineer could conjure a loss of session, but no loss of sync, is beyond me.

I never mentioned Openreach.

Planning engineer, mechanical engineer, aeronautical engineer, etc?

You didn’t mention Openreach but did quote FTTC, and do any other network operators use FTTC ?

Last time I saw something like this, it was a contractor doing roadworks, putting a JCB through the fibre cable between the cabinet and the exchange.

The copper lines stayed in sync, but everyone on that cabinet had no onward connectivity until the fibre cable was repaired

In reply to a post by Oliver341:

Recently I've been getting periods of a few hours where the router internet is steady orange, i.e. no internet, no loss of sync.

The timing of this one is interesting, just before 8am (BST), possibly suggests an engineer was working on something.

What is the most likely cause of this? FTTC cabinet issue? Sky internal systems issue? I can understand a sync-affecting issue being recurrent, but this is not that.

Text
1 23 45 6	2024-06-06 06:53:57 syslog: No lease renewal received 2024-06-06 06:53:59 syslog: ptm0.1 - WAN link DOWN.2024-06-06 06:53:59 syslog: DHCP lease expired from server. Connection DOWN. 2024-06-06 06:54:25 syslog: Voice IP Connection Down2024-06-06 06:54:25 syslog: WAN IPV6 DOWN 2024-06-06 06:54:27 syslog: Voice Disconnected

Text
1 2	2024-06-06 10:30:51 syslog: ptm0.1 - WAN link UP. 2024-06-06 10:30:51 syslog: Received valid DHCP lease from server.  Connection UP.

I had this happen to my FTTC circuit after the ISP had ruled out my modem / router being the cause they got open reach out He plugged in his tester ( exfo) got a sync like my modem, But couldn't test access to the net on his kit, so he brought a bt router in plugged that in same thing sync not PPPoE session so he went to the cab had to change the port twice to get a working port, sounds like this could be your issue

Could be that or the Port in the cab itself like the fault i experienced took several days to get it fixed due to zen wanting me to test with their loan router modem 1st

Edited by tommy45 (Thu 06-Jun-24 16:35:41)

In reply to a post by Iniltous:

You didn’t mention Openreach but did quote FTTC, and do any other network operators use FTTC ?

I mentioned FTTC since it gave some context to my issue, and I also suggested it could be an internal systems issue within Sky, e.g. Sky engineers or engineers contracted by Sky. The FTTC cab is only part of the journey, and I don't believe my post contradicted this fact.

Edited by Oliver341 (Thu 06-Jun-24 16:54:37)

In reply to a post by tommy45:

But couldn't test access to the net on his kit, so he brought a bt router in plugged that in same thing sync not PPPoE session so he went to the cab had to change the port twice to get a working port, sounds like this could be your issue

Interesting, so a fault like this can exist within the cab.