Pingdom customer impact
External signalNo Pingdom checks were available in this window.
No active issue listed in this category.
Generated 2026-04-11 13:31 for 2026-04-04 07:00 to 2026-04-11 07:00 from Pingdom checks, Slack #_alerts_prod, and AWS SNS alerts.
Bottom line: application-level critical paths are present.
No Pingdom checks were available in this window.
No active issue listed in this category.
1 critical, 4 non-critical active item(s).
No AWS alarm emails were captured in this window.
No active issue listed in this category.
| Pingdom Check | Status | Events | Downtime | Last Seen | Likely Services | Correlated Evidence |
|---|
Pingdom rows show externally visible signal first. The correlated evidence column helps tie the failing check back to services, Slack alert families, or AWS alarms when those links exist.
This view attributes alerts to the workload or resource named in the alert text. Grafana, Loki, and Tempo are treated as observability components and are excluded when a more specific impacted target is also present.
| Impacted Service / Resource | Highest Severity | Count | Last Seen | Status | Top Alert Types | Discussion Signal | Latest Thread Note |
|---|---|---|---|---|---|---|---|
| core-grafana-80 | Critical | 2 | 2026-04-06 00:44 | Seen this week | TraefikServiceHighErrorRate (2) | None | No thread note |
| update-recurenta Grouped 7 variantsVariant mentions 56Active variants 7 | Warning | 56 | 2026-04-11 03:30 | Seen today | KubeJobFailed (44)KubeJobNotCompleted (12) | None | No thread note |
| ai-api | Warning | 3 | 2026-04-10 17:25 | Seen today | TraefikServiceHighLatency (3) | None | No thread note |
| metrics-server | Warning | 15 | 2026-04-06 17:34 | Seen this week | KubeAggregatedAPIDown (15) | None | No thread note |
| grafana | Warning | 6 | 2026-04-08 02:53 | Seen this week | KubeHpaMaxedOut (6) | None | No thread note |
| Alert | Severity | Count | Last Seen | Status | Threads | Top Impacted Services | Discussion Signal | Latest Thread Note |
|---|---|---|---|---|---|---|---|---|
| TraefikServiceHighErrorRate | Critical | 2 | 2026-04-06 00:44 | Seen this week | 0 | core-grafana-80 (2) | None | |
| KubeJobFailed | Warning | 44 | 2026-04-11 03:30 | Seen today | 0 | update-recurenta (44) | None | |
| TraefikServiceHighLatency | Warning | 3 | 2026-04-10 17:25 | Seen today | 0 | ai-api (3) | None | |
| KubeJobNotCompleted | Warning | 12 | 2026-04-09 03:20 | Recent (72h) | 0 | update-recurenta (12) | None | |
| KubeAggregatedAPIDown | Warning | 15 | 2026-04-06 17:34 | Seen this week | 0 | metrics-server (15) | None | |
| KubeHpaMaxedOut | Warning | 6 | 2026-04-08 02:53 | Seen this week | 0 | grafana (6) | None |
Status is heuristic. Slack rarely posts explicit resolutions, so “Seen today” or “Recent” means the alert family still appeared in production recently, not that it is definitely unresolved.
| AWS Alarm | Emails | ALARM | OK | State Flips | First Seen | Last Seen | Latest State | Status |
|---|
“Flapping, latest OK” means the most recent email was an OK, but the alarm toggled repeatedly and is still a reliability concern.
| Thread Date | Alert | Severity | Services | Signal | Key Notes |
|---|