Dev Seed - 136 Tcp TCP Unreachable 03
Powered by AILive updates on
AI Status Summary
Dev Seed - 136 Tcp TCP Unreachable 03 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 36 checks, with 36 failed checks. Current check cadence is every 300 seconds with a 5000 ms timeout and a failure threshold of 3. The latest check completed at 2026-03-10 00:12:23Z, returning down in 0 ms. A downtime transition was last observed at 2026-03-09 21:27:25Z.
Generated locally/offline from recent checks, events, and monitor configuration.
Anomaly Signals
No recent latency anomalies were detected.
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=27; incidents=1; consecutiveFailures=27.
Service Graphs
Uptime Strip
0.00%Response Trend
Avg 0 msPeak 0 ms across 36 checks.
Event Activity (24h)
3 eventsRecent Checks
| Started | Status | Duration | Location | Error |
|---|---|---|---|---|
| 2026-03-10 00:12:23Z | Down | 0 ms | global 3 | Host could not be resolved. |
| 2026-03-10 00:07:23Z | Down | 0 ms | global 3 | Host could not be resolved. |
| 2026-03-10 00:02:23Z | Down | 0 ms | global 2 | Host could not be resolved. |
| 2026-03-09 23:57:22Z | Down | 0 ms | global 2 | Host could not be resolved. |
| 2026-03-09 23:52:22Z | Down | 0 ms | global 1 | Host could not be resolved. |
| 2026-03-09 23:47:22Z | Down | 0 ms | global 3 | Host could not be resolved. |
| 2026-03-09 23:42:26Z | Down | 0 ms | global 2 | Host could not be resolved. |
| 2026-03-09 23:37:26Z | Down | 0 ms | global 1 | Host could not be resolved. |
| 2026-03-09 23:32:26Z | Down | 0 ms | global 3 | Host could not be resolved. |
| 2026-03-09 23:27:25Z | Down | 0 ms | global 1 | Host could not be resolved. |
| 2026-03-09 23:22:24Z | Down | 0 ms | global 2 | Host could not be resolved. |
| 2026-03-09 23:17:23Z | Down | 0 ms | global 2 | Host could not be resolved. |
| 2026-03-09 23:12:23Z | Down | 0 ms | global 3 | Host could not be resolved. |
| 2026-03-09 23:07:22Z | Down | 0 ms | global 3 | Host could not be resolved. |
| 2026-03-09 23:02:22Z | Down | 0 ms | global 1 | Host could not be resolved. |
| 2026-03-09 22:57:22Z | Down | 0 ms | global 3 | Host could not be resolved. |
| 2026-03-09 22:52:22Z | Down | 0 ms | global 2 | Host could not be resolved. |
| 2026-03-09 22:47:26Z | Down | 0 ms | global 1 | Host could not be resolved. |
| 2026-03-09 22:42:26Z | Down | 0 ms | global 2 | Host could not be resolved. |
| 2026-03-09 22:37:25Z | Down | 0 ms | global 2 | Host could not be resolved. |
Recent Events
| Time | Event | From | To | Incident Summary |
|---|---|---|---|---|
| 2026-03-09 22: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-09 21:27:25Z | 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-09 21:17:25Z | Investigating | Down | Unknown | - |