DNS response history for ns2.haproxy.net

ns2.haproxy.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-27. For this date, NameServerHistory found 33 DNS check records, 33 successful responses, 0 failed responses, and 210 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.haproxy.net.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

210 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 10:36

All timestamps shown in UTC

Latest Resolved IP on Selected Date

205.234.165.42

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.haproxy.net

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
33 2026-08-27 10:36 639234233269654413
106 ms 205.234.165.42
32 2026-08-27 10:19 639234222943951923
95 ms 205.234.165.42
31 2026-08-27 10:01 639234212558002823
192 ms 205.234.165.42
30 2026-08-27 09:44 639234202117531850
184 ms 205.234.165.42
29 2026-08-27 09:27 639234191649612722
192 ms 205.234.165.42
28 2026-08-27 09:09 639234181105879568
107 ms 205.234.165.42
27 2026-08-27 08:52 639234170713214496
180 ms 205.234.165.42
26 2026-08-27 08:34 639234160341037652
192 ms 205.234.165.42
25 2026-08-27 08:17 639234149799404224
101 ms 205.234.165.42
24 2026-08-27 08:00 639234139553286469
186 ms 205.234.165.42
23 2026-08-27 07:06 639234107183588293
102 ms 205.234.165.42
22 2026-08-27 06:49 639234096905435724
2101 ms 205.234.165.42
21 2026-08-27 06:32 639234086579410775
226 ms 205.234.165.42
20 2026-08-27 06:14 639234076291157956
191 ms 205.234.165.42
19 2026-08-27 05:57 639234065981939454
189 ms 205.234.165.42
18 2026-08-27 05:40 639234055548642997
116 ms 205.234.165.42
17 2026-08-27 05:23 639234045267979603
181 ms 205.234.165.42
16 2026-08-27 05:06 639234034999717463
93 ms 205.234.165.42
15 2026-08-27 04:48 639234024739225358
122 ms 205.234.165.42
14 2026-08-27 04:31 639234014311170162
180 ms 205.234.165.42
13 2026-08-27 04:14 639234003806017640
111 ms 205.234.165.42
12 2026-08-27 03:56 639233993356203030
193 ms 205.234.165.42
11 2026-08-27 03:03 639233961301716608
8 ms 205.234.165.42
10 2026-08-27 02:46 639233950834200647
204 ms 205.234.165.42
9 2026-08-27 02:28 639233940431849026
182 ms 205.234.165.42
8 2026-08-27 02:11 639233930110596398
182 ms 205.234.165.42
7 2026-08-27 01:54 639233919705434540
185 ms 205.234.165.42
6 2026-08-27 01:36 639233909452807845
183 ms 205.234.165.42
5 2026-08-27 01:19 639233899096420820
182 ms 205.234.165.42
4 2026-08-27 01:02 639233888707824939
95 ms 205.234.165.42
3 2026-08-27 00:45 639233878461203802
179 ms 205.234.165.42
2 2026-08-27 00:27 639233868060868209
13 ms 205.234.165.42
1 2026-08-27 00:10 639233857450922991
184 ms 205.234.165.42