DNS response history for ns134.serve.my

ns134.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-25. For this date, NameServerHistory found 34 DNS check records, 34 successful responses, 0 failed responses, and 694 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 ns134.serve.my.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

694 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:50

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

34

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

Showing DNS history for 2026-08-25 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
34 2026-08-25 11:50 639232545839529039
829 ms 175.138.31.163
33 2026-08-25 11:33 639232535349285207
250 ms 175.138.31.163
32 2026-08-25 11:15 639232524938080723
266 ms 175.138.31.163
31 2026-08-25 10:22 639232492740373468
249 ms 175.138.31.163
30 2026-08-25 10:05 639232482235303141
259 ms 175.138.31.163
29 2026-08-25 09:47 639232471861770303
822 ms 175.138.31.163
28 2026-08-25 09:30 639232461630217327
826 ms 175.138.31.163
27 2026-08-25 09:13 639232451282965990
408 ms 175.138.31.163
26 2026-08-25 08:55 639232440814614938
258 ms 175.138.31.163
25 2026-08-25 08:38 639232430410720425
829 ms 175.138.31.163
24 2026-08-25 08:21 639232420003096185
837 ms 175.138.31.163
23 2026-08-25 08:03 639232409467287444
827 ms 175.138.31.163
22 2026-08-25 07:46 639232399077195997
837 ms 175.138.31.163
21 2026-08-25 07:28 639232388731528337
237 ms 175.138.31.163
20 2026-08-25 07:11 639232378288598612
843 ms 175.138.31.163
19 2026-08-25 06:17 639232346196373643
245 ms 175.138.31.163
18 2026-08-25 06:00 639232336112370741
256 ms 175.138.31.163
17 2026-08-25 05:44 639232326146508970
825 ms 175.138.31.163
16 2026-08-25 05:27 639232316189381720
1676 ms 175.138.31.163
15 2026-08-25 05:11 639232306217998913
248 ms 175.138.31.163
14 2026-08-25 04:54 639232296255744174
871 ms 175.138.31.163
13 2026-08-25 04:37 639232286095760789
244 ms 175.138.31.163
12 2026-08-25 04:20 639232276086186273
826 ms 175.138.31.163
11 2026-08-25 04:04 639232265900986425
833 ms 175.138.31.163
10 2026-08-25 03:47 639232255723518075
239 ms 175.138.31.163
9 2026-08-25 03:30 639232245484452890
251 ms 175.138.31.163
8 2026-08-25 03:12 639232235157175331
2349 ms 175.138.31.163
7 2026-08-25 02:19 639232203197189095
830 ms 175.138.31.163
6 2026-08-25 02:02 639232192844564298
792 ms 175.138.31.163
5 2026-08-25 01:45 639232182496008942
837 ms 175.138.31.163
4 2026-08-25 01:27 639232172197053132
836 ms 175.138.31.163
3 2026-08-25 00:34 639232140250307418
1189 ms 175.138.31.163
2 2026-08-25 00:17 639232129927860324
833 ms 175.138.31.163
1 2026-08-25 00:00 639232119551972438
833 ms 175.138.31.163