Timeouts and Latency
184 incident problems that show up as “Timeouts and Latency”.
먼저 읽을 가이드
추천 문제
All problems (184)
NETWORK-038Spanning tree root shifts after switch replacement resets bridge priorityA replacement access switch joins successfully, but traffic starts taking the wrong path because the expected root priority was never re-applied.NetworkBeginner16 minFreeK8S-093Service selector is correct but EndpointSlice labels point the controller at the wrong shardThe Service definition looks fine, yet traffic still misses the intended backend because a generated EndpointSlice path is bound to an outdated label set.KubernetesIntermediate17 minFreeK8S-067StatefulSet ordinal DNS looks healthy but traffic is emptyPod names resolve as expected, yet clients get no working backend because the Service that should back ordinal DNS no longer selects the current pods.KubernetesIntermediate17 minFreeLINUX-027Tar backup excludes filesThe backup command seems valid, but quoting and wildcard expansion remove important files before archiving starts.LinuxBeginner13 minFreeK8S-027Secret key name changed but envFrom stays silentThe pod starts, but the expected environment variable never appears because the secret key no longer matches application expectations.KubernetesBeginner14 minFreeNETWORK-013IPv6 precedence slows connections for only some clientsIPv6 precedence slows connections for only some clients is a hands-on troubleshooting drill. A situation in a dual-stack environment where poor IPv6 path quality causes connection delays for only certain users. Firewall and Proxy Paths needs to be checked by narrowing scope, r...NetworkAdvanced26 minProNETWORK-133An IP SLA object track recovers immediately, but without hysteresis the WAN edge oscillates on every brief probe successThe failover design is correct in principle, yet recovery logic is too eager for the quality of the circuit.NetworkAdvanced17 minProNETWORK-096HSRP preempt delay is shorter than upstream route convergence and gateway flaps twice on recoveryFailover succeeds initially, but recovery creates another outage because the active gateway returns before its upstream dependencies are ready.NetworkAdvanced17 minProNETWORK-100Anycast DNS stays reachable but one site serves stale zone data after an AXFR policy changeThe service appears up globally, yet answers diverge because one anycast site stopped receiving zone transfers under the new policy.NetworkAdvanced18 minProNETWORK-086IP SLA tracks the wrong probe target and withdraws the primary path during a healthy application incidentFailover triggers exactly as configured, but the chosen probe target does not represent the real application health and causes an unnecessary routing shift.NetworkAdvanced18 minProSECURITY-094mTLS handshake succeeds to the proxy but upstream certificate pinning breaks only on one pathThe edge trust path looks correct, yet the service still fails because an internal hop enforces a different certificate identity contract.SecurityAdvanced18 minProSECURITY-099Security group egress hardening blocks the OCSP responder and only strict TLS clients fail validationCertificates are current, yet a subset of clients fail because the server-side environment can no longer complete revocation checks through the hardened egress policy.SecurityAdvanced18 minProCICD-068CloudFront keeps serving stale index.html after a blue-green cutoverThe new environment is healthy, but users still load references to the old asset set because cache invalidation and origin switch ordering were not coordinated.CI/CDAdvanced19 minProSECURITY-088Mutual TLS is enabled but the CRL endpoint is unreachable and only strict clients reject the serverCertificates are otherwise valid, but some clients fail because they require revocation checking and the CRL distribution path is no longer reachable.SecurityAdvanced19 minProNETWORK-093OSPF adjacency remains full but the summary route hides the more specific path needed for policy routingThe protocol is healthy, yet the application path fails because route summarization obscures the specific destination the policy logic depends on.NetworkAdvanced19 minProCICD-078Canary analysis passes against cached CDN responses instead of the origin traffic it was meant to judgeThe rollout looks healthy by metric, but the analysis is reading cache-hit behavior and not the new origin path that users will actually exercise after promotion.CI/CDAdvanced20 minProNETWORK-078Anycast service becomes unstable after an IGP cost change moves stateful clients across sitesThe anycast design still advertises correctly, but a cost change shifts clients to another site that does not hold the expected state continuity.NetworkAdvanced21 minProK8S-081Readiness passes but Envoy sidecar cannot reach the control plane after a trust bundle splitThe app container is healthy, yet traffic still fails because the sidecar lost trust in the mesh control plane after the certificate bundle changed unevenly.KubernetesAdvanced21 minProNETWORK-090EVPN MAC mobility is detected but the dampening timer keeps traffic pinned to the old leafThe control plane sees the move, yet data still breaks because mobility dampening delays acceptance of the new location longer than the workload can tolerate.NetworkAdvanced22 minProK8S-028Node drain hangs on long-lived connection podsMaintenance starts correctly, but eviction never finishes because connection draining and termination hooks take too long.KubernetesIntermediate22 minPro