DNS response history for ns3.1cmshosting.com

ns3.1cmshosting.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-27. For this date, NameServerHistory found 36 DNS check records, 36 successful responses, 0 failed responses, and 263 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 ns3.1cmshosting.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

263 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 12:04

All timestamps shown in UTC

Latest Resolved IP on Selected Date

139.64.176.230

Most recently resolved hosting IP on selected date

Successful Responses

36

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 ns3.1cmshosting.com

Showing DNS history for 2026-08-27 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
36 2026-08-27 12:04 639234286253196126
36 ms 139.64.176.230
35 2026-08-27 11:10 639234253963286387
146 ms 139.64.176.230
34 2026-08-27 10:53 639234243654907465
192 ms 139.64.176.230
33 2026-08-27 10:35 639234233269654413
373 ms 139.64.176.230
32 2026-08-27 10:18 639234222943951923
201 ms 139.64.176.230
31 2026-08-27 10:01 639234212558002823
124 ms 139.64.176.230
30 2026-08-27 09:44 639234202117531850
196 ms 139.64.176.230
29 2026-08-27 09:26 639234191649612722
98 ms 139.64.176.230
28 2026-08-27 09:09 639234181105879568
97 ms 139.64.176.230
27 2026-08-27 08:51 639234170713214496
2008 ms 139.64.176.230
26 2026-08-27 08:34 639234160341037652
193 ms 139.64.176.230
25 2026-08-27 08:16 639234149799404224
203 ms 139.64.176.230
24 2026-08-27 07:59 639234139553286469
511 ms 139.64.176.230
23 2026-08-27 07:06 639234107183588293
194 ms 139.64.176.230
22 2026-08-27 06:48 639234096905435724
194 ms 139.64.176.230
21 2026-08-27 06:31 639234086579410775
125 ms 139.64.176.230
20 2026-08-27 06:14 639234076291157956
10 ms 139.64.176.230
19 2026-08-27 05:57 639234065981939454
109 ms 139.64.176.230
18 2026-08-27 05:40 639234055548642997
106 ms 139.64.176.230
17 2026-08-27 05:22 639234045267979603
99 ms 139.64.176.230
16 2026-08-27 05:05 639234034999717463
191 ms 139.64.176.230
15 2026-08-27 04:48 639234024739225358
203 ms 139.64.176.230
14 2026-08-27 04:31 639234014311170162
213 ms 139.64.176.230
13 2026-08-27 04:13 639234003806017640
95 ms 139.64.176.230
12 2026-08-27 03:56 639233993356203030
193 ms 139.64.176.230
11 2026-08-27 03:02 639233961301716608
211 ms 139.64.176.230
10 2026-08-27 02:45 639233950834200647
194 ms 139.64.176.230
9 2026-08-27 02:28 639233940431849026
145 ms 139.64.176.230
8 2026-08-27 02:10 639233930110596398
94 ms 139.64.176.230
7 2026-08-27 01:53 639233919705434540
7 ms 139.64.176.230
6 2026-08-27 01:36 639233909452807845
107 ms 139.64.176.230
5 2026-08-27 01:19 639233899096420820
123 ms 139.64.176.230
4 2026-08-27 01:01 639233888707824939
7 ms 139.64.176.230
3 2026-08-27 00:44 639233878461203802
196 ms 139.64.176.230
2 2026-08-27 00:27 639233868060868209
185 ms 139.64.176.230
1 2026-08-27 00:09 639233857450922991
2100 ms 139.64.176.230