DNS response history for ns2.on-trace.com

ns2.on-trace.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-24. For this date, NameServerHistory found 38 DNS check records, 38 successful responses, 0 failed responses, and 228 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.on-trace.com.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

228 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 15:49

All timestamps shown in UTC

Latest Resolved IP on Selected Date

91.142.215.75

Most recently resolved hosting IP on selected date

Successful Responses

38

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.on-trace.com

Showing DNS history for 2026-08-24 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
38 2026-08-24 15:49 639231828211839931
9 ms 91.142.215.75
37 2026-08-24 15:32 639231818080917481
90 ms 91.142.215.75
36 2026-08-24 15:15 639231807961539652
2080 ms 91.142.215.75
35 2026-08-24 14:58 639231797631669865
100 ms 91.142.215.75
34 2026-08-24 14:05 639231765923559455
89 ms 91.142.215.75
33 2026-08-24 13:48 639231755868832964
91 ms 91.142.215.75
32 2026-08-24 13:31 639231745628278877
10 ms 91.142.215.75
31 2026-08-24 13:14 639231735407682062
52 ms 91.142.215.75
30 2026-08-24 12:21 639231703815441688
92 ms 91.142.215.75
29 2026-08-24 12:04 639231693747052549
2110 ms 91.142.215.75
28 2026-08-24 11:48 639231683712487276
4 ms 91.142.215.75
27 2026-08-24 11:31 639231673513573868
4 ms 91.142.215.75
26 2026-08-24 10:38 639231641791249939
87 ms 91.142.215.75
25 2026-08-24 10:21 639231631866211033
96 ms 91.142.215.75
24 2026-08-24 10:04 639231621644955316
88 ms 91.142.215.75
23 2026-08-24 09:47 639231611478799259
95 ms 91.142.215.75
22 2026-08-24 08:55 639231579923718211
100 ms 91.142.215.75
21 2026-08-24 08:38 639231569810702936
9 ms 91.142.215.75
20 2026-08-24 08:21 639231559762411619
66 ms 91.142.215.75
19 2026-08-24 08:04 639231549663595407
107 ms 91.142.215.75
18 2026-08-24 07:12 639231518076817246
113 ms 91.142.215.75
17 2026-08-24 06:55 639231508078650885
85 ms 91.142.215.75
16 2026-08-24 06:38 639231498210697093
92 ms 91.142.215.75
15 2026-08-24 06:22 639231488109699360
91 ms 91.142.215.75
14 2026-08-24 05:30 639231456772510692
93 ms 91.142.215.75
13 2026-08-24 05:13 639231447084631185
87 ms 91.142.215.75
12 2026-08-24 04:57 639231437208519473
80 ms 91.142.215.75
11 2026-08-24 04:40 639231427209627490
8 ms 91.142.215.75
10 2026-08-24 03:48 639231395791246644
102 ms 91.142.215.75
9 2026-08-24 03:32 639231386075551458
46 ms 91.142.215.75
8 2026-08-24 03:15 639231376208713791
96 ms 91.142.215.75
7 2026-08-24 02:59 639231366170589276
2055 ms 91.142.215.75
6 2026-08-24 02:06 639231334732159368
77 ms 91.142.215.75
5 2026-08-24 01:50 639231325035670078
30 ms 91.142.215.75
4 2026-08-24 01:33 639231315132253837
86 ms 91.142.215.75
3 2026-08-24 01:17 639231305014280808
76 ms 91.142.215.75
2 2026-08-24 00:24 639231273779380675
10 ms 91.142.215.75
1 2026-08-24 00:08 639231264180839154
68 ms 91.142.215.75