DNS response history for ns212.my-serve.com

ns212.my-serve.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-24. For this date, NameServerHistory found 32 DNS check records, 32 successful responses, 0 failed responses, and 796 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 ns212.my-serve.com.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

796 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 13:37

All timestamps shown in UTC

Latest Resolved IP on Selected Date

175.138.31.163

Most recently resolved hosting IP on selected date

Successful Responses

32

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 ns212.my-serve.com

Showing DNS history for 2026-08-24 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
32 2026-08-24 13:37 639231745628278877
255 ms 175.138.31.163
31 2026-08-24 13:20 639231735407682062
840 ms 175.138.31.163
30 2026-08-24 12:27 639231703815441688
508 ms 175.138.31.163
29 2026-08-24 12:10 639231693747052549
248 ms 175.138.31.163
28 2026-08-24 11:53 639231683712487276
1765 ms 175.138.31.163
27 2026-08-24 11:36 639231673513573868
245 ms 175.138.31.163
26 2026-08-24 10:43 639231641791249939
193 ms 175.138.31.163
25 2026-08-24 10:27 639231631866211033
5 ms 175.138.31.163
24 2026-08-24 10:10 639231621644955316
513 ms 175.138.31.163
23 2026-08-24 09:53 639231611478799259
250 ms 175.138.31.163
22 2026-08-24 09:00 639231579923718211
498 ms 175.138.31.163
21 2026-08-24 08:44 639231569810702936
257 ms 175.138.31.163
20 2026-08-24 08:27 639231559762411619
827 ms 175.138.31.163
19 2026-08-24 08:10 639231549663595407
518 ms 175.138.31.163
18 2026-08-24 07:17 639231518076817246
841 ms 175.138.31.163
17 2026-08-24 07:01 639231508078650885
256 ms 175.138.31.163
16 2026-08-24 06:44 639231498210697093
833 ms 175.138.31.163
15 2026-08-24 06:27 639231488109699360
837 ms 175.138.31.163
14 2026-08-24 05:35 639231456772510692
839 ms 175.138.31.163
13 2026-08-24 05:19 639231447084631185
5 ms 175.138.31.163
12 2026-08-24 05:02 639231437208519473
826 ms 175.138.31.163
11 2026-08-24 04:46 639231427209627490
180 ms 175.138.31.163
10 2026-08-24 03:53 639231395791246644
258 ms 175.138.31.163
9 2026-08-24 03:37 639231386075551458
518 ms 175.138.31.163
8 2026-08-24 03:21 639231376208713791
250 ms 175.138.31.163
7 2026-08-24 03:04 639231366170589276
828 ms 175.138.31.163
6 2026-08-24 02:12 639231334732159368
268 ms 175.138.31.163
5 2026-08-24 01:55 639231325035670078
1090 ms 175.138.31.163
4 2026-08-24 01:39 639231315132253837
245 ms 175.138.31.163
3 2026-08-24 01:22 639231305014280808
4313 ms 175.138.31.163
2 2026-08-24 00:30 639231273779380675
5664 ms 175.138.31.163
1 2026-08-24 00:14 639231264180839154
498 ms 175.138.31.163