Uptimer UptimerTEST ENVIRONMENT

Dev Seed - 010 Dns DNS zendesk.com

Powered by AI

Live updates on

Uptimer: 6 hours, 16 minutes, 30 seconds

Status: Up

Longest Uptime: 6 hours, 16 minutes, 30 seconds

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): 100.00%

Preferred Location: Auto

Last Check Location: global 2

Certificate Expiry: -

Maintenance: Unavailable on current plan

AI Status Summary

Dev Seed - 010 Dns DNS zendesk.com is currently up for a DNS target ([redacted]). Latency is trending upward and may indicate early degradation. Over the last 6 hours, all 70 checks were successful (100.00% uptime). 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:23:38Z, returning up in 7 ms. A latency degradation trend was detected for the window 2026-03-10 20:11:06Z to 2026-03-10 21:11:06Z (score 3.04).

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

Anomaly Signals

Window (UTC) Type Score Notes
2026-03-10 20:11:06Z to 2026-03-10 21:11:06Z LatencyDegradation 3.04 Recent median 12 ms vs baseline median 8 ms (z=3.04, ratio=1.56).
2026-03-10 19:11:06Z to 2026-03-10 20:11:06Z LatencyDegradation 3.37 Recent median 13 ms vs baseline median 8 ms (z=3.37, ratio=1.62).

Predictive Insights (ML.NET)

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

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

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

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

Early Warning: Degrading (confidence: 56.2%, limited confidence).

Likely Incident Type: Timeout (confidence: 23.7%, low 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=0; consecutiveFailures=0.

Service Graphs

Uptime Strip

100.00%
Up Down Paused Unknown

Response Trend

Avg 14 ms
0 ms25 ms50 ms75 ms100 ms 2026-03-10 15:08:37Z - 18 ms2026-03-10 15:14:20Z - 13 ms2026-03-10 15:18:37Z - 22 ms2026-03-10 15:23:37Z - 7 ms2026-03-10 15:28:38Z - 7 ms2026-03-10 15:33:38Z - 17 ms2026-03-10 15:38:38Z - 7 ms2026-03-10 15:43:38Z - 16 ms2026-03-10 15:48:39Z - 18 ms2026-03-10 15:53:39Z - 7 ms2026-03-10 16:11:21Z - 7 ms2026-03-10 16:13:36Z - 19 ms2026-03-10 16:18:36Z - 7 ms2026-03-10 16:23:37Z - 7 ms2026-03-10 16:28:37Z - 23 ms2026-03-10 16:33:37Z - 6 ms2026-03-10 16:38:37Z - 22 ms2026-03-10 16:43:38Z - 17 ms2026-03-10 16:48:38Z - 8 ms2026-03-10 16:53:38Z - 7 ms2026-03-10 16:58:38Z - 9 ms2026-03-10 17:03:39Z - 9 ms2026-03-10 17:08:39Z - 20 ms2026-03-10 17:13:34Z - 7 ms2026-03-10 17:18:35Z - 7 ms2026-03-10 17:23:35Z - 8 ms2026-03-10 17:28:35Z - 7 ms2026-03-10 17:33:36Z - 9 ms2026-03-10 17:38:36Z - 24 ms2026-03-10 17:43:36Z - 7 ms2026-03-10 17:48:37Z - 14 ms2026-03-10 17:53:37Z - 7 ms2026-03-10 17:58:37Z - 23 ms2026-03-10 18:03:38Z - 8 ms2026-03-10 18:08:38Z - 8 ms2026-03-10 18:13:38Z - 14 ms2026-03-10 18:18:39Z - 7 ms2026-03-10 18:23:39Z - 7 ms2026-03-10 18:28:39Z - 7 ms2026-03-10 18:33:34Z - 7 ms2026-03-10 18:38:35Z - 13 ms2026-03-10 18:43:35Z - 7 ms2026-03-10 18:48:35Z - 8 ms2026-03-10 18:53:36Z - 9 ms2026-03-10 18:58:36Z - 23 ms2026-03-10 19:03:36Z - 16 ms2026-03-10 19:08:36Z - 26 ms2026-03-10 19:13:37Z - 8 ms2026-03-10 19:18:37Z - 85 ms2026-03-10 19:23:37Z - 8 ms2026-03-10 19:28:38Z - 18 ms2026-03-10 19:33:38Z - 18 ms2026-03-10 19:38:38Z - 6 ms2026-03-10 19:43:38Z - 7 ms2026-03-10 19:48:38Z - 8 ms2026-03-10 19:53:39Z - 20 ms2026-03-10 19:58:39Z - 18 ms2026-03-10 20:03:39Z - 7 ms2026-03-10 20:08:35Z - 21 ms2026-03-10 20:13:35Z - 18 ms2026-03-10 20:18:35Z - 18 ms2026-03-10 20:23:35Z - 17 ms2026-03-10 20:28:36Z - 8 ms2026-03-10 20:33:36Z - 8 ms2026-03-10 20:38:36Z - 23 ms2026-03-10 20:43:37Z - 7 ms2026-03-10 20:48:37Z - 22 ms2026-03-10 20:53:37Z - 7 ms2026-03-10 20:58:37Z - 47 ms2026-03-10 21:03:37Z - 7 ms2026-03-10 21:08:38Z - 8 ms2026-03-10 21:13:38Z - 8 ms2026-03-10 21:18:38Z - 7 ms2026-03-10 21:23:38Z - 7 ms

Peak 85 ms across 74 checks.

Event Activity (24h)

2 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 - 2 event(s)
WedThuFriSatSunMonTue
LatencyAnomalyDetected (2)

Recent Checks

Started Status DurationLocationError
2026-03-10 21:23:38Z Up 7 msglobal 2-
2026-03-10 21:18:38Z Up 7 msglobal 3-
2026-03-10 21:13:38Z Up 8 msglobal 1-
2026-03-10 21:08:38Z Up 8 msglobal 3-
2026-03-10 21:03:37Z Up 7 msglobal 1-
2026-03-10 20:58:37Z Up 47 msglobal 2-
2026-03-10 20:53:37Z Up 7 msglobal 3-
2026-03-10 20:48:37Z Up 22 msglobal 3-
2026-03-10 20:43:37Z Up 7 msglobal 1-
2026-03-10 20:38:36Z Up 23 msglobal 3-
2026-03-10 20:33:36Z Up 8 msglobal 1-
2026-03-10 20:28:36Z Up 8 msglobal 1-
2026-03-10 20:23:35Z Up 17 msglobal 2-
2026-03-10 20:18:35Z Up 18 msglobal 2-
2026-03-10 20:13:35Z Up 18 msglobal 1-
2026-03-10 20:08:35Z Up 21 msglobal 2-
2026-03-10 20:03:39Z Up 7 msglobal 3-
2026-03-10 19:58:39Z Up 18 msglobal 1-
2026-03-10 19:53:39Z Up 20 msglobal 1-
2026-03-10 19:48:38Z Up 8 msglobal 3-
Showing 1-20 of 74
Page 1 of 4

Recent Events

Time Event From ToIncident Summary
2026-03-10 21:11:06Z Latency anomaly detected Up Up-
2026-03-10 20:11:06Z Latency anomaly detected Up Up-
Showing 1-2 of 2
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?