DNS response history for ns2.good-dating24x7.com

ns2.good-dating24x7.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 28 DNS check records, 28 successful responses, 0 failed responses, and 267 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.good-dating24x7.com.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

267 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:36

All timestamps shown in UTC

Latest Resolved IP on Selected Date

212.38.166.155

Most recently resolved hosting IP on selected date

Successful Responses

28

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.good-dating24x7.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
28 2026-08-25 09:36 639232471861770303
57 ms 212.38.166.155
27 2026-08-25 09:19 639232461630217327
56 ms 212.38.166.155
26 2026-08-25 09:02 639232451282965990
43 ms 212.38.166.155
25 2026-08-25 08:44 639232440814614938
47 ms 212.38.166.155
24 2026-08-25 08:27 639232430410720425
40 ms 212.38.166.155
23 2026-08-25 08:10 639232420003096185
83 ms 212.38.166.155
22 2026-08-25 07:52 639232409467287444
85 ms 212.38.166.155
21 2026-08-25 07:35 639232399077195997
42 ms 212.38.166.155
20 2026-08-25 07:17 639232388731528337
49 ms 212.38.166.155
19 2026-08-25 07:00 639232378288598612
77 ms 212.38.166.155
18 2026-08-25 06:06 639232346196373643
50 ms 212.38.166.155
17 2026-08-25 05:50 639232336112370741
2116 ms 212.38.166.155
16 2026-08-25 05:33 639232326146508970
2058 ms 212.38.166.155
15 2026-08-25 05:16 639232316189381720
31 ms 212.38.166.155
14 2026-08-25 05:00 639232306217998913
60 ms 212.38.166.155
13 2026-08-25 04:43 639232296255744174
24 ms 212.38.166.155
12 2026-08-25 04:26 639232286095760789
2123 ms 212.38.166.155
11 2026-08-25 04:10 639232276086186273
54 ms 212.38.166.155
10 2026-08-25 03:53 639232265900986425
38 ms 212.38.166.155
9 2026-08-25 03:36 639232255723518075
43 ms 212.38.166.155
8 2026-08-25 03:19 639232245484452890
42 ms 212.38.166.155
7 2026-08-25 03:01 639232235157175331
21 ms 212.38.166.155
6 2026-08-25 02:08 639232203197189095
61 ms 212.38.166.155
5 2026-08-25 01:51 639232192844564298
63 ms 212.38.166.155
4 2026-08-25 01:34 639232182496008942
21 ms 212.38.166.155
3 2026-08-25 01:16 639232172197053132
24 ms 212.38.166.155
2 2026-08-25 00:23 639232140250307418
26 ms 212.38.166.155
1 2026-08-25 00:06 639232129927860324
50 ms 212.38.166.155