DNS response history for ns200.my-serve.com

ns200.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 24 DNS check records, 24 successful responses, 0 failed responses, and 689 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 ns200.my-serve.com.
Records on Selected Date

24

Historical checks stored for this nameserver on selected date

Average Latency

689 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 10:10

All timestamps shown in UTC

Latest Resolved IP on Selected Date

175.138.31.166

Most recently resolved hosting IP on selected date

Successful Responses

24

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 ns200.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
24 2026-08-24 10:10 639231621644955316
2315 ms 175.138.31.166
23 2026-08-24 09:53 639231611478799259
515 ms 175.138.31.166
22 2026-08-24 09:00 639231579923718211
5 ms 175.138.31.166
21 2026-08-24 08:44 639231569810702936
1080 ms 175.138.31.166
20 2026-08-24 08:27 639231559762411619
3 ms 175.138.31.166
19 2026-08-24 08:10 639231549663595407
511 ms 175.138.31.166
18 2026-08-24 07:17 639231518076817246
1097 ms 175.138.31.166
17 2026-08-24 07:01 639231508078650885
250 ms 175.138.31.166
16 2026-08-24 06:44 639231498210697093
3 ms 175.138.31.166
15 2026-08-24 06:27 639231488109699360
1083 ms 175.138.31.166
14 2026-08-24 05:35 639231456772510692
504 ms 175.138.31.166
13 2026-08-24 05:19 639231447084631185
252 ms 175.138.31.166
12 2026-08-24 05:02 639231437208519473
3688 ms 175.138.31.166
11 2026-08-24 04:46 639231427209627490
244 ms 175.138.31.166
10 2026-08-24 03:53 639231395791246644
8 ms 175.138.31.166
9 2026-08-24 03:37 639231386075551458
211 ms 175.138.31.166
8 2026-08-24 03:21 639231376208713791
3 ms 175.138.31.166
7 2026-08-24 03:04 639231366170589276
1094 ms 175.138.31.166
6 2026-08-24 02:12 639231334732159368
502 ms 175.138.31.166
5 2026-08-24 01:55 639231325035670078
1076 ms 175.138.31.166
4 2026-08-24 01:39 639231315132253837
3 ms 175.138.31.166
3 2026-08-24 01:22 639231305014280808
1090 ms 175.138.31.166
2 2026-08-24 00:30 639231273779380675
509 ms 175.138.31.166
1 2026-08-24 00:14 639231264180839154
501 ms 175.138.31.166