DNS response history for ns2.set.repair

ns2.set.repair 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 38 DNS check records, 38 successful responses, 0 failed responses, and 281 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.set.repair.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

281 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 13:15

All timestamps shown in UTC

Latest Resolved IP on Selected Date

191.252.149.105

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.set.repair

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
38 2026-08-25 13:15 639232597643611557
410 ms 191.252.149.105
37 2026-08-25 12:57 639232587225721862
418 ms 191.252.149.105
36 2026-08-25 12:40 639232576780683689
5 ms 191.252.149.105
35 2026-08-25 12:23 639232566381512620
403 ms 191.252.149.105
34 2026-08-25 12:05 639232556111768563
191 ms 191.252.149.105
33 2026-08-25 11:48 639232545839529039
390 ms 191.252.149.105
32 2026-08-25 11:31 639232535349285207
180 ms 191.252.149.105
31 2026-08-25 11:13 639232524938080723
184 ms 191.252.149.105
30 2026-08-25 10:20 639232492740373468
191 ms 191.252.149.105
29 2026-08-25 10:03 639232482235303141
200 ms 191.252.149.105
28 2026-08-25 09:45 639232471861770303
192 ms 191.252.149.105
27 2026-08-25 09:28 639232461630217327
192 ms 191.252.149.105
26 2026-08-25 09:11 639232451282965990
194 ms 191.252.149.105
25 2026-08-25 08:53 639232440814614938
184 ms 191.252.149.105
24 2026-08-25 08:36 639232430410720425
186 ms 191.252.149.105
23 2026-08-25 08:19 639232420003096185
5 ms 191.252.149.105
22 2026-08-25 08:01 639232409467287444
486 ms 191.252.149.105
21 2026-08-25 07:44 639232399077195997
402 ms 191.252.149.105
20 2026-08-25 07:26 639232388731528337
5 ms 191.252.149.105
19 2026-08-25 07:09 639232378288598612
198 ms 191.252.149.105
18 2026-08-25 06:15 639232346196373643
389 ms 191.252.149.105
17 2026-08-25 05:59 639232336112370741
402 ms 191.252.149.105
16 2026-08-25 05:42 639232326146508970
176 ms 191.252.149.105
15 2026-08-25 05:25 639232316189381720
181 ms 191.252.149.105
14 2026-08-25 05:09 639232306217998913
188 ms 191.252.149.105
13 2026-08-25 04:52 639232296255744174
399 ms 191.252.149.105
12 2026-08-25 04:35 639232286095760789
391 ms 191.252.149.105
11 2026-08-25 04:18 639232276086186273
375 ms 191.252.149.105
10 2026-08-25 04:02 639232265900986425
183 ms 191.252.149.105
9 2026-08-25 03:45 639232255723518075
178 ms 191.252.149.105
8 2026-08-25 03:28 639232245484452890
406 ms 191.252.149.105
7 2026-08-25 03:11 639232235157175331
401 ms 191.252.149.105
6 2026-08-25 02:17 639232203197189095
413 ms 191.252.149.105
5 2026-08-25 02:00 639232192844564298
399 ms 191.252.149.105
4 2026-08-25 01:43 639232182496008942
397 ms 191.252.149.105
3 2026-08-25 01:26 639232172197053132
395 ms 191.252.149.105
2 2026-08-25 00:32 639232140250307418
404 ms 191.252.149.105
1 2026-08-25 00:15 639232129927860324
387 ms 191.252.149.105