DNS response history for ns2.halipos.com

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

35

Historical checks stored for this nameserver on selected date

Average Latency

226 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 11:05

All timestamps shown in UTC

Latest Resolved IP on Selected Date

161.97.102.155

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

Showing DNS history for 2026-08-27 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-27 11:05 639234253963286387
75 ms 161.97.102.155
34 2026-08-27 10:48 639234243654907465
87 ms 161.97.102.155
33 2026-08-27 10:30 639234233269654413
30 ms 161.97.102.155
32 2026-08-27 10:13 639234222943951923
34 ms 161.97.102.155
31 2026-08-27 09:56 639234212558002823
46 ms 161.97.102.155
30 2026-08-27 09:38 639234202117531850
109 ms 161.97.102.155
29 2026-08-27 09:21 639234191649612722
39 ms 161.97.102.155
28 2026-08-27 09:04 639234181105879568
45 ms 161.97.102.155
27 2026-08-27 08:46 639234170713214496
118 ms 161.97.102.155
26 2026-08-27 08:29 639234160341037652
40 ms 161.97.102.155
25 2026-08-27 08:11 639234149799404224
49 ms 161.97.102.155
24 2026-08-27 07:54 639234139553286469
33 ms 161.97.102.155
23 2026-08-27 07:00 639234107183588293
55 ms 161.97.102.155
22 2026-08-27 06:43 639234096905435724
41 ms 161.97.102.155
21 2026-08-27 06:26 639234086579410775
90 ms 161.97.102.155
20 2026-08-27 06:09 639234076291157956
90 ms 161.97.102.155
19 2026-08-27 05:52 639234065981939454
2025 ms 161.97.102.155
18 2026-08-27 05:34 639234055548642997
2136 ms 161.97.102.155
17 2026-08-27 05:17 639234045267979603
33 ms 161.97.102.155
16 2026-08-27 05:00 639234034999717463
75 ms 161.97.102.155
15 2026-08-27 04:43 639234024739225358
7 ms 161.97.102.155
14 2026-08-27 04:26 639234014311170162
53 ms 161.97.102.155
13 2026-08-27 04:08 639234003806017640
70 ms 161.97.102.155
12 2026-08-27 03:51 639233993356203030
41 ms 161.97.102.155
11 2026-08-27 02:57 639233961301716608
41 ms 161.97.102.155
10 2026-08-27 02:40 639233950834200647
10 ms 161.97.102.155
9 2026-08-27 02:22 639233940431849026
32 ms 161.97.102.155
8 2026-08-27 02:05 639233930110596398
8 ms 161.97.102.155
7 2026-08-27 01:48 639233919705434540
58 ms 161.97.102.155
6 2026-08-27 01:31 639233909452807845
2007 ms 161.97.102.155
5 2026-08-27 01:14 639233899096420820
83 ms 161.97.102.155
4 2026-08-27 00:56 639233888707824939
32 ms 161.97.102.155
3 2026-08-27 00:39 639233878461203802
59 ms 161.97.102.155
2 2026-08-27 00:22 639233868060868209
74 ms 161.97.102.155
1 2026-08-27 00:04 639233857450922991
71 ms 161.97.102.155