DNS response history for hk1.laserwave.com

hk1.laserwave.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-25. For this date, NameServerHistory found 28 DNS check records, 28 successful responses, 0 failed responses, and 421 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 hk1.laserwave.com.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

421 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:46

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.16.228.106

Most recently resolved hosting IP on selected date

Successful Responses

28

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 hk1.laserwave.com

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
28 2026-08-25 09:46 639232471861770303
2193 ms 103.16.228.106
27 2026-08-25 09:29 639232461630217327
186 ms 103.16.228.106
26 2026-08-25 09:11 639232451282965990
218 ms 103.16.228.106
25 2026-08-25 08:54 639232440814614938
187 ms 103.16.228.106
24 2026-08-25 08:37 639232430410720425
367 ms 103.16.228.106
23 2026-08-25 08:19 639232420003096185
372 ms 103.16.228.106
22 2026-08-25 08:02 639232409467287444
373 ms 103.16.228.106
21 2026-08-25 07:45 639232399077195997
372 ms 103.16.228.106
20 2026-08-25 07:27 639232388731528337
388 ms 103.16.228.106
19 2026-08-25 07:10 639232378288598612
372 ms 103.16.228.106
18 2026-08-25 06:16 639232346196373643
181 ms 103.16.228.106
17 2026-08-25 05:59 639232336112370741
260 ms 103.16.228.106
16 2026-08-25 05:43 639232326146508970
186 ms 103.16.228.106
15 2026-08-25 05:26 639232316189381720
287 ms 103.16.228.106
14 2026-08-25 05:09 639232306217998913
185 ms 103.16.228.106
13 2026-08-25 04:53 639232296255744174
372 ms 103.16.228.106
12 2026-08-25 04:36 639232286095760789
370 ms 103.16.228.106
11 2026-08-25 04:19 639232276086186273
370 ms 103.16.228.106
10 2026-08-25 04:02 639232265900986425
367 ms 103.16.228.106
9 2026-08-25 03:46 639232255723518075
189 ms 103.16.228.106
8 2026-08-25 03:28 639232245484452890
191 ms 103.16.228.106
7 2026-08-25 03:11 639232235157175331
186 ms 103.16.228.106
6 2026-08-25 02:18 639232203197189095
199 ms 103.16.228.106
5 2026-08-25 02:01 639232192844564298
288 ms 103.16.228.106
4 2026-08-25 01:44 639232182496008942
373 ms 103.16.228.106
3 2026-08-25 01:26 639232172197053132
185 ms 103.16.228.106
2 2026-08-25 00:33 639232140250307418
372 ms 103.16.228.106
1 2026-08-25 00:16 639232129927860324
2197 ms 103.16.228.106