Core Link Failures Backbone

Timeline (most recent first)

• 2024-05-01
  10:52:00

  The other MAN-LON link is dead because that provider is dealing with a bug on their Juniper ACX platform.

  We've brought the link into service with the reduced MTU.

• 2024-05-01
  09:33:00

  The other MAN-LON link is dead because that provider is dealing with a bug on their Juniper ACX platform.

  We've confirmed that this link is working, but with 54 bytes shorter MTU than before. We're deploying some configuration changes to accommodate this.

• 2024-05-01
  08:15:00

  The other MAN-LON link is dead because that provider is dealing with a bug on their Juniper ACX platform.

  We've had an update from the de-prioritised link provider's NOC and are performing tests to determine whether their corrective changes have worked.

• 2024-05-01
  06:46:00

  The other MAN-LON link is dead because that provider is dealing with a bug on their Juniper ACX platform.

  Further tests show that this provider link is unhealthy. We have de-prioritised it once more, waiting for the provider's NOC to update us.

• 2024-05-01
  04:15:00

  One MAN-LON link is dead because of maintenance we were not told would affect this service.

  The "surprise maintenance" link has been stable for two hours now. We have backed-out our workaround.

• 2024-04-30
  23:26:00

  The other MAN-LON link is dead because that provider is dealing with a bug on their Juniper ACX platform.

  This provider link has come up.

• 2024-04-30
  23:13:00

  We've got a workaround in place.

• 2024-04-30
  22:49:00

  We're continuing to work on a workaround…

• 2024-04-30
  22:45:00

  One MAN-LON link is dead because of maintenance we were not told would affect this service.

  The other MAN-LON link is dead because that provider is dealing with a bug on their Juniper ACX platform.