DNS response history for ns2.set-2.com

ns2.set-2.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 36 DNS check records, 35 successful responses, 1 failed responses, and 467 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-2.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

467 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:39

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.120.179.56

Most recently resolved hosting IP on selected date

Successful Responses

35

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.set-2.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
36 2026-08-25 12:39 639232576780683689
293 ms 103.120.179.56
35 2026-08-25 12:21 639232566381512620
142 ms 103.120.179.56
34 2026-08-25 12:04 639232556111768563
276 ms 103.120.179.56
33 2026-08-25 11:47 639232545839529039
274 ms 103.120.179.56
32 2026-08-25 11:30 639232535349285207
285 ms 103.120.179.56
31 2026-08-25 11:12 639232524938080723
-
30 2026-08-25 10:18 639232492740373468
135 ms 103.120.179.56
29 2026-08-25 10:01 639232482235303141
148 ms 103.120.179.56
28 2026-08-25 09:44 639232471861770303
289 ms 103.120.179.56
27 2026-08-25 09:27 639232461630217327
269 ms 103.120.179.56
26 2026-08-25 09:09 639232451282965990
172 ms 103.120.179.56
25 2026-08-25 08:52 639232440814614938
2255 ms 103.120.179.56
24 2026-08-25 08:35 639232430410720425
273 ms 103.120.179.56
23 2026-08-25 08:17 639232420003096185
2147 ms 103.120.179.56
22 2026-08-25 08:00 639232409467287444
293 ms 103.120.179.56
21 2026-08-25 07:42 639232399077195997
278 ms 103.120.179.56
20 2026-08-25 07:25 639232388731528337
287 ms 103.120.179.56
19 2026-08-25 07:08 639232378288598612
270 ms 103.120.179.56
18 2026-08-25 06:14 639232346196373643
276 ms 103.120.179.56
17 2026-08-25 05:57 639232336112370741
292 ms 103.120.179.56
16 2026-08-25 05:41 639232326146508970
4 ms 103.120.179.56
15 2026-08-25 05:24 639232316189381720
278 ms 103.120.179.56
14 2026-08-25 05:08 639232306217998913
273 ms 103.120.179.56
13 2026-08-25 04:51 639232296255744174
256 ms 103.120.179.56
12 2026-08-25 04:34 639232286095760789
280 ms 103.120.179.56
11 2026-08-25 04:17 639232276086186273
263 ms 103.120.179.56
10 2026-08-25 04:00 639232265900986425
2134 ms 103.120.179.56
9 2026-08-25 03:43 639232255723518075
271 ms 103.120.179.56
8 2026-08-25 03:26 639232245484452890
286 ms 103.120.179.56
7 2026-08-25 03:09 639232235157175331
2253 ms 103.120.179.56
6 2026-08-25 02:16 639232203197189095
278 ms 103.120.179.56
5 2026-08-25 01:59 639232192844564298
133 ms 103.120.179.56
4 2026-08-25 01:42 639232182496008942
290 ms 103.120.179.56
3 2026-08-25 01:24 639232172197053132
138 ms 103.120.179.56
2 2026-08-25 00:31 639232140250307418
271 ms 103.120.179.56
1 2026-08-25 00:14 639232129927860324
293 ms 103.120.179.56