AI Status Summary
Dev Seed - 103 Tcp TCP Unreachable 04 is currently down for a TCP monitor ([redacted]). The service is actively degraded and needs immediate attention. Over the last 6 hours, uptime was 0.00% across 50 checks, with 50 failed checks. Current check cadence is every 420 seconds with a 5000 ms timeout and a failure threshold of 3. The latest check completed at 2026-03-10 21:19:48Z, returning down in 0 ms. A downtime transition was last observed at 2026-03-10 15:22:47Z. A latency degradation trend was detected for the window 2026-03-10 13:21:21Z to 2026-03-10 14:21:21Z (score 3.30).
Generated locally/offline from recent checks, events, and monitor configuration.
Anomaly Signals
| Window (UTC) | Type | Score | Notes |
|---|---|---|---|
| 2026-03-10 13:21:21Z to 2026-03-10 14:21:21Z | LatencyDegradation | 3.30 | Development synthetic anomaly coverage: recent median 188 ms vs baseline 130 ms. |
Predictive Insights (ML.NET)
How to read this: risk percentages estimate probability, while confidence percentages estimate model certainty in the Early Warning and Incident Type labels.
Sparse-data fallback is active until this monitor has at least 500 checks and 5 incidents in the historical window.
heuristic fallback; checks=51; incidents=1; consecutiveFailures=51.
Service Graphs
Uptime Strip
0.00%Response Trend
Avg 0 msPeak 0 ms across 53 checks.
Event Activity (24h)
3 eventsRecent Checks
| Started | Status | Duration | Location | Error |
|---|---|---|---|---|
| 2026-03-10 21:19:48Z | Down | 0 ms | global 2 | Host could not be resolved. |
| 2026-03-10 21:12:48Z | Down | 0 ms | global 2 | Host could not be resolved. |
| 2026-03-10 21:05:48Z | Down | 0 ms | global 3 | Host could not be resolved. |
| 2026-03-10 20:58:47Z | Down | 0 ms | global 1 | Host could not be resolved. |
| 2026-03-10 20:51:47Z | Down | 0 ms | global 1 | Host could not be resolved. |
| 2026-03-10 20:44:47Z | Down | 0 ms | global 2 | Host could not be resolved. |
| 2026-03-10 20:37:46Z | Down | 0 ms | global 3 | Host could not be resolved. |
| 2026-03-10 20:30:46Z | Down | 0 ms | global 1 | Host could not be resolved. |
| 2026-03-10 20:23:45Z | Down | 0 ms | global 1 | Host could not be resolved. |
| 2026-03-10 20:16:45Z | Down | 0 ms | global 3 | Host could not be resolved. |
| 2026-03-10 20:09:45Z | Down | 0 ms | global 1 | Host could not be resolved. |
| 2026-03-10 20:02:49Z | Down | 0 ms | global 1 | Host could not be resolved. |
| 2026-03-10 19:55:49Z | Down | 0 ms | global 1 | Host could not be resolved. |
| 2026-03-10 19:48:48Z | Down | 0 ms | global 1 | Host could not be resolved. |
| 2026-03-10 19:41:48Z | Down | 0 ms | global 3 | Host could not be resolved. |
| 2026-03-10 19:34:48Z | Down | 0 ms | global 3 | Host could not be resolved. |
| 2026-03-10 19:27:48Z | Down | 0 ms | global 1 | Host could not be resolved. |
| 2026-03-10 19:20:47Z | Down | 0 ms | global 1 | Host could not be resolved. |
| 2026-03-10 19:13:47Z | Down | 0 ms | global 3 | Host could not be resolved. |
| 2026-03-10 19:06:46Z | Down | 0 ms | global 2 | Host could not be resolved. |
Recent Events
| Time | Event | From | To | Incident Summary |
|---|---|---|---|---|
| 2026-03-10 17:00:00Z | Predictive risk escalated | Down | Down | Predictive warning: elevated incident risk detected (1h 83.3%, 24h 100.0%). Likely next failure mode: Dns (70.0% confidence). Forecast uptime: next day 43.6%, next 7 days 34.6%. |
| 2026-03-10 15:22:47Z | Incident started | Unknown | Down | AI hints: Network 90%. - Approx duration: `Ongoing` - Likely cause: **Network transport or connectivity failures** - Suggested checks: Check connectivity path, packet loss, firewall rules, and upstream s |
| 2026-03-10 15:08:47Z | Investigating | Down | Unknown | - |