Uptimer UptimerTEST ENVIRONMENT

Dev Seed - 120 Http HTTP live.com

Powered by AI

Live updates on

Uptimer: Currently Down

Status: Down

Longest Uptime: Currently Down

Type: Http

Target: https://live.com/

Behavior: Performs active uptime checks.

Status Logic: Normal

Interval: 180 s

Timeout: 10000 ms

Retries: 1

Failure Threshold: 3

Uptime (24h): 0.00%

Preferred Location: Auto

Last Check Location: global 3

Certificate Expiry: 2026-11-09 23:59:59Z

Maintenance: Unavailable on current plan

AI Status Summary

Dev Seed - 120 Http HTTP live.com is currently down for an HTTP endpoint (https://live.com/). The service is actively degraded and needs immediate attention. Over the last 6 hours, uptime was 0.00% across 116 checks, with 116 failed checks. 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 down in 216 ms. A downtime transition was last observed at 2026-03-10 15:14:19Z. A latency degradation trend was detected for the window 2026-03-10 13:05:16Z to 2026-03-10 14:05:16Z (score 3.30).

Generated locally/offline from recent checks, events, and monitor configuration.

Anomaly Signals

Window (UTC) Type Score Notes
2026-03-10 13:05:16Z to 2026-03-10 14:05:16Z LatencyDegradation 3.30 Development synthetic anomaly coverage: recent median 261 ms vs baseline 180 ms.

Predictive Insights (ML.NET)

Incident Risk (1h): 83.3% chance of at least one incident in the next hour.

Incident Risk (24h): 100.0% chance of at least one incident in the next 24 hours.

Forecast Uptime (Next Day): 43.60% expected successful checks over the next day.

Forecast Uptime (Next 7 Days): 34.60% expected successful checks over the next 7 days.

Early Warning: Critical (confidence: 100.0%, high confidence).

Likely Incident Type: Timeout (confidence: 70.0%, moderate confidence).

Model: mlnet-predictive-v1 (prediction model version identifier).

Model Trained: 2026-03-10 16:11:15Z (last full model training time).

Snapshot Time: 2026-03-10 21:00:00Z (when this prediction snapshot was generated).

Training Samples: 324 historical records used, across 99 monitor(s).

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=1; consecutiveFailures=118.

Service Graphs

Uptime Strip

0.00%
Up Down Paused Unknown

Response Trend

Avg 173 ms
0 ms200 ms400 ms600 ms800 ms 2026-03-10 16:34:02Z - 152 ms2026-03-10 16:37:03Z - 172 ms2026-03-10 16:40:03Z - 157 ms2026-03-10 16:43:03Z - 151 ms2026-03-10 16:46:03Z - 164 ms2026-03-10 16:49:03Z - 163 ms2026-03-10 16:52:03Z - 158 ms2026-03-10 16:55:03Z - 539 ms2026-03-10 16:58:03Z - 189 ms2026-03-10 17:00:59Z - 146 ms2026-03-10 17:03:59Z - 212 ms2026-03-10 17:06:59Z - 158 ms2026-03-10 17:10:00Z - 145 ms2026-03-10 17:13:00Z - 152 ms2026-03-10 17:16:00Z - 154 ms2026-03-10 17:19:00Z - 177 ms2026-03-10 17:22:00Z - 190 ms2026-03-10 17:25:00Z - 149 ms2026-03-10 17:28:01Z - 146 ms2026-03-10 17:31:01Z - 161 ms2026-03-10 17:34:01Z - 151 ms2026-03-10 17:37:01Z - 189 ms2026-03-10 17:40:01Z - 156 ms2026-03-10 17:43:01Z - 146 ms2026-03-10 17:46:02Z - 189 ms2026-03-10 17:49:02Z - 155 ms2026-03-10 17:52:02Z - 163 ms2026-03-10 17:55:02Z - 154 ms2026-03-10 17:58:02Z - 154 ms2026-03-10 18:01:03Z - 179 ms2026-03-10 18:04:03Z - 221 ms2026-03-10 18:07:03Z - 169 ms2026-03-10 18:10:03Z - 199 ms2026-03-10 18:12:59Z - 163 ms2026-03-10 18:15:59Z - 182 ms2026-03-10 18:18:59Z - 144 ms2026-03-10 18:21:59Z - 159 ms2026-03-10 18:24:59Z - 164 ms2026-03-10 18:27:59Z - 170 ms2026-03-10 18:31:00Z - 184 ms2026-03-10 18:34:00Z - 155 ms2026-03-10 18:37:00Z - 165 ms2026-03-10 18:40:00Z - 769 ms2026-03-10 18:43:00Z - 144 ms2026-03-10 18:46:01Z - 149 ms2026-03-10 18:49:01Z - 191 ms2026-03-10 18:52:01Z - 154 ms2026-03-10 18:55:01Z - 146 ms2026-03-10 18:58:01Z - 146 ms2026-03-10 19:01:01Z - 148 ms2026-03-10 19:04:01Z - 192 ms2026-03-10 19:07:02Z - 149 ms2026-03-10 19:10:02Z - 155 ms2026-03-10 19:13:02Z - 156 ms2026-03-10 19:16:02Z - 146 ms2026-03-10 19:19:02Z - 189 ms2026-03-10 19:22:02Z - 186 ms2026-03-10 19:25:03Z - 152 ms2026-03-10 19:28:03Z - 151 ms2026-03-10 19:31:03Z - 143 ms2026-03-10 19:34:03Z - 178 ms2026-03-10 19:37:03Z - 159 ms2026-03-10 19:40:03Z - 183 ms2026-03-10 19:43:03Z - 140 ms2026-03-10 19:46:04Z - 140 ms2026-03-10 19:48:59Z - 153 ms2026-03-10 19:51:59Z - 159 ms2026-03-10 19:54:59Z - 157 ms2026-03-10 19:57:59Z - 155 ms2026-03-10 20:00:59Z - 164 ms2026-03-10 20:03:59Z - 152 ms2026-03-10 20:07:00Z - 150 ms2026-03-10 20:10:00Z - 196 ms2026-03-10 20:13:00Z - 146 ms2026-03-10 20:16:00Z - 183 ms2026-03-10 20:19:00Z - 144 ms2026-03-10 20:22:01Z - 165 ms2026-03-10 20:25:01Z - 141 ms2026-03-10 20:28:01Z - 163 ms2026-03-10 20:31:01Z - 167 ms2026-03-10 20:34:01Z - 150 ms2026-03-10 20:37:02Z - 167 ms2026-03-10 20:40:02Z - 155 ms2026-03-10 20:43:02Z - 146 ms2026-03-10 20:46:02Z - 152 ms2026-03-10 20:49:02Z - 161 ms2026-03-10 20:52:02Z - 146 ms2026-03-10 20:55:02Z - 153 ms2026-03-10 20:58:02Z - 148 ms2026-03-10 21:01:03Z - 181 ms2026-03-10 21:04:03Z - 179 ms2026-03-10 21:07:03Z - 182 ms2026-03-10 21:10:03Z - 184 ms2026-03-10 21:13:03Z - 150 ms2026-03-10 21:16:03Z - 143 ms2026-03-10 21:19:03Z - 216 ms

Peak 769 ms across 96 checks.

Event Activity (24h)

3 events
012342026-03-04 00:00:00Z - 0 event(s)2026-03-05 00:00:00Z - 0 event(s)2026-03-06 00:00:00Z - 0 event(s)2026-03-07 00:00:00Z - 0 event(s)2026-03-08 00:00:00Z - 0 event(s)2026-03-09 00:00:00Z - 0 event(s)2026-03-10 00:00:00Z - 3 event(s)
WedThuFriSatSunMonTue
PredictiveRiskEscalated (1)Down (1)StatusChanged (1)

Recent Checks

Started Status DurationCodeLocationCert ExpiresError
2026-03-10 21:19:03Z Down 216 ms417global 32026-11-09 23:59:59ZHTTP 417
2026-03-10 21:16:03Z Down 143 ms417global 22026-11-09 23:59:59ZHTTP 417
2026-03-10 21:13:03Z Down 150 ms417global 12026-11-09 23:59:59ZHTTP 417
2026-03-10 21:10:03Z Down 184 ms417global 22026-11-09 23:59:59ZHTTP 417
2026-03-10 21:07:03Z Down 182 ms417global 12026-11-09 23:59:59ZHTTP 417
2026-03-10 21:04:03Z Down 179 ms417global 32026-11-09 23:59:59ZHTTP 417
2026-03-10 21:01:03Z Down 181 ms417global 12026-11-09 23:59:59ZHTTP 417
2026-03-10 20:58:02Z Down 148 ms417global 12026-11-09 23:59:59ZHTTP 417
2026-03-10 20:55:02Z Down 153 ms417global 12026-11-09 23:59:59ZHTTP 417
2026-03-10 20:52:02Z Down 146 ms417global 22026-11-09 23:59:59ZHTTP 417
2026-03-10 20:49:02Z Down 161 ms417global 32026-11-09 23:59:59ZHTTP 417
2026-03-10 20:46:02Z Down 152 ms417global 12026-11-09 23:59:59ZHTTP 417
2026-03-10 20:43:02Z Down 146 ms417global 22026-11-09 23:59:59ZHTTP 417
2026-03-10 20:40:02Z Down 155 ms417global 22026-11-09 23:59:59ZHTTP 417
2026-03-10 20:37:02Z Down 167 ms417global 32026-11-09 23:59:59ZHTTP 417
2026-03-10 20:34:01Z Down 150 ms417global 12026-11-09 23:59:59ZHTTP 417
2026-03-10 20:31:01Z Down 167 ms417global 32026-11-09 23:59:59ZHTTP 417
2026-03-10 20:28:01Z Down 163 ms417global 32026-11-09 23:59:59ZHTTP 417
2026-03-10 20:25:01Z Down 141 ms417global 22026-11-09 23:59:59ZHTTP 417
2026-03-10 20:22:01Z Down 165 ms417global 22026-11-09 23:59:59ZHTTP 417
Showing 1-20 of 121
Page 1 of 7

Recent Events

Time Event From ToIncident Summary
2026-03-10 16:00:00Z Predictive risk escalated Down DownPredictive 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:14:19Z Incident started Unknown DownAI hints: Application 90%. - Approx duration: `Ongoing` - Likely cause: **Application/server response failures** - Suggested checks: Inspect upstream logs, recent deploys, and 5xx/error-rate spikes.
2026-03-10 15:07:02Z Investigating Up Unknown-
Showing 1-3 of 3
Page 1 of 1

Embed Widget

Choose template/theme, preview it, then copy the iframe snippet.

An unhandled error has occurred. Reload x

Connection Interrupted

Uptimer is a live app session. Reconnecting...

Still reconnecting your live session in s.

We could not restore the live session yet. Retry or reload when you are ready.

Your live session was paused by the server.

We could not resume the live session. Retry or reload.

Status: Waiting... Uptime Streak: 0 Best Streak: 0

Guide the Uptimer node over outage spikes. Press Space or tap to jump.

Keeping the mini-game active while your live session reconnects...

Live session re-established. Continue with Uptimer Runner?