AI Status Summary
Dev Seed - 151 Cron Cron Invalid 04 is currently down for a CRON monitor ([redacted]). The service is actively degraded and needs immediate attention. Over the last 6 hours, uptime was 0.00% across 70 checks, with 70 failed checks. Current check cadence is every 300 seconds with a 2000 ms timeout and a failure threshold of 3. The latest check completed at 2026-03-10 21:23:38Z, returning down in 0 ms. A downtime transition was last observed at 2026-03-10 15:18:37Z. A latency spike was detected for the window 2026-03-10 13:42:21Z to 2026-03-10 14:42:21Z (score 5.40).
Generated locally/offline from recent checks, events, and monitor configuration.
Anomaly Signals
| Window (UTC) | Type | Score | Notes |
|---|---|---|---|
| 2026-03-10 13:42:21Z to 2026-03-10 14:42:21Z | LatencySpike | 5.40 | Development synthetic anomaly coverage: recent median 132 ms vs baseline 60 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=71; incidents=1; consecutiveFailures=71.
Service Graphs
Uptime Strip
0.00%Response Trend
Avg 0 msPeak 0 ms across 74 checks.
Event Activity (24h)
3 eventsRecent Checks
| Started | Status | Duration | Location | Error |
|---|---|---|---|---|
| 2026-03-10 21:23:38Z | Down | 0 ms | global 3 | CRON expression must have 5 or 6 fields. |
| 2026-03-10 21:18:38Z | Down | 0 ms | global 1 | CRON expression must have 5 or 6 fields. |
| 2026-03-10 21:13:38Z | Down | 0 ms | global 3 | CRON expression must have 5 or 6 fields. |
| 2026-03-10 21:08:38Z | Down | 0 ms | global 1 | CRON expression must have 5 or 6 fields. |
| 2026-03-10 21:03:37Z | Down | 0 ms | global 2 | CRON expression must have 5 or 6 fields. |
| 2026-03-10 20:58:37Z | Down | 0 ms | global 1 | CRON expression must have 5 or 6 fields. |
| 2026-03-10 20:53:37Z | Down | 0 ms | global 2 | CRON expression must have 5 or 6 fields. |
| 2026-03-10 20:48:37Z | Down | 0 ms | global 2 | CRON expression must have 5 or 6 fields. |
| 2026-03-10 20:43:37Z | Down | 0 ms | global 1 | CRON expression must have 5 or 6 fields. |
| 2026-03-10 20:38:41Z | Down | 0 ms | global 1 | CRON expression must have 5 or 6 fields. |
| 2026-03-10 20:33:41Z | Down | 0 ms | global 3 | CRON expression must have 5 or 6 fields. |
| 2026-03-10 20:28:41Z | Down | 0 ms | global 3 | CRON expression must have 5 or 6 fields. |
| 2026-03-10 20:23:40Z | Down | 0 ms | global 2 | CRON expression must have 5 or 6 fields. |
| 2026-03-10 20:18:40Z | Down | 0 ms | global 3 | CRON expression must have 5 or 6 fields. |
| 2026-03-10 20:13:40Z | Down | 0 ms | global 1 | CRON expression must have 5 or 6 fields. |
| 2026-03-10 20:08:40Z | Down | 0 ms | global 3 | CRON expression must have 5 or 6 fields. |
| 2026-03-10 20:03:39Z | Down | 0 ms | global 3 | CRON expression must have 5 or 6 fields. |
| 2026-03-10 19:58:39Z | Down | 0 ms | global 3 | CRON expression must have 5 or 6 fields. |
| 2026-03-10 19:53:39Z | Down | 0 ms | global 3 | CRON expression must have 5 or 6 fields. |
| 2026-03-10 19:48:38Z | Down | 0 ms | global 2 | CRON expression must have 5 or 6 fields. |
Recent Events
| Time | Event | From | To | Incident Summary |
|---|---|---|---|---|
| 2026-03-10 16:00:00Z | Predictive risk escalated | Down | Down | Predictive warning: elevated incident risk detected (1h 83.3%, 24h 100.0%). Likely next failure mode: Timeout (70.0% confidence). Forecast uptime: next day 43.6%, next 7 days 34.6% |
| 2026-03-10 15:18:37Z | Incident started | Unknown | Down | AI hints: Unknown 35%. - Approx duration: `Ongoing` - Likely cause: **Transient or mixed failure pattern** - Suggested checks: Review recent check errors and compare with monitor change history. |
| 2026-03-10 15:08:37Z | Investigating | Down | Unknown | - |