DNS response history for serv2.dotcms.my

serv2.dotcms.my 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 37 DNS check records, 37 successful responses, 0 failed responses, and 839 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 serv2.dotcms.my.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

839 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 12:29

All timestamps shown in UTC

Latest Resolved IP on Selected Date

149.50.213.220

Most recently resolved hosting IP on selected date

Successful Responses

37

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 serv2.dotcms.my

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
37 2026-08-27 12:29 639234296664302575
731 ms 149.50.213.220
36 2026-08-27 12:11 639234286253196126
4 ms 149.50.213.220
35 2026-08-27 11:18 639234253963286387
6 ms 149.50.213.220
34 2026-08-27 11:00 639234243654907465
329 ms 149.50.213.220
33 2026-08-27 10:43 639234233269654413
728 ms 149.50.213.220
32 2026-08-27 10:26 639234222943951923
3 ms 149.50.213.220
31 2026-08-27 10:09 639234212558002823
317 ms 149.50.213.220
30 2026-08-27 09:51 639234202117531850
320 ms 149.50.213.220
29 2026-08-27 09:34 639234191649612722
754 ms 149.50.213.220
28 2026-08-27 09:16 639234181105879568
2243 ms 149.50.213.220
27 2026-08-27 08:59 639234170713214496
327 ms 149.50.213.220
26 2026-08-27 08:42 639234160341037652
157 ms 149.50.213.220
25 2026-08-27 08:24 639234149799404224
317 ms 149.50.213.220
24 2026-08-27 08:07 639234139553286469
477 ms 149.50.213.220
23 2026-08-27 07:13 639234107183588293
165 ms 149.50.213.220
22 2026-08-27 06:56 639234096905435724
923 ms 149.50.213.220
21 2026-08-27 06:39 639234086579410775
2185 ms 149.50.213.220
20 2026-08-27 06:21 639234076291157956
2008 ms 149.50.213.220
19 2026-08-27 06:04 639234065981939454
730 ms 149.50.213.220
18 2026-08-27 05:47 639234055548642997
2007 ms 149.50.213.220
17 2026-08-27 05:30 639234045267979603
729 ms 149.50.213.220
16 2026-08-27 05:13 639234034999717463
731 ms 149.50.213.220
15 2026-08-27 04:55 639234024739225358
331 ms 149.50.213.220
14 2026-08-27 04:38 639234014311170162
2410 ms 149.50.213.220
13 2026-08-27 04:21 639234003806017640
315 ms 149.50.213.220
12 2026-08-27 04:03 639233993356203030
755 ms 149.50.213.220
11 2026-08-27 03:10 639233961301716608
156 ms 149.50.213.220
10 2026-08-27 02:53 639233950834200647
3833 ms 149.50.213.220
9 2026-08-27 02:35 639233940431849026
2009 ms 149.50.213.220
8 2026-08-27 02:18 639233930110596398
322 ms 149.50.213.220
7 2026-08-27 02:01 639233919705434540
749 ms 149.50.213.220
6 2026-08-27 01:43 639233909452807845
796 ms 149.50.213.220
5 2026-08-27 01:26 639233899096420820
835 ms 149.50.213.220
4 2026-08-27 01:09 639233888707824939
351 ms 149.50.213.220
3 2026-08-27 00:52 639233878461203802
787 ms 149.50.213.220
2 2026-08-27 00:35 639233868060868209
876 ms 149.50.213.220
1 2026-08-27 00:17 639233857450922991
316 ms 149.50.213.220