Dev Seed - 009 Http HTTP facebook.com
Powered by AILive updates on
Uptimer: 6 hours, 10 minutes, 49 seconds
AI Status Summary
Dev Seed - 009 Http HTTP facebook.com is currently up for an HTTP endpoint (https://facebook.com/). Health signals are stable with strong recent reliability. Over the last 6 hours, all 116 checks were successful (100.00% uptime). Current check cadence is every 180 seconds with a 10000 ms timeout and a failure threshold of 3. The latest check completed at 2026-03-10 21:19:03Z, returning up in 421 ms.
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=118; incidents=0; consecutiveFailures=0.
Service Graphs
Uptime Strip
100.00%Response Trend
Avg 442 msPeak 612 ms across 96 checks.
Event Activity (24h)
2 eventsRecent Checks
| Started | Status | Duration | Code | Location | Cert Expires | Error |
|---|---|---|---|---|---|---|
| 2026-03-10 21:19:03Z | Up | 421 ms | 200 | global 1 | 2026-03-18 23:59:59Z | - |
| 2026-03-10 21:16:03Z | Up | 428 ms | 200 | global 2 | 2026-03-18 23:59:59Z | - |
| 2026-03-10 21:13:03Z | Up | 439 ms | 200 | global 3 | 2026-03-18 23:59:59Z | - |
| 2026-03-10 21:10:03Z | Up | 420 ms | 200 | global 3 | 2026-03-18 23:59:59Z | - |
| 2026-03-10 21:07:03Z | Up | 487 ms | 200 | global 3 | 2026-03-18 23:59:59Z | - |
| 2026-03-10 21:04:03Z | Up | 493 ms | 200 | global 3 | 2026-03-18 23:59:59Z | - |
| 2026-03-10 21:01:07Z | Up | 424 ms | 200 | global 1 | 2026-03-18 23:59:59Z | - |
| 2026-03-10 20:58:07Z | Up | 425 ms | 200 | global 3 | 2026-03-18 23:59:59Z | - |
| 2026-03-10 20:55:07Z | Up | 427 ms | 200 | global 3 | 2026-03-18 23:59:59Z | - |
| 2026-03-10 20:52:07Z | Up | 422 ms | 200 | global 1 | 2026-03-18 23:59:59Z | - |
| 2026-03-10 20:49:07Z | Up | 456 ms | 200 | global 1 | 2026-03-18 23:59:59Z | - |
| 2026-03-10 20:46:07Z | Up | 416 ms | 200 | global 1 | 2026-03-18 23:59:59Z | - |
| 2026-03-10 20:43:07Z | Up | 418 ms | 200 | global 2 | 2026-03-18 23:59:59Z | - |
| 2026-03-10 20:40:06Z | Up | 419 ms | 200 | global 2 | 2026-03-18 23:59:59Z | - |
| 2026-03-10 20:37:06Z | Up | 443 ms | 200 | global 2 | 2026-03-18 23:59:59Z | - |
| 2026-03-10 20:34:06Z | Up | 411 ms | 200 | global 2 | 2026-03-18 23:59:59Z | - |
| 2026-03-10 20:31:06Z | Up | 421 ms | 200 | global 1 | 2026-03-18 23:59:59Z | - |
| 2026-03-10 20:28:06Z | Up | 435 ms | 200 | global 3 | 2026-03-18 23:59:59Z | - |
| 2026-03-10 20:25:05Z | Up | 422 ms | 200 | global 3 | 2026-03-18 23:59:59Z | - |
| 2026-03-10 20:22:05Z | Up | 417 ms | 200 | global 2 | 2026-03-18 23:59:59Z | - |
Recent Events
| Time | Event | From | To | Incident Summary |
|---|---|---|---|---|
| 2026-03-10 15:10:07Z | Investigation resolved | Unknown | Up | AI hints: TLS 70%, Application 14%. - Approx duration: `Unknown` - Likely cause: **TLS or certificate negotiation failures** - Suggested checks: Check certificate chain/expiry, hostname match, and TLS handshake compa |
| 2026-03-10 15:07:07Z | Investigating | Up | Unknown | - |