DNS response history for ns2.cms502.com

ns2.cms502.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 39 DNS check records, 39 successful responses, 0 failed responses, and 392 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.cms502.com.
Records on Selected Date

39

Historical checks stored for this nameserver on selected date

Average Latency

392 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 13:01

All timestamps shown in UTC

Latest Resolved IP on Selected Date

94.154.36.178

Most recently resolved hosting IP on selected date

Successful Responses

39

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 ns2.cms502.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
39 2026-08-27 13:01 639234317475724313
355 ms 94.154.36.178
38 2026-08-27 12:43 639234307007468133
347 ms 94.154.36.178
37 2026-08-27 12:26 639234296664302575
359 ms 94.154.36.178
36 2026-08-27 12:09 639234286253196126
352 ms 94.154.36.178
35 2026-08-27 11:15 639234253963286387
351 ms 94.154.36.178
34 2026-08-27 10:58 639234243654907465
345 ms 94.154.36.178
33 2026-08-27 10:40 639234233269654413
232 ms 94.154.36.178
32 2026-08-27 10:23 639234222943951923
344 ms 94.154.36.178
31 2026-08-27 10:06 639234212558002823
349 ms 94.154.36.178
30 2026-08-27 09:48 639234202117531850
349 ms 94.154.36.178
29 2026-08-27 09:31 639234191649612722
240 ms 94.154.36.178
28 2026-08-27 09:14 639234181105879568
359 ms 94.154.36.178
27 2026-08-27 08:56 639234170713214496
349 ms 94.154.36.178
26 2026-08-27 08:39 639234160341037652
355 ms 94.154.36.178
25 2026-08-27 08:21 639234149799404224
354 ms 94.154.36.178
24 2026-08-27 08:04 639234139553286469
351 ms 94.154.36.178
23 2026-08-27 07:10 639234107183588293
350 ms 94.154.36.178
22 2026-08-27 06:53 639234096905435724
350 ms 94.154.36.178
21 2026-08-27 06:36 639234086579410775
364 ms 94.154.36.178
20 2026-08-27 06:19 639234076291157956
354 ms 94.154.36.178
19 2026-08-27 06:02 639234065981939454
362 ms 94.154.36.178
18 2026-08-27 05:44 639234055548642997
342 ms 94.154.36.178
17 2026-08-27 05:27 639234045267979603
511 ms 94.154.36.178
16 2026-08-27 05:10 639234034999717463
350 ms 94.154.36.178
15 2026-08-27 04:53 639234024739225358
347 ms 94.154.36.178
14 2026-08-27 04:36 639234014311170162
361 ms 94.154.36.178
13 2026-08-27 04:18 639234003806017640
350 ms 94.154.36.178
12 2026-08-27 04:00 639233993356203030
358 ms 94.154.36.178
11 2026-08-27 03:07 639233961301716608
348 ms 94.154.36.178
10 2026-08-27 02:50 639233950834200647
242 ms 94.154.36.178
9 2026-08-27 02:32 639233940431849026
348 ms 94.154.36.178
8 2026-08-27 02:15 639233930110596398
353 ms 94.154.36.178
7 2026-08-27 01:58 639233919705434540
347 ms 94.154.36.178
6 2026-08-27 01:41 639233909452807845
346 ms 94.154.36.178
5 2026-08-27 01:23 639233899096420820
348 ms 94.154.36.178
4 2026-08-27 01:06 639233888707824939
353 ms 94.154.36.178
3 2026-08-27 00:49 639233878461203802
2222 ms 94.154.36.178
2 2026-08-27 00:32 639233868060868209
224 ms 94.154.36.178
1 2026-08-27 00:14 639233857450922991
356 ms 94.154.36.178