DNS response history for cms1.cms500.com

cms1.cms500.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 29 DNS check records, 29 successful responses, 0 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 cms1.cms500.com.
Records on Selected Date

29

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-27 09:21

All timestamps shown in UTC

Latest Resolved IP on Selected Date

64.62.143.78

Most recently resolved hosting IP on selected date

Successful Responses

29

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 cms1.cms500.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
29 2026-08-27 09:21 639234191649612722
511 ms 64.62.143.78
28 2026-08-27 09:03 639234181105879568
34 ms 64.62.143.78
27 2026-08-27 08:46 639234170713214496
15 ms 64.62.143.78
26 2026-08-27 08:29 639234160341037652
2025 ms 64.62.143.78
25 2026-08-27 08:11 639234149799404224
53 ms 64.62.143.78
24 2026-08-27 07:54 639234139553286469
59 ms 64.62.143.78
23 2026-08-27 07:00 639234107183588293
18 ms 64.62.143.78
22 2026-08-27 06:43 639234096905435724
27 ms 64.62.143.78
21 2026-08-27 06:26 639234086579410775
2220 ms 64.62.143.78
20 2026-08-27 06:09 639234076291157956
19 ms 64.62.143.78
19 2026-08-27 05:51 639234065981939454
14 ms 64.62.143.78
18 2026-08-27 05:34 639234055548642997
38 ms 64.62.143.78
17 2026-08-27 05:17 639234045267979603
31 ms 64.62.143.78
16 2026-08-27 05:00 639234034999717463
46 ms 64.62.143.78
15 2026-08-27 04:43 639234024739225358
29 ms 64.62.143.78
14 2026-08-27 04:25 639234014311170162
32 ms 64.62.143.78
13 2026-08-27 04:08 639234003806017640
2207 ms 64.62.143.78
12 2026-08-27 03:50 639233993356203030
2271 ms 64.62.143.78
11 2026-08-27 02:57 639233961301716608
16 ms 64.62.143.78
10 2026-08-27 02:40 639233950834200647
12 ms 64.62.143.78
9 2026-08-27 02:22 639233940431849026
77 ms 64.62.143.78
8 2026-08-27 02:05 639233930110596398
20 ms 64.62.143.78
7 2026-08-27 01:48 639233919705434540
16 ms 64.62.143.78
6 2026-08-27 01:31 639233909452807845
15 ms 64.62.143.78
5 2026-08-27 01:13 639233899096420820
11 ms 64.62.143.78
4 2026-08-27 00:56 639233888707824939
18 ms 64.62.143.78
3 2026-08-27 00:39 639233878461203802
20 ms 64.62.143.78
2 2026-08-27 00:21 639233868060868209
13 ms 64.62.143.78
1 2026-08-27 00:04 639233857450922991
11 ms 64.62.143.78