Get webhook notifications whenever Network & Infrastructure creates an incident, updates an incident, resolves an incident or changes a component status.
We are experiencing some loss with the device. We are investigating currently.
Update(s):
Date: 2018-08-17 03:39:48 UTC We've currently re-shut the port with CRC causing issue and check with our provider.
Date: 2018-08-17 03:17:36 UTC We currently experienced some loss towards this equipment. We are investigating further.
Date: 2018-08-17 03:03:57 UTC The fiber and SFP modules have been replaced. There is no longer CRC on the interface.
Date: 2018-08-17 00:17:22 UTC The port still currently has CRC. We will now re-isolate it and check the fiber and SFP modules.
Date: 2018-08-17 00:10:16 UTC We've replaced some fiber between the two devices. We will now deisolate to check for CRC.
Date: 2018-08-16 21:56:10 UTC We are currently in the process of replacing the fiber between the two devices.
Date: 2018-08-16 18:10:24 UTC We put it back online but immediately seen CRC and decided to re-isolate it.
Date: 2018-08-16 18:07:52 UTC We replaced the SFP and now the signal is much better than before and the link is stable. We will put it back in production.
Date: 2018-08-16 17:33:00 UTC The uplinks between sbg2-106a-n56-vrack <> sbg-g5-a9 has started to flap quickly and we had to isolate the link to force the traffic going on the B side. Everything is back to normal, we seen 10min~ of instability.
Posted Aug 16, 2018 - 17:27 UTC
This incident affected: Infrastructure || SBG (SBG1, SBG3, SBG4).