DNS response history for ns10.roi4my.com

ns10.roi4my.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 317 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 ns10.roi4my.com.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

317 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:01

All timestamps shown in UTC

Latest Resolved IP on Selected Date

68.178.202.83

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 ns10.roi4my.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 10:01 639232482235303141
254 ms 68.178.202.83
28 2026-08-25 09:43 639232471861770303
125 ms 68.178.202.83
27 2026-08-25 09:26 639232461630217327
143 ms 68.178.202.83
26 2026-08-25 09:09 639232451282965990
125 ms 68.178.202.83
25 2026-08-25 08:52 639232440814614938
134 ms 68.178.202.83
24 2026-08-25 08:34 639232430410720425
252 ms 68.178.202.83
23 2026-08-25 08:17 639232420003096185
251 ms 68.178.202.83
22 2026-08-25 08:00 639232409467287444
135 ms 68.178.202.83
21 2026-08-25 07:42 639232399077195997
134 ms 68.178.202.83
20 2026-08-25 07:25 639232388731528337
128 ms 68.178.202.83
19 2026-08-25 07:08 639232378288598612
148 ms 68.178.202.83
18 2026-08-25 06:14 639232346196373643
158 ms 68.178.202.83
17 2026-08-25 05:57 639232336112370741
2181 ms 68.178.202.83
16 2026-08-25 05:40 639232326146508970
168 ms 68.178.202.83
15 2026-08-25 05:24 639232316189381720
252 ms 68.178.202.83
14 2026-08-25 05:07 639232306217998913
253 ms 68.178.202.83
13 2026-08-25 04:51 639232296255744174
129 ms 68.178.202.83
12 2026-08-25 04:34 639232286095760789
2133 ms 68.178.202.83
11 2026-08-25 04:17 639232276086186273
258 ms 68.178.202.83
10 2026-08-25 04:00 639232265900986425
151 ms 68.178.202.83
9 2026-08-25 03:43 639232255723518075
140 ms 68.178.202.83
8 2026-08-25 03:26 639232245484452890
251 ms 68.178.202.83
7 2026-08-25 03:09 639232235157175331
130 ms 68.178.202.83
6 2026-08-25 02:16 639232203197189095
143 ms 68.178.202.83
5 2026-08-25 01:59 639232192844564298
253 ms 68.178.202.83
4 2026-08-25 01:41 639232182496008942
131 ms 68.178.202.83
3 2026-08-25 01:24 639232172197053132
257 ms 68.178.202.83
2 2026-08-25 00:31 639232140250307418
133 ms 68.178.202.83
1 2026-08-25 00:14 639232129927860324
255 ms 68.178.202.83