DNS response history for ns2.happyhubbyhobby.com

ns2.happyhubbyhobby.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-26. For this date, NameServerHistory found 35 DNS check records, 35 successful responses, 0 failed responses, and 335 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.happyhubbyhobby.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

335 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:54

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.180.121.111

Most recently resolved hosting IP on selected date

Successful Responses

35

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.happyhubbyhobby.com

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
35 2026-08-26 11:54 639233414056832719
306 ms 103.180.121.111
34 2026-08-26 11:36 639233403515141099
280 ms 103.180.121.111
33 2026-08-26 10:42 639233370841350248
281 ms 103.180.121.111
32 2026-08-26 10:24 639233360361507238
271 ms 103.180.121.111
31 2026-08-26 10:07 639233350067824371
2008 ms 103.180.121.111
30 2026-08-26 09:50 639233339545274518
277 ms 103.180.121.111
29 2026-08-26 09:32 639233329214918079
2157 ms 103.180.121.111
28 2026-08-26 09:15 639233318749762337
273 ms 103.180.121.111
27 2026-08-26 08:58 639233308387917838
270 ms 103.180.121.111
26 2026-08-26 08:40 639233297961740122
274 ms 103.180.121.111
25 2026-08-26 08:23 639233287487159094
287 ms 103.180.121.111
24 2026-08-26 08:05 639233276995531707
271 ms 103.180.121.111
23 2026-08-26 07:48 639233266521568229
286 ms 103.180.121.111
22 2026-08-26 07:30 639233256081047431
285 ms 103.180.121.111
21 2026-08-26 06:36 639233223620132921
276 ms 103.180.121.111
20 2026-08-26 06:19 639233213287814244
8 ms 103.180.121.111
19 2026-08-26 06:02 639233202925983161
2 ms 103.180.121.111
18 2026-08-26 05:45 639233192644780696
272 ms 103.180.121.111
17 2026-08-26 05:27 639233182401183833
6 ms 103.180.121.111
16 2026-08-26 05:11 639233172074181051
3 ms 103.180.121.111
15 2026-08-26 04:53 639233161808421455
287 ms 103.180.121.111
14 2026-08-26 04:36 639233151357344052
2 ms 103.180.121.111
13 2026-08-26 04:19 639233141034116946
276 ms 103.180.121.111
12 2026-08-26 04:02 639233130828334142
3 ms 103.180.121.111
11 2026-08-26 03:44 639233120373450007
283 ms 103.180.121.111
10 2026-08-26 03:27 639233110066216193
294 ms 103.180.121.111
9 2026-08-26 02:34 639233078065410564
289 ms 103.180.121.111
8 2026-08-26 02:17 639233067787457832
289 ms 103.180.121.111
7 2026-08-26 01:59 639233057501801162
267 ms 103.180.121.111
6 2026-08-26 01:42 639233047089431703
272 ms 103.180.121.111
5 2026-08-26 01:25 639233036754790688
287 ms 103.180.121.111
4 2026-08-26 01:08 639233026412602472
273 ms 103.180.121.111
3 2026-08-26 00:50 639233016064066127
275 ms 103.180.121.111
2 2026-08-26 00:33 639233005922655772
273 ms 103.180.121.111
1 2026-08-26 00:16 639232995672256907
263 ms 103.180.121.111