| # | Time (UTC) | Symptoms | Diagnosis | Action | Outcome | OK? |
|---|
| 4266 | 2026-06-18T08:28:20 | high_latency_critical | Similar past incidents [semantic]: id=4151 sim=0.939, id=4114 sim=0.939, id=4136… | alert | rejected_by_human | ✗ |
| 4265 | 2026-06-18T08:26:52 | high_latency_critical | Similar past incidents [semantic]: id=4091 sim=0.791, id=4094 sim=0.788, id=4088… | alert | rejected_by_human | ✗ |
| 4264 | 2026-06-18T08:26:43 | high_latency_critical | Similar past incidents [semantic]: id=4091 sim=0.791, id=4094 sim=0.788, id=4088… | alert | rejected_by_human | ✗ |
| 4263 | 2026-06-18T08:20:44 | high_latency_critical | Similar past incidents [semantic]: id=4091 sim=0.791, id=4094 sim=0.788, id=4088… | alert | alerted | ✗ |
| 4262 | 2026-06-18T08:18:00 | high_latency_critical | Similar past incidents [semantic]: id=4091 sim=0.791, id=4094 sim=0.788, id=4088… | alert | alerted | ✗ |
| 4261 | 2026-06-18T08:16:42 | high_latency_critical | Similar past incidents [semantic]: id=4091 sim=0.789, id=4088 sim=0.786, id=4094… | alert | alerted | ✗ |
| 4260 | 2026-06-14T15:39:42 | high_latency_critical | Service experiencing critical latency due to overload but remains reachable with… | alert | alerted | ✗ |
| 4259 | 2026-06-14T15:29:36 | high_latency_critical | Service experiencing critical latency due to overload but remains reachable with… | alert | alerted | ✗ |
| 4258 | 2026-06-14T12:08:32 | service_unreachable | Service unreachable with zero RSS and max latency, matching historical safe-mode… | alert | alerted | ✗ |
| 4257 | 2026-06-14T12:06:55 | high_latency_critical | Service experiencing critical latency due to overload but remains reachable with… | alert | alerted | ✗ |