AI Status Summary
Dev Seed - 081 Http HTTP reuters.com is currently down for an HTTP endpoint (https://reuters.com/). The service is actively degraded and needs immediate attention. Over the last 6 hours, uptime was 0.00% across 87 checks, with 87 failed checks. Current check cadence is every 240 seconds with a 10000 ms timeout and a failure threshold of 3. The latest check completed at 2026-03-10 21:21:15Z, returning down in 575 ms. A downtime transition was last observed at 2026-03-10 15:17:18Z. A latency spike was detected for the window 2026-03-10 13:20:16Z to 2026-03-10 14:20:16Z (score 5.40).
Generated locally/offline from recent checks, events, and monitor configuration.
Anomaly Signals
| Window (UTC) | Type | Score | Notes |
|---|---|---|---|
| 2026-03-10 13:20:16Z to 2026-03-10 14:20:16Z | LatencySpike | 5.40 | Development synthetic anomaly coverage: recent median 396 ms vs baseline 180 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=88; incidents=1; consecutiveFailures=88.
Service Graphs
Uptime Strip
0.00%Response Trend
Avg 575 msPeak 770 ms across 91 checks.
Event Activity (24h)
3 eventsRecent Checks
| Started | Status | Duration | Code | Location | Cert Expires | Error |
|---|---|---|---|---|---|---|
| 2026-03-10 21:21:15Z | Down | 575 ms | 401 | global 3 | 2026-06-10 23:59:59Z | HTTP 401 |
| 2026-03-10 21:17:14Z | Down | 590 ms | 401 | global 2 | 2026-06-10 23:59:59Z | HTTP 401 |
| 2026-03-10 21:13:14Z | Down | 555 ms | 401 | global 3 | 2026-06-10 23:59:59Z | HTTP 401 |
| 2026-03-10 21:09:13Z | Down | 566 ms | 401 | global 3 | 2026-06-10 23:59:59Z | HTTP 401 |
| 2026-03-10 21:05:13Z | Down | 547 ms | 401 | global 2 | 2026-06-10 23:59:59Z | HTTP 401 |
| 2026-03-10 21:01:18Z | Down | 562 ms | 401 | global 3 | 2026-06-10 23:59:59Z | HTTP 401 |
| 2026-03-10 20:57:18Z | Down | 588 ms | 401 | global 2 | 2026-06-10 23:59:59Z | HTTP 401 |
| 2026-03-10 20:53:18Z | Down | 593 ms | 401 | global 1 | 2026-06-10 23:59:59Z | HTTP 401 |
| 2026-03-10 20:49:18Z | Down | 679 ms | 401 | global 1 | 2026-06-10 23:59:59Z | HTTP 401 |
| 2026-03-10 20:45:17Z | Down | 705 ms | 401 | global 3 | 2026-06-10 23:59:59Z | HTTP 401 |
| 2026-03-10 20:41:17Z | Down | 597 ms | 401 | global 2 | 2026-06-10 23:59:59Z | HTTP 401 |
| 2026-03-10 20:37:17Z | Down | 598 ms | 401 | global 3 | 2026-06-10 23:59:59Z | HTTP 401 |
| 2026-03-10 20:33:17Z | Down | 715 ms | 401 | global 1 | 2026-06-10 23:59:59Z | HTTP 401 |
| 2026-03-10 20:29:17Z | Down | 597 ms | 401 | global 2 | 2026-06-10 23:59:59Z | HTTP 401 |
| 2026-03-10 20:25:16Z | Down | 592 ms | 401 | global 2 | 2026-06-10 23:59:59Z | HTTP 401 |
| 2026-03-10 20:21:16Z | Down | 574 ms | 401 | global 2 | 2026-06-10 23:59:59Z | HTTP 401 |
| 2026-03-10 20:17:16Z | Down | 614 ms | 401 | global 2 | 2026-06-10 23:59:59Z | HTTP 401 |
| 2026-03-10 20:13:16Z | Down | 553 ms | 401 | global 2 | 2026-06-10 23:59:59Z | HTTP 401 |
| 2026-03-10 20:09:15Z | Down | 554 ms | 401 | global 2 | 2026-06-10 23:59:59Z | HTTP 401 |
| 2026-03-10 20:05:15Z | Down | 564 ms | 401 | global 2 | 2026-06-10 23:59:59Z | HTTP 401 |
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:17:18Z | Incident started | Unknown | Down | AI hints: Auth 90%. - Approx duration: `Ongoing` - Likely cause: **Authentication or authorization failures** - Suggested checks: Validate credentials/tokens, auth policy changes, and clock skew. |
| 2026-03-10 15:09:18Z | Investigating | Up | Unknown | - |