DNS response history for ns1.we-like-2meet.com

ns1.we-like-2meet.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-24. For this date, NameServerHistory found 26 DNS check records, 26 successful responses, 0 failed responses, and 431 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 ns1.we-like-2meet.com.
Records on Selected Date

26

Historical checks stored for this nameserver on selected date

Average Latency

431 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 10:34

All timestamps shown in UTC

Latest Resolved IP on Selected Date

51.68.108.121

Most recently resolved hosting IP on selected date

Successful Responses

26

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 ns1.we-like-2meet.com

Showing DNS history for 2026-08-24 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
26 2026-08-24 10:34 639231641791249939
32 ms 51.68.108.121
25 2026-08-24 10:17 639231631866211033
2033 ms 51.68.108.121
24 2026-08-24 10:01 639231621644955316
30 ms 51.68.108.121
23 2026-08-24 09:43 639231611478799259
44 ms 51.68.108.121
22 2026-08-24 08:51 639231579923718211
36 ms 51.68.108.121
21 2026-08-24 08:34 639231569810702936
2025 ms 51.68.108.121
20 2026-08-24 08:17 639231559762411619
105 ms 51.68.108.121
19 2026-08-24 08:00 639231549663595407
33 ms 51.68.108.121
18 2026-08-24 07:08 639231518076817246
58 ms 51.68.108.121
17 2026-08-24 06:51 639231508078650885
35 ms 51.68.108.121
16 2026-08-24 06:35 639231498210697093
2025 ms 51.68.108.121
15 2026-08-24 06:18 639231488109699360
30 ms 51.68.108.121
14 2026-08-24 05:26 639231456772510692
29 ms 51.68.108.121
13 2026-08-24 05:10 639231447084631185
76 ms 51.68.108.121
12 2026-08-24 04:53 639231437208519473
32 ms 51.68.108.121
11 2026-08-24 04:36 639231427209627490
17 ms 51.68.108.121
10 2026-08-24 03:44 639231395791246644
2023 ms 51.68.108.121
9 2026-08-24 03:28 639231386075551458
34 ms 51.68.108.121
8 2026-08-24 03:12 639231376208713791
2028 ms 51.68.108.121
7 2026-08-24 02:55 639231366170589276
36 ms 51.68.108.121
6 2026-08-24 02:02 639231334732159368
39 ms 51.68.108.121
5 2026-08-24 01:46 639231325035670078
85 ms 51.68.108.121
4 2026-08-24 01:30 639231315132253837
49 ms 51.68.108.121
3 2026-08-24 01:13 639231305014280808
56 ms 51.68.108.121
2 2026-08-24 00:21 639231273779380675
23 ms 51.68.108.121
1 2026-08-24 00:05 639231264180839154
196 ms 51.68.108.121