DNS response history for ns2.solofreshdigital.net

ns2.solofreshdigital.net 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 37 DNS check records, 36 successful responses, 1 failed responses, and 100 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.solofreshdigital.net.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

100 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-31 12:18

All timestamps shown in UTC

Latest Resolved IP on Selected Date

99.83.229.113

Most recently resolved hosting IP on selected date

Successful Responses

36

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.solofreshdigital.net

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
37 2026-08-31 12:18 639237753225101103
66 ms 99.83.229.113
36 2026-08-31 12:01 639237742927117371
105 ms 99.83.229.113
35 2026-08-31 11:43 639237732538256235
158 ms 99.83.229.113
34 2026-08-31 11:26 639237722025682013
116 ms 99.83.229.113
33 2026-08-31 11:09 639237711568720101
253 ms 99.83.229.113
32 2026-08-31 10:51 639237701119461876
100 ms 99.83.229.113
31 2026-08-31 10:34 639237690759595513
80 ms 99.83.229.113
30 2026-08-31 10:16 639237680122296836
98 ms 99.83.229.113
29 2026-08-31 09:23 639237647999458954
140 ms 99.83.229.113
28 2026-08-31 09:05 639237637680951774
74 ms 99.83.229.113
27 2026-08-31 08:48 639237627437728712
87 ms 99.83.229.113
26 2026-08-31 08:31 639237617127808241
41 ms 99.83.229.113
25 2026-08-31 08:14 639237606990101394
59 ms 99.83.229.113
24 2026-08-31 07:57 639237596595480036
45 ms 99.83.229.113
23 2026-08-31 07:40 639237586261012001
282 ms 99.83.229.113
22 2026-08-31 07:23 639237576047657695
52 ms 99.83.229.113
21 2026-08-31 07:06 639237565832936443
164 ms 99.83.229.113
20 2026-08-31 06:48 639237555466329546
54 ms 99.83.229.113
19 2026-08-31 06:31 639237545032411072
98 ms 99.83.229.113
18 2026-08-31 06:13 639237534469438634
74 ms 99.83.229.113
17 2026-08-31 05:20 639237502279296801
89 ms 99.83.229.113
16 2026-08-31 05:03 639237492362730124
45 ms 99.83.229.113
15 2026-08-31 04:46 639237482311584319
119 ms 99.83.229.113
14 2026-08-31 04:30 639237472150685594
59 ms 99.83.229.113
13 2026-08-31 04:13 639237462055295430
191 ms 99.83.229.113
12 2026-08-31 03:56 639237452089913890
47 ms 99.83.229.113
11 2026-08-31 03:39 639237441972654103
157 ms 99.83.229.113
10 2026-08-31 03:23 639237432052396478
29 ms 99.83.229.113
9 2026-08-31 03:06 639237422012990851
10 ms 99.83.229.113
8 2026-08-31 02:49 639237411889602012
61 ms 99.83.229.113
7 2026-08-31 02:32 639237401637354221
99 ms 99.83.229.113
6 2026-08-31 02:15 639237391412690360
69 ms 99.83.229.113
5 2026-08-31 01:22 639237359972957132
12 ms 99.83.229.113
4 2026-08-31 01:06 639237350032183979
-
3 2026-08-31 00:49 639237340111452066
154 ms 99.83.229.113
2 2026-08-31 00:33 639237329967272514
133 ms 99.83.229.113
1 2026-08-31 00:16 639237319916508151
186 ms 99.83.229.113