[WARNING] cache-service showing elevated errors

user-db config reverted to same state (no change). Cache continues evicting. Fallthrough load unchanged. Error rate unchanged.


[WARNING] pricing-service showing elevated errors

Action is a no-op. Circuit breaker already open. pricing-service memory leak continues. Worse outcome in remaining ticks.


network_partition fault signature detected

Restart merges cluster without flushing diverged keys. Last-write-wins means some keys have wrong values. Data inconsistency persists.


[WARNING] user-profile-service showing elevated errors

New replicas added to same broken weight table. Hot replica weight=4.0 unchanged. New replicas receive ~0% traffic. CPU still 0.87 on hot replica.


[WARNING] payment-service showing elevated errors

Service re-enters CrashLoopBackOff immediately. restart_count increments. Missing env var unchanged. Zero improvement.


[WARNING] payment-processor showing elevated errors

Service restarts and immediately re-enters same probe-fail loop. restart_count increments. Flap continues unchanged.


[WARNING] api-gateway showing elevated errors

auth-service restarts — it is a victim service. api-gateway pool exhaustion unchanged. api-gateway errors continue. Precision penalty + acted on adversarial.


[WARNING] db-proxy showing elevated errors

network_partition fault signature detected

auth-service restarts, errors clear momentarily, return within 2 ticks — db-proxy is still partitioned. Precision failure.


Temporarily absorbs api-gateway excess retries for ~3 ticks. auth error_rate drops to ~0.15. api-gateway retry count=10 unchanged. Errors return in 4 ticks.


More api-gateway instances each enforcing same misconfigured 100-rpm limit. 429 error rate unchanged. Backend services still idle.


[WARNING] notification-service showing elevated errors

user-service absorbs excess calls for 2-3 ticks. Error rate drops to ~0.08. notification-service retry bug persists. At tick+3, user-service fills up again. Errors return.


More DB replicas handle immediate stampede load. cache_hit_rate still 0.02-0.15. Next traffic spike triggers identical stampede. Root cause unaddressed.