DNS response history for ns2.harmonymultimedia.net

ns2.harmonymultimedia.net 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 26 DNS check records, 26 successful responses, 0 failed responses, and 297 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 ns2.harmonymultimedia.net.
Records on Selected Date

26

Historical checks stored for this nameserver on selected date

Average Latency

297 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 08:25

All timestamps shown in UTC

Latest Resolved IP on Selected Date

162.240.151.203

Most recently resolved hosting IP on selected date

Successful Responses

26

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 ns2.harmonymultimedia.net

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
26 2026-08-26 08:25 639233287487159094
383 ms 162.240.151.203
25 2026-08-26 08:08 639233276995531707
369 ms 162.240.151.203
24 2026-08-26 07:50 639233266521568229
201 ms 162.240.151.203
23 2026-08-26 07:33 639233256081047431
364 ms 162.240.151.203
22 2026-08-26 06:39 639233223620132921
348 ms 162.240.151.203
21 2026-08-26 06:22 639233213287814244
382 ms 162.240.151.203
20 2026-08-26 06:04 639233202925983161
180 ms 162.240.151.203
19 2026-08-26 05:47 639233192644780696
369 ms 162.240.151.203
18 2026-08-26 05:30 639233182401183833
356 ms 162.240.151.203
17 2026-08-26 05:13 639233172074181051
361 ms 162.240.151.203
16 2026-08-26 04:56 639233161808421455
356 ms 162.240.151.203
15 2026-08-26 04:39 639233151357344052
232 ms 162.240.151.203
14 2026-08-26 04:21 639233141034116946
353 ms 162.240.151.203
13 2026-08-26 04:04 639233130828334142
353 ms 162.240.151.203
12 2026-08-26 03:47 639233120373450007
176 ms 162.240.151.203
11 2026-08-26 03:29 639233110066216193
177 ms 162.240.151.203
10 2026-08-26 02:36 639233078065410564
3 ms 162.240.151.203
9 2026-08-26 02:19 639233067787457832
282 ms 162.240.151.203
8 2026-08-26 02:02 639233057501801162
369 ms 162.240.151.203
7 2026-08-26 01:45 639233047089431703
176 ms 162.240.151.203
6 2026-08-26 01:27 639233036754790688
355 ms 162.240.151.203
5 2026-08-26 01:10 639233026412602472
174 ms 162.240.151.203
4 2026-08-26 00:53 639233016064066127
353 ms 162.240.151.203
3 2026-08-26 00:36 639233005922655772
358 ms 162.240.151.203
2 2026-08-26 00:19 639232995672256907
352 ms 162.240.151.203
1 2026-08-26 00:02 639232985300872416
351 ms 162.240.151.203