DNS response history for ns2.4intimate.com

ns2.4intimate.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-31. For this date, NameServerHistory found 27 DNS check records, 26 successful responses, 1 failed responses, and 341 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.4intimate.com.
Records on Selected Date

27

Historical checks stored for this nameserver on selected date

Average Latency

341 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-31 08:46

All timestamps shown in UTC

Latest Resolved IP on Selected Date

129.121.123.50

Most recently resolved hosting IP on selected date

Successful Responses

26

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

4%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.4intimate.com

Showing DNS history for 2026-08-31 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
27 2026-08-31 08:46 639237627437728712
13 ms 129.121.123.50
26 2026-08-31 08:29 639237617127808241
4016 ms 129.121.123.50
25 2026-08-31 08:12 639237606990101394
48 ms 129.121.123.50
24 2026-08-31 07:55 639237596595480036
4020 ms 129.121.123.50
23 2026-08-31 07:38 639237586261012001
20 ms 129.121.123.50
22 2026-08-31 07:21 639237576047657695
39 ms 129.121.123.50
21 2026-08-31 07:03 639237565832936443
43 ms 129.121.123.50
20 2026-08-31 06:46 639237555466329546
41 ms 129.121.123.50
19 2026-08-31 06:29 639237545032411072
18 ms 129.121.123.50
18 2026-08-31 06:11 639237534469438634
53 ms 129.121.123.50
17 2026-08-31 05:18 639237502279296801
28 ms 129.121.123.50
16 2026-08-31 05:01 639237492362730124
36 ms 129.121.123.50
15 2026-08-31 04:44 639237482311584319
21 ms 129.121.123.50
14 2026-08-31 04:27 639237472150685594
72 ms 129.121.123.50
13 2026-08-31 04:10 639237462055295430
60 ms 129.121.123.50
12 2026-08-31 03:54 639237452089913890
32 ms 129.121.123.50
11 2026-08-31 03:37 639237441972654103
-
10 2026-08-31 03:21 639237432052396478
18 ms 129.121.123.50
9 2026-08-31 03:04 639237422012990851
11 ms 129.121.123.50
8 2026-08-31 02:47 639237411889602012
17 ms 129.121.123.50
7 2026-08-31 02:30 639237401637354221
130 ms 129.121.123.50
6 2026-08-31 02:13 639237391412690360
22 ms 129.121.123.50
5 2026-08-31 01:20 639237359972957132
27 ms 129.121.123.50
4 2026-08-31 01:04 639237350032183979
23 ms 129.121.123.50
3 2026-08-31 00:47 639237340111452066
21 ms 129.121.123.50
2 2026-08-31 00:30 639237329967272514
36 ms 129.121.123.50
1 2026-08-31 00:14 639237319916508151
12 ms 129.121.123.50