Uptimer UptimerTEST ENVIRONMENT

Dev Seed - 129 Dns DNS Missing 06

Powered by AI

Live updates on

Uptimer: Currently Down

Status: Down

Longest Uptime: Currently Down

Type: Dns

DNS Config: [redacted] (resolution check)

Behavior: Validates DNS resolution and optional expected records.

Status Logic: Normal

Interval: 300 s

Timeout: 5000 ms

Retries: 1

Failure Threshold: 3

Uptime (24h): 0.00%

Preferred Location: Auto

Last Check Location: global 2

Certificate Expiry: -

Maintenance: Unavailable on current plan

AI Status Summary

Dev Seed - 129 Dns DNS Missing 06 is currently down for a DNS target ([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 5000 ms timeout and a failure threshold of 3. The latest check completed at 2026-03-10 21:19:23Z, returning down in 8 ms. A downtime transition was last observed at 2026-03-10 15:19:27Z.

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

Anomaly Signals

No recent latency anomalies were detected.

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: Dns (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=71; incidents=1; consecutiveFailures=71.

Service Graphs

Uptime Strip

0.00%
Up Down Paused Unknown

Response Trend

Avg 9 ms
0 ms25 ms50 ms75 ms100 ms 2026-03-10 15:09:27Z - 8 ms2026-03-10 15:14:27Z - 9 ms2026-03-10 15:19:27Z - 7 ms2026-03-10 15:24:27Z - 8 ms2026-03-10 15:29:23Z - 10 ms2026-03-10 15:34:23Z - 9 ms2026-03-10 15:39:23Z - 8 ms2026-03-10 15:44:23Z - 7 ms2026-03-10 15:49:24Z - 7 ms2026-03-10 15:54:24Z - 8 ms2026-03-10 16:11:26Z - 11 ms2026-03-10 16:14:26Z - 9 ms2026-03-10 16:19:26Z - 9 ms2026-03-10 16:24:27Z - 15 ms2026-03-10 16:29:27Z - 7 ms2026-03-10 16:34:27Z - 9 ms2026-03-10 16:39:27Z - 10 ms2026-03-10 16:44:23Z - 9 ms2026-03-10 16:49:23Z - 10 ms2026-03-10 16:54:23Z - 9 ms2026-03-10 16:59:23Z - 9 ms2026-03-10 17:04:24Z - 9 ms2026-03-10 17:09:24Z - 8 ms2026-03-10 17:14:25Z - 12 ms2026-03-10 17:19:25Z - 7 ms2026-03-10 17:24:25Z - 8 ms2026-03-10 17:29:25Z - 12 ms2026-03-10 17:34:26Z - 7 ms2026-03-10 17:39:26Z - 9 ms2026-03-10 17:44:26Z - 10 ms2026-03-10 17:49:27Z - 10 ms2026-03-10 17:54:27Z - 10 ms2026-03-10 17:59:27Z - 9 ms2026-03-10 18:04:23Z - 9 ms2026-03-10 18:09:23Z - 10 ms2026-03-10 18:14:23Z - 9 ms2026-03-10 18:19:24Z - 9 ms2026-03-10 18:24:24Z - 8 ms2026-03-10 18:29:24Z - 9 ms2026-03-10 18:34:24Z - 7 ms2026-03-10 18:39:25Z - 10 ms2026-03-10 18:44:25Z - 13 ms2026-03-10 18:49:25Z - 9 ms2026-03-10 18:54:26Z - 35 ms2026-03-10 18:59:26Z - 9 ms2026-03-10 19:04:26Z - 9 ms2026-03-10 19:09:26Z - 9 ms2026-03-10 19:14:27Z - 9 ms2026-03-10 19:19:27Z - 9 ms2026-03-10 19:24:27Z - 9 ms2026-03-10 19:29:23Z - 9 ms2026-03-10 19:34:23Z - 9 ms2026-03-10 19:39:23Z - 9 ms2026-03-10 19:44:23Z - 10 ms2026-03-10 19:49:23Z - 8 ms2026-03-10 19:54:24Z - 8 ms2026-03-10 19:59:24Z - 9 ms2026-03-10 20:04:24Z - 8 ms2026-03-10 20:09:25Z - 10 ms2026-03-10 20:14:25Z - 7 ms2026-03-10 20:19:25Z - 8 ms2026-03-10 20:24:25Z - 8 ms2026-03-10 20:29:26Z - 8 ms2026-03-10 20:34:26Z - 8 ms2026-03-10 20:39:26Z - 9 ms2026-03-10 20:44:27Z - 7 ms2026-03-10 20:49:27Z - 9 ms2026-03-10 20:54:27Z - 9 ms2026-03-10 20:59:27Z - 8 ms2026-03-10 21:04:23Z - 8 ms2026-03-10 21:09:23Z - 7 ms2026-03-10 21:14:23Z - 7 ms2026-03-10 21:19:23Z - 8 ms

Peak 35 ms across 73 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 DurationLocationError
2026-03-10 21:19:23Z Down 8 msglobal 2Host could not be resolved.
2026-03-10 21:14:23Z Down 7 msglobal 3Host could not be resolved.
2026-03-10 21:09:23Z Down 7 msglobal 2Host could not be resolved.
2026-03-10 21:04:23Z Down 8 msglobal 2Host could not be resolved.
2026-03-10 20:59:27Z Down 8 msglobal 2Host could not be resolved.
2026-03-10 20:54:27Z Down 9 msglobal 3Host could not be resolved.
2026-03-10 20:49:27Z Down 9 msglobal 2Host could not be resolved.
2026-03-10 20:44:27Z Down 7 msglobal 2Host could not be resolved.
2026-03-10 20:39:26Z Down 9 msglobal 2Host could not be resolved.
2026-03-10 20:34:26Z Down 8 msglobal 3Host could not be resolved.
2026-03-10 20:29:26Z Down 8 msglobal 2Host could not be resolved.
2026-03-10 20:24:25Z Down 8 msglobal 2Host could not be resolved.
2026-03-10 20:19:25Z Down 8 msglobal 2Host could not be resolved.
2026-03-10 20:14:25Z Down 7 msglobal 2Host could not be resolved.
2026-03-10 20:09:25Z Down 10 msglobal 2Host could not be resolved.
2026-03-10 20:04:24Z Down 8 msglobal 2Host could not be resolved.
2026-03-10 19:59:24Z Down 9 msglobal 1Host could not be resolved.
2026-03-10 19:54:24Z Down 8 msglobal 3Host could not be resolved.
2026-03-10 19:49:23Z Down 8 msglobal 3Host could not be resolved.
2026-03-10 19:44:23Z Down 10 msglobal 3Host could not be resolved.
Showing 1-20 of 73
Page 1 of 4

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: Dns (70.0% confidence). Forecast uptime: next day 43.6%, next 7 days 34.6%.
2026-03-10 15:19:27Z Incident started Unknown DownAI hints: DNS 90%. - Approx duration: `Ongoing` - Likely cause: **DNS resolution failures** - Suggested checks: Verify resolver health, authoritative records, and TTL/propagation.
2026-03-10 15:09:27Z Investigating Down 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?