DNS response history for ns2.datingme.vip

ns2.datingme.vip 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 30 DNS check records, 30 successful responses, 0 failed responses, and 408 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.datingme.vip.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

408 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:21

All timestamps shown in UTC

Latest Resolved IP on Selected Date

24.121.85.112

Most recently resolved hosting IP on selected date

Successful Responses

30

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.datingme.vip

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
30 2026-08-25 10:21 639232492740373468
1176 ms 24.121.85.112
29 2026-08-25 10:04 639232482235303141
380 ms 24.121.85.112
28 2026-08-25 09:47 639232471861770303
371 ms 24.121.85.112
27 2026-08-25 09:29 639232461630217327
573 ms 24.121.85.112
26 2026-08-25 09:12 639232451282965990
409 ms 24.121.85.112
25 2026-08-25 08:55 639232440814614938
367 ms 24.121.85.112
24 2026-08-25 08:38 639232430410720425
513 ms 24.121.85.112
23 2026-08-25 08:20 639232420003096185
373 ms 24.121.85.112
22 2026-08-25 08:03 639232409467287444
366 ms 24.121.85.112
21 2026-08-25 07:45 639232399077195997
377 ms 24.121.85.112
20 2026-08-25 07:28 639232388731528337
392 ms 24.121.85.112
19 2026-08-25 07:11 639232378288598612
371 ms 24.121.85.112
18 2026-08-25 06:17 639232346196373643
365 ms 24.121.85.112
17 2026-08-25 06:00 639232336112370741
393 ms 24.121.85.112
16 2026-08-25 05:43 639232326146508970
376 ms 24.121.85.112
15 2026-08-25 05:27 639232316189381720
2 ms 24.121.85.112
14 2026-08-25 05:10 639232306217998913
2 ms 24.121.85.112
13 2026-08-25 04:54 639232296255744174
373 ms 24.121.85.112
12 2026-08-25 04:37 639232286095760789
408 ms 24.121.85.112
11 2026-08-25 04:20 639232276086186273
364 ms 24.121.85.112
10 2026-08-25 04:03 639232265900986425
417 ms 24.121.85.112
9 2026-08-25 03:46 639232255723518075
548 ms 24.121.85.112
8 2026-08-25 03:29 639232245484452890
388 ms 24.121.85.112
7 2026-08-25 03:12 639232235157175331
547 ms 24.121.85.112
6 2026-08-25 02:19 639232203197189095
376 ms 24.121.85.112
5 2026-08-25 02:02 639232192844564298
371 ms 24.121.85.112
4 2026-08-25 01:44 639232182496008942
525 ms 24.121.85.112
3 2026-08-25 01:27 639232172197053132
380 ms 24.121.85.112
2 2026-08-25 00:34 639232140250307418
372 ms 24.121.85.112
1 2026-08-25 00:17 639232129927860324
362 ms 24.121.85.112