DNS response history for ns153.serve.my

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

31

Historical checks stored for this nameserver on selected date

Average Latency

552 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 13:19

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

31

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 ns153.serve.my

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
31 2026-08-24 13:19 639231735407682062
269 ms 175.138.31.166
30 2026-08-24 12:26 639231703815441688
826 ms 175.138.31.166
29 2026-08-24 12:10 639231693747052549
257 ms 175.138.31.166
28 2026-08-24 11:53 639231683712487276
256 ms 175.138.31.166
27 2026-08-24 11:36 639231673513573868
255 ms 175.138.31.166
26 2026-08-24 10:43 639231641791249939
834 ms 175.138.31.166
25 2026-08-24 10:27 639231631866211033
841 ms 175.138.31.166
24 2026-08-24 10:10 639231621644955316
260 ms 175.138.31.166
23 2026-08-24 09:53 639231611478799259
838 ms 175.138.31.166
22 2026-08-24 09:00 639231579923718211
246 ms 175.138.31.166
21 2026-08-24 08:43 639231569810702936
273 ms 175.138.31.166
20 2026-08-24 08:26 639231559762411619
833 ms 175.138.31.166
19 2026-08-24 08:10 639231549663595407
244 ms 175.138.31.166
18 2026-08-24 07:17 639231518076817246
837 ms 175.138.31.166
17 2026-08-24 07:01 639231508078650885
4 ms 175.138.31.166
16 2026-08-24 06:44 639231498210697093
265 ms 175.138.31.166
15 2026-08-24 06:27 639231488109699360
845 ms 175.138.31.166
14 2026-08-24 05:35 639231456772510692
2243 ms 175.138.31.166
13 2026-08-24 05:18 639231447084631185
3 ms 175.138.31.166
12 2026-08-24 05:02 639231437208519473
1682 ms 175.138.31.166
11 2026-08-24 04:46 639231427209627490
832 ms 175.138.31.166
10 2026-08-24 03:53 639231395791246644
830 ms 175.138.31.166
9 2026-08-24 03:37 639231386075551458
9 ms 175.138.31.166
8 2026-08-24 03:21 639231376208713791
1872 ms 175.138.31.166
7 2026-08-24 03:04 639231366170589276
252 ms 175.138.31.166
6 2026-08-24 02:11 639231334732159368
3 ms 175.138.31.166
5 2026-08-24 01:55 639231325035670078
261 ms 175.138.31.166
4 2026-08-24 01:39 639231315132253837
254 ms 175.138.31.166
3 2026-08-24 01:22 639231305014280808
178 ms 175.138.31.166
2 2026-08-24 00:30 639231273779380675
245 ms 175.138.31.166
1 2026-08-24 00:14 639231264180839154
251 ms 175.138.31.166