Post-mortem: Loss of connectivity on 83.150.218.0/24
Duration: ~2 minutes (01:08 - 01:10)
Summary: A network loop was accidentally introduced by an external contractor during a maintenance intervention at approximately 01:10, causing a brief total loss of connectivity on the 83.150.218.0/24 & 217.145.72.0/24 subnet.
Timeline:
01:08 : Automatic alert triggered by Instatus monitoring, subnet 83.150.218.0/24 detected as down.
01:10 : Root cause identified and resolved: a network loop caused by an external contractor's intervention on-site.
01:15 : Incident officially marked as resolved after monitoring confirmed full recovery.
Root Cause: An external contractor performing on-site maintenance accidentally created a loopback on the network, which briefly turned our subnet into a very enthusiastic game of ping-pong with itself. Packets were having the time of their lives going in circles, unfortunately at the expense of actual connectivity.
Impact: Full outage on 83.150.218.0/24 for approximately 2 minutes. All services hosted on this subnet were temporarily unreachable.
Corrective actions:
Loop was removed and connectivity restored immediately upon detection.
Reminder sent to external contractors that cables, much like boomerangs, should not come back to where they started.
