DNS response history for ns2.hagamf.com

ns2.hagamf.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 34 DNS check records, 34 successful responses, 0 failed responses, and 255 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.hagamf.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

255 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:43

All timestamps shown in UTC

Latest Resolved IP on Selected Date

14.207.143.52

Most recently resolved hosting IP on selected date

Successful Responses

34

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.hagamf.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
34 2026-08-26 10:43 639233370841350248
382 ms 14.207.143.52
33 2026-08-26 10:25 639233360361507238
189 ms 14.207.143.52
32 2026-08-26 10:08 639233350067824371
375 ms 14.207.143.52
31 2026-08-26 09:51 639233339545274518
5 ms 14.207.143.52
30 2026-08-26 09:33 639233329214918079
6 ms 14.207.143.52
29 2026-08-26 09:16 639233318749762337
6 ms 14.207.143.52
28 2026-08-26 08:59 639233308387917838
4 ms 14.207.143.52
27 2026-08-26 08:41 639233297961740122
380 ms 14.207.143.52
26 2026-08-26 08:24 639233287487159094
379 ms 14.207.143.52
25 2026-08-26 08:07 639233276995531707
369 ms 14.207.143.52
24 2026-08-26 07:49 639233266521568229
374 ms 14.207.143.52
23 2026-08-26 07:31 639233256081047431
375 ms 14.207.143.52
22 2026-08-26 06:38 639233223620132921
189 ms 14.207.143.52
21 2026-08-26 06:20 639233213287814244
364 ms 14.207.143.52
20 2026-08-26 06:03 639233202925983161
16 ms 14.207.143.52
19 2026-08-26 05:46 639233192644780696
3 ms 14.207.143.52
18 2026-08-26 05:28 639233182401183833
383 ms 14.207.143.52
17 2026-08-26 05:11 639233172074181051
368 ms 14.207.143.52
16 2026-08-26 04:54 639233161808421455
3 ms 14.207.143.52
15 2026-08-26 04:37 639233151357344052
368 ms 14.207.143.52
14 2026-08-26 04:20 639233141034116946
4 ms 14.207.143.52
13 2026-08-26 04:03 639233130828334142
186 ms 14.207.143.52
12 2026-08-26 03:45 639233120373450007
380 ms 14.207.143.52
11 2026-08-26 03:28 639233110066216193
369 ms 14.207.143.52
10 2026-08-26 02:35 639233078065410564
189 ms 14.207.143.52
9 2026-08-26 02:18 639233067787457832
3 ms 14.207.143.52
8 2026-08-26 02:00 639233057501801162
376 ms 14.207.143.52
7 2026-08-26 01:43 639233047089431703
371 ms 14.207.143.52
6 2026-08-26 01:26 639233036754790688
382 ms 14.207.143.52
5 2026-08-26 01:09 639233026412602472
369 ms 14.207.143.52
4 2026-08-26 00:51 639233016064066127
378 ms 14.207.143.52
3 2026-08-26 00:34 639233005922655772
384 ms 14.207.143.52
2 2026-08-26 00:17 639232995672256907
367 ms 14.207.143.52
1 2026-08-26 00:00 639232985300872416
373 ms 14.207.143.52