DNS response history for ns2.mode-on.com

ns2.mode-on.com is a DNS nameserver monitored by NameServerHistory. This page provides historical DNS response-time data, nameserver uptime signals, DNS latency observations, resolved IP history, successful response counts, failed response counts, and reliability indicators for this nameserver.

The selected UTC date is 2026-08-25. For this date, NameServerHistory found 29 DNS check records, 29 successful responses, 0 failed responses, and 1176 ms average response time. Current selected-date status: At least one successful DNS response was recorded for the selected date.

  • Use this report to investigate historical DNS uptime and nameserver reliability.
  • Compare DNS latency changes, failed DNS checks, and response behavior over time.
  • Review the latest resolved IP address and raw DNS check history for ns2.mode-on.com.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

1176 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:48

All timestamps shown in UTC

Latest Resolved IP on Selected Date

210.116.98.164

Most recently resolved hosting IP on selected date

Successful Responses

29

Checks that returned a measurable response

Failed Responses

0

Checks with no response or no returned latency

Failure Rate

0%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.mode-on.com

Showing DNS history for 2026-08-25 UTC. Newest records appear first.

Latency bars are scaled to a maximum of 5000 ms for quick visual comparison.

# Query Time (UTC) Correlation ID Latency Response IP Address
29 2026-08-25 09:48 639232471861770303
1153 ms 210.116.98.164
28 2026-08-25 09:31 639232461630217327
1094 ms 210.116.98.164
27 2026-08-25 09:14 639232451282965990
1157 ms 210.116.98.164
26 2026-08-25 08:57 639232440814614938
1149 ms 210.116.98.164
25 2026-08-25 08:39 639232430410720425
1152 ms 210.116.98.164
24 2026-08-25 08:22 639232420003096185
1166 ms 210.116.98.164
23 2026-08-25 08:04 639232409467287444
1148 ms 210.116.98.164
22 2026-08-25 07:47 639232399077195997
1156 ms 210.116.98.164
21 2026-08-25 07:30 639232388731528337
1161 ms 210.116.98.164
20 2026-08-25 07:12 639232378288598612
1160 ms 210.116.98.164
19 2026-08-25 06:18 639232346196373643
1162 ms 210.116.98.164
18 2026-08-25 06:02 639232336112370741
1912 ms 210.116.98.164
17 2026-08-25 05:45 639232326146508970
1152 ms 210.116.98.164
16 2026-08-25 05:28 639232316189381720
1143 ms 210.116.98.164
15 2026-08-25 05:12 639232306217998913
1147 ms 210.116.98.164
14 2026-08-25 04:55 639232296255744174
1178 ms 210.116.98.164
13 2026-08-25 04:38 639232286095760789
1149 ms 210.116.98.164
12 2026-08-25 04:21 639232276086186273
1154 ms 210.116.98.164
11 2026-08-25 04:05 639232265900986425
1085 ms 210.116.98.164
10 2026-08-25 03:48 639232255723518075
1135 ms 210.116.98.164
9 2026-08-25 03:31 639232245484452890
1137 ms 210.116.98.164
8 2026-08-25 03:14 639232235157175331
1161 ms 210.116.98.164
7 2026-08-25 02:20 639232203197189095
1158 ms 210.116.98.164
6 2026-08-25 02:03 639232192844564298
1154 ms 210.116.98.164
5 2026-08-25 01:46 639232182496008942
1154 ms 210.116.98.164
4 2026-08-25 01:29 639232172197053132
1154 ms 210.116.98.164
3 2026-08-25 00:35 639232140250307418
1165 ms 210.116.98.164
2 2026-08-25 00:18 639232129927860324
1153 ms 210.116.98.164
1 2026-08-25 00:01 639232119551972438
1145 ms 210.116.98.164