DNS response history for ns1.ipsserver.my

ns1.ipsserver.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-26. For this date, NameServerHistory found 29 DNS check records, 29 successful responses, 0 failed responses, and 461 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 ns1.ipsserver.my.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

461 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:32

All timestamps shown in UTC

Latest Resolved IP on Selected Date

137.59.110.220

Most recently resolved hosting IP on selected date

Successful Responses

29

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 ns1.ipsserver.my

Showing DNS history for 2026-08-26 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
29 2026-08-26 09:32 639233329214918079
336 ms 137.59.110.220
28 2026-08-26 09:15 639233318749762337
348 ms 137.59.110.220
27 2026-08-26 08:58 639233308387917838
171 ms 137.59.110.220
26 2026-08-26 08:40 639233297961740122
188 ms 137.59.110.220
25 2026-08-26 08:23 639233287487159094
338 ms 137.59.110.220
24 2026-08-26 08:06 639233276995531707
331 ms 137.59.110.220
23 2026-08-26 07:48 639233266521568229
2218 ms 137.59.110.220
22 2026-08-26 07:31 639233256081047431
321 ms 137.59.110.220
21 2026-08-26 06:37 639233223620132921
335 ms 137.59.110.220
20 2026-08-26 06:19 639233213287814244
158 ms 137.59.110.220
19 2026-08-26 06:02 639233202925983161
159 ms 137.59.110.220
18 2026-08-26 05:45 639233192644780696
324 ms 137.59.110.220
17 2026-08-26 05:28 639233182401183833
185 ms 137.59.110.220
16 2026-08-26 05:11 639233172074181051
180 ms 137.59.110.220
15 2026-08-26 04:53 639233161808421455
162 ms 137.59.110.220
14 2026-08-26 04:36 639233151357344052
232 ms 137.59.110.220
13 2026-08-26 04:19 639233141034116946
323 ms 137.59.110.220
12 2026-08-26 04:02 639233130828334142
193 ms 137.59.110.220
11 2026-08-26 03:45 639233120373450007
162 ms 137.59.110.220
10 2026-08-26 03:27 639233110066216193
343 ms 137.59.110.220
9 2026-08-26 02:34 639233078065410564
356 ms 137.59.110.220
8 2026-08-26 02:17 639233067787457832
336 ms 137.59.110.220
7 2026-08-26 02:00 639233057501801162
7 ms 137.59.110.220
6 2026-08-26 01:42 639233047089431703
329 ms 137.59.110.220
5 2026-08-26 01:25 639233036754790688
321 ms 137.59.110.220
4 2026-08-26 01:08 639233026412602472
355 ms 137.59.110.220
3 2026-08-26 00:51 639233016064066127
9 ms 137.59.110.220
2 2026-08-26 00:34 639233005922655772
320 ms 137.59.110.220
1 2026-08-26 00:17 639232995672256907
4342 ms 137.59.110.220