DNS response history for nm3.c4m3.com

nm3.c4m3.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 38 DNS check records, 38 successful responses, 0 failed responses, and 406 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 nm3.c4m3.com.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

406 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 12:40

All timestamps shown in UTC

Latest Resolved IP on Selected Date

135.148.158.222

Most recently resolved hosting IP on selected date

Successful Responses

38

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 nm3.c4m3.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
38 2026-08-27 12:40 639234307007468133
120 ms 135.148.158.222
37 2026-08-27 12:23 639234296664302575
242 ms 135.148.158.222
36 2026-08-27 12:06 639234286253196126
2216 ms 135.148.158.222
35 2026-08-27 11:12 639234253963286387
245 ms 135.148.158.222
34 2026-08-27 10:55 639234243654907465
242 ms 135.148.158.222
33 2026-08-27 10:37 639234233269654413
272 ms 135.148.158.222
32 2026-08-27 10:20 639234222943951923
248 ms 135.148.158.222
31 2026-08-27 10:03 639234212558002823
232 ms 135.148.158.222
30 2026-08-27 09:46 639234202117531850
242 ms 135.148.158.222
29 2026-08-27 09:28 639234191649612722
150 ms 135.148.158.222
28 2026-08-27 09:11 639234181105879568
246 ms 135.148.158.222
27 2026-08-27 08:53 639234170713214496
2036 ms 135.148.158.222
26 2026-08-27 08:36 639234160341037652
251 ms 135.148.158.222
25 2026-08-27 08:18 639234149799404224
120 ms 135.148.158.222
24 2026-08-27 08:01 639234139553286469
252 ms 135.148.158.222
23 2026-08-27 07:07 639234107183588293
196 ms 135.148.158.222
22 2026-08-27 06:50 639234096905435724
266 ms 135.148.158.222
21 2026-08-27 06:33 639234086579410775
208 ms 135.148.158.222
20 2026-08-27 06:16 639234076291157956
205 ms 135.148.158.222
19 2026-08-27 05:59 639234065981939454
194 ms 135.148.158.222
18 2026-08-27 05:42 639234055548642997
202 ms 135.148.158.222
17 2026-08-27 05:24 639234045267979603
211 ms 135.148.158.222
16 2026-08-27 05:07 639234034999717463
196 ms 135.148.158.222
15 2026-08-27 04:50 639234024739225358
214 ms 135.148.158.222
14 2026-08-27 04:33 639234014311170162
21 ms 135.148.158.222
13 2026-08-27 04:15 639234003806017640
197 ms 135.148.158.222
12 2026-08-27 03:58 639233993356203030
123 ms 135.148.158.222
11 2026-08-27 03:04 639233961301716608
209 ms 135.148.158.222
10 2026-08-27 02:47 639233950834200647
206 ms 135.148.158.222
9 2026-08-27 02:30 639233940431849026
205 ms 135.148.158.222
8 2026-08-27 02:12 639233930110596398
188 ms 135.148.158.222
7 2026-08-27 01:55 639233919705434540
2011 ms 135.148.158.222
6 2026-08-27 01:38 639233909452807845
222 ms 135.148.158.222
5 2026-08-27 01:21 639233899096420820
2205 ms 135.148.158.222
4 2026-08-27 01:03 639233888707824939
223 ms 135.148.158.222
3 2026-08-27 00:46 639233878461203802
207 ms 135.148.158.222
2 2026-08-27 00:29 639233868060868209
204 ms 135.148.158.222
1 2026-08-27 00:11 639233857450922991
205 ms 135.148.158.222