Incident Library
Applied filters SymptomPacket lossFactorGray failureClear allEvery case under the filters, with no sentence; newest first.
Suggested filters Search, and the values found in your words appear here.

Graph

  • Root cause
  • Component
  • Symptom
  • Contributing factor
  • Case

Cases1 case

1 to 1 of 1

  1. Symptoms

    On Friday 17 November 2023, the local government administrative computer services in Korea stopped working, and the Government24 service of the National Information Resources Service was down until the next morning.

    Root cause
    Component
    Contributing factor
    Remediation
    • Replaced the two malfunctioning L4 devices with higher-performance devices, tested them and resumed Government24 at 09:00 on 18 November
    • Moved the connection on the defective port of the Daejeon center router to another port at 07:00 on 19 November
    • Swapped out the module of the router that had the fault
    Action items
    • Inspect all old equipment that may have similar port defects
    • Revise the incident handling manual so the public is told about an outage quickly
    • Announce the status of service recovery quickly through various means
    • Build integrated monitoring of critical service systems and related equipment to catch signs of failure early
    • Form a standing incident response team to send into major outages
    • Prepare administrative measures and a response manual so administrative services can still be provided when core digital government services stop
    • Name a paralysis of the national computer network as a type of disaster and accident, managed from prevention to recovery
    • Build a government-wide crisis response system for linked information systems and strengthen the control tower for outage prevention and response
    • Improve how public IT projects are run and managed, replace hardware and software past their service life quickly and make project pricing realistic
    • Reduce the reliance on outsourcing for developing and operating information systems and bring digital talent into government
    • Review the redundancy, recovery systems and network configuration of the systems in the National Information Resources Service, and its organisation
    • Work with manufacturers on a way to find and monitor failures of internal parts earlier
    Lessons

    The team said that hardware faults like this defective port also happen in the private sector, and that failures of parts inside a device are hard to catch in advance with basic monitoring and daily visual checks. Redundancy did not help because it takes over only when a whole device stops working, and a module that failed only in part did not make the device count as abnormal. The impact was wide because the defective port carried traffic for all the services.

Check your cluster for this

This case involves NIC, cable and switch port link. kubegap audits a Kubernetes cluster for gaps like these, read-only, from Claude Code or Codex; its checks cite public reports like the ones in this library.

By root cause1