DNS response history for ns2.happy-news.co.jp

ns2.happy-news.co.jp 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 33 DNS check records, 33 successful responses, 0 failed responses, and 463 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.happy-news.co.jp.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

463 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:27

All timestamps shown in UTC

Latest Resolved IP on Selected Date

160.16.144.105

Most recently resolved hosting IP on selected date

Successful Responses

33

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.happy-news.co.jp

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
33 2026-08-26 10:27 639233360361507238
451 ms 160.16.144.105
32 2026-08-26 10:10 639233350067824371
427 ms 160.16.144.105
31 2026-08-26 09:52 639233339545274518
436 ms 160.16.144.105
30 2026-08-26 09:35 639233329214918079
437 ms 160.16.144.105
29 2026-08-26 09:18 639233318749762337
445 ms 160.16.144.105
28 2026-08-26 09:00 639233308387917838
435 ms 160.16.144.105
27 2026-08-26 08:43 639233297961740122
418 ms 160.16.144.105
26 2026-08-26 08:25 639233287487159094
457 ms 160.16.144.105
25 2026-08-26 08:08 639233276995531707
438 ms 160.16.144.105
24 2026-08-26 07:51 639233266521568229
453 ms 160.16.144.105
23 2026-08-26 07:33 639233256081047431
437 ms 160.16.144.105
22 2026-08-26 06:39 639233223620132921
458 ms 160.16.144.105
21 2026-08-26 06:22 639233213287814244
10 ms 160.16.144.105
20 2026-08-26 06:04 639233202925983161
459 ms 160.16.144.105
19 2026-08-26 05:47 639233192644780696
2268 ms 160.16.144.105
18 2026-08-26 05:30 639233182401183833
463 ms 160.16.144.105
17 2026-08-26 05:13 639233172074181051
468 ms 160.16.144.105
16 2026-08-26 04:56 639233161808421455
252 ms 160.16.144.105
15 2026-08-26 04:39 639233151357344052
466 ms 160.16.144.105
14 2026-08-26 04:21 639233141034116946
3 ms 160.16.144.105
13 2026-08-26 04:04 639233130828334142
472 ms 160.16.144.105
12 2026-08-26 03:47 639233120373450007
502 ms 160.16.144.105
11 2026-08-26 03:30 639233110066216193
3 ms 160.16.144.105
10 2026-08-26 02:36 639233078065410564
452 ms 160.16.144.105
9 2026-08-26 02:19 639233067787457832
475 ms 160.16.144.105
8 2026-08-26 02:02 639233057501801162
459 ms 160.16.144.105
7 2026-08-26 01:45 639233047089431703
442 ms 160.16.144.105
6 2026-08-26 01:28 639233036754790688
512 ms 160.16.144.105
5 2026-08-26 01:10 639233026412602472
447 ms 160.16.144.105
4 2026-08-26 00:53 639233016064066127
463 ms 160.16.144.105
3 2026-08-26 00:36 639233005922655772
470 ms 160.16.144.105
2 2026-08-26 00:19 639232995672256907
456 ms 160.16.144.105
1 2026-08-26 00:02 639232985300872416
449 ms 160.16.144.105