DNS response history for ns2.roadrepairman.com

ns2.roadrepairman.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-26. For this date, NameServerHistory found 36 DNS check records, 36 successful responses, 0 failed responses, and 515 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.roadrepairman.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

515 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:55

All timestamps shown in UTC

Latest Resolved IP on Selected Date

162.240.160.133

Most recently resolved hosting IP on selected date

Successful Responses

36

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.roadrepairman.com

Showing DNS history for 2026-08-26 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
36 2026-08-26 11:55 639233414056832719
358 ms 162.240.160.133
35 2026-08-26 11:37 639233403515141099
2180 ms 162.240.160.133
34 2026-08-26 10:43 639233370841350248
219 ms 162.240.160.133
33 2026-08-26 10:26 639233360361507238
354 ms 162.240.160.133
32 2026-08-26 10:08 639233350067824371
360 ms 162.240.160.133
31 2026-08-26 09:51 639233339545274518
356 ms 162.240.160.133
30 2026-08-26 09:33 639233329214918079
358 ms 162.240.160.133
29 2026-08-26 09:16 639233318749762337
385 ms 162.240.160.133
28 2026-08-26 08:59 639233308387917838
397 ms 162.240.160.133
27 2026-08-26 08:41 639233297961740122
377 ms 162.240.160.133
26 2026-08-26 08:24 639233287487159094
394 ms 162.240.160.133
25 2026-08-26 08:07 639233276995531707
379 ms 162.240.160.133
24 2026-08-26 07:49 639233266521568229
350 ms 162.240.160.133
23 2026-08-26 07:31 639233256081047431
357 ms 162.240.160.133
22 2026-08-26 06:38 639233223620132921
352 ms 162.240.160.133
21 2026-08-26 06:20 639233213287814244
374 ms 162.240.160.133
20 2026-08-26 06:03 639233202925983161
349 ms 162.240.160.133
19 2026-08-26 05:46 639233192644780696
348 ms 162.240.160.133
18 2026-08-26 05:29 639233182401183833
347 ms 162.240.160.133
17 2026-08-26 05:12 639233172074181051
374 ms 162.240.160.133
16 2026-08-26 04:54 639233161808421455
4 ms 162.240.160.133
15 2026-08-26 04:37 639233151357344052
4 ms 162.240.160.133
14 2026-08-26 04:20 639233141034116946
228 ms 162.240.160.133
13 2026-08-26 04:03 639233130828334142
4352 ms 162.240.160.133
12 2026-08-26 03:46 639233120373450007
178 ms 162.240.160.133
11 2026-08-26 03:28 639233110066216193
3 ms 162.240.160.133
10 2026-08-26 02:35 639233078065410564
344 ms 162.240.160.133
9 2026-08-26 02:18 639233067787457832
349 ms 162.240.160.133
8 2026-08-26 02:01 639233057501801162
343 ms 162.240.160.133
7 2026-08-26 01:43 639233047089431703
346 ms 162.240.160.133
6 2026-08-26 01:26 639233036754790688
349 ms 162.240.160.133
5 2026-08-26 01:09 639233026412602472
347 ms 162.240.160.133
4 2026-08-26 00:52 639233016064066127
358 ms 162.240.160.133
3 2026-08-26 00:34 639233005922655772
2007 ms 162.240.160.133
2 2026-08-26 00:17 639232995672256907
7 ms 162.240.160.133
1 2026-08-26 00:00 639232985300872416
346 ms 162.240.160.133