DNS response history for ns2.connect-dns.com

ns2.connect-dns.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 39 DNS check records, 27 successful responses, 12 failed responses, and 1546 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.connect-dns.com.
Records on Selected Date

39

Historical checks stored for this nameserver on selected date

Average Latency

1546 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 13:19

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.153.36.86

Most recently resolved hosting IP on selected date

Successful Responses

27

Checks that returned a measurable response

Failed Responses

12

Checks with no response or no returned latency

Failure Rate

31%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.connect-dns.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
39 2026-08-25 13:19 639232597643611557
-
38 2026-08-25 13:02 639232587225721862
-
37 2026-08-25 12:44 639232576780683689
1922 ms 103.153.36.86
36 2026-08-25 12:27 639232566381512620
1927 ms 103.153.36.86
35 2026-08-25 12:09 639232556111768563
1956 ms 103.153.36.86
34 2026-08-25 11:52 639232545839529039
-
33 2026-08-25 11:35 639232535349285207
-
32 2026-08-25 11:18 639232524938080723
-
31 2026-08-25 10:24 639232492740373468
1859 ms 103.153.36.86
30 2026-08-25 10:07 639232482235303141
-
29 2026-08-25 09:49 639232471861770303
-
28 2026-08-25 09:32 639232461630217327
-
27 2026-08-25 09:15 639232451282965990
-
26 2026-08-25 08:58 639232440814614938
1875 ms 103.153.36.86
25 2026-08-25 08:40 639232430410720425
1880 ms 103.153.36.86
24 2026-08-25 08:23 639232420003096185
1840 ms 103.153.36.86
23 2026-08-25 08:05 639232409467287444
1828 ms 103.153.36.86
22 2026-08-25 07:48 639232399077195997
-
21 2026-08-25 07:31 639232388731528337
1868 ms 103.153.36.86
20 2026-08-25 07:13 639232378288598612
1874 ms 103.153.36.86
19 2026-08-25 06:19 639232346196373643
2 ms 103.153.36.86
18 2026-08-25 06:02 639232336112370741
2 ms 103.153.36.86
17 2026-08-25 05:46 639232326146508970
1875 ms 103.153.36.86
16 2026-08-25 05:29 639232316189381720
3 ms 103.153.36.86
15 2026-08-25 05:12 639232306217998913
3 ms 103.153.36.86
14 2026-08-25 04:56 639232296255744174
2 ms 103.153.36.86
13 2026-08-25 04:39 639232286095760789
1842 ms 103.153.36.86
12 2026-08-25 04:22 639232276086186273
1843 ms 103.153.36.86
11 2026-08-25 04:06 639232265900986425
1875 ms 103.153.36.86
10 2026-08-25 03:49 639232255723518075
3 ms 103.153.36.86
9 2026-08-25 03:32 639232245484452890
1857 ms 103.153.36.86
8 2026-08-25 03:15 639232235157175331
1900 ms 103.153.36.86
7 2026-08-25 02:21 639232203197189095
3 ms 103.153.36.86
6 2026-08-25 02:04 639232192844564298
4546 ms 103.153.36.86
5 2026-08-25 01:47 639232182496008942
-
4 2026-08-25 01:30 639232172197053132
2 ms 103.153.36.86
3 2026-08-25 00:36 639232140250307418
1981 ms 103.153.36.86
2 2026-08-25 00:19 639232129927860324
5175 ms 103.153.36.86
1 2026-08-25 00:02 639232119551972438
-