Timeouts and Latency
184 incident problems that show up as “Timeouts and Latency”.
먼저 읽을 가이드
추천 문제
All problems (184)
NETWORK-369A QoS policy marks the right classes while tunnel overhead changed and one class now fragments or drops before the shaped queue ever sees it during a staged decommissionClassification is correct, but the packet size math no longer fits the path. The service still works through the primary path, but one dependency only fails when the old component is finally drained away.NetworkAdvanced17 minProNETWORK-141A route-policy preserves MED during normal operation, but a maintenance template strips it on the backup edge and inbound traffic never returns after failoverPaths exist both ways, yet partner preference signals vanish only on the standby path.NetworkAdvanced17 minProNETWORK-129BFD minimum receive timers do not align between vendors, and only one side believes the session is stableBoth devices show partial liveliness, but the negotiated timing reality differs enough to keep the path flapping.NetworkAdvanced17 minProNETWORK-115BGP confederation sub-AS policy strips the community needed to choose the correct exit pathThe routes arrive everywhere, but exit selection is wrong because a transit policy removed the signal the edge uses for preference.NetworkAdvanced17 minProNETWORK-111Consistent hashing is disabled during a line-card replacement and long-lived sessions reset across ECMP membersRedundancy remains, but user sessions drop because path stickiness disappeared during the hardware swap window.NetworkAdvanced17 minProNETWORK-137VRRP advertisements pass, but the mixed-vendor pair uses different packet version expectations and both routers think they are masterLayer-3 reachability exists, yet first-hop symmetry collapses because redundancy control messages are interpreted differently.NetworkAdvanced17 minProNETWORK-234A BGP session remains established while graceful restart keeps stale forwarding alive longer than the outage can tolerate during a failover rehearsalControl-plane continuity looks stable while data-plane truth is already different. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.NetworkAdvanced18 minProNETWORK-204A failover signal tracks device liveness while the service behind it is already gone during a failover rehearsalThe route follows a reachable box instead of the actual service dependency. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.NetworkAdvanced18 minProNETWORK-306A QoS trust boundary changed on one edge while policy-map assumptions on the WAN handoff still reflect the old marking point during a failover rehearsalMarking is correct in one segment and wrong by the time traffic reaches the WAN policy decision. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.NetworkAdvanced18 minProNETWORK-162A standby edge keeps routes while losing the preference signal that made inbound traffic behave correctly during a failover rehearsalFailover succeeds functionally and inbound policy intent disappears on the alternate path. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.NetworkAdvanced18 minProNETWORK-149An EVPN anycast gateway MAC is correct on both leaves, but one site keeps an older virtual router MAC and hosts split traffic unpredictably after maintenanceGateway abstraction exists, yet endpoint behavior diverges because one site's virtual identity is stale.NetworkAdvanced18 minProK8S-312An externalTrafficPolicy Local design is correctAn externalTrafficPolicy Local design is correct focuses on cluster-networking-and-service-discovery and asks the reader to isolate Timeouts and Latency in AWS. 실무에서는 timeouts-and-latency 증상만 보고 Pod 하나에 매달리지 말고 이벤트, 이전 로그, Service/Endpoint, 최근 배포 변경을 한 번에 묶어 보는 편이 오진을 줄입니다.KubernetesAdvanced18 minProNETWORK-091BGP community is set on ingress but removed by a route-map sequence later in the same policy chainThe intended tag exists briefly, yet traffic engineering never works because a later policy step strips it before export.NetworkAdvanced18 minProNETWORK-132GRE keepalives remain up, but an underlay ACL blocks the recursive route to the tunnel destination during WAN failoverTunnel health appears good until the underlay path changes, exposing a missing control route allowance.NetworkAdvanced18 minProK8S-091Mutating webhook times out only on large Pod specsSmall workloads admit fine, but larger ones fail because the webhook path includes a proxy with a body-size setting lower than the API server request.KubernetesAdvanced18 minProNETWORK-076Policy-based routing sends health-check probes into a blackhole next hopNormal application flows look fine, but the service stays unhealthy because policy routing treats the health-check source differently and steers it to a dead path.NetworkAdvanced18 minProK8S-151The ingress controller trusts X-Forwarded-Proto from the external load balancer, but an internal hop rewrites it and secure redirects begin loopingTLS is terminated correctly, yet downstream protocol awareness is now inconsistent across hops.KubernetesAdvanced18 minProNETWORK-117Tunnel MTU is adjusted on GRE over IPsec, but the underlay policer still drops fragments above the old profileThe logical tunnel is tuned correctly, yet the carrier-facing policy continues to enforce a smaller assumption and silently drops larger traffic.NetworkAdvanced18 minProNETWORK-113A campus overlay fabric duplicates the anycast gateway across sites with overlapping VNIs and east-west traffic misroutes intermittentlyLocal routing works most of the time, but some flows take the wrong site path because fabric identifiers are no longer unique per domain.NetworkAdvanced19 minProNETWORK-210A shared gateway keeps the same IP while one site drifts to a different virtual identity during a failover rehearsalDependent controls stay anchored on an identity the network no longer presents consistently. Normal traffic masked the issue until the standby or alternate path became active under rehearsal conditions.NetworkAdvanced19 minPro