DNS response history for n2.froxlor.com

n2.froxlor.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, 33 successful responses, 2 failed responses, and 343 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 n2.froxlor.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

343 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 11:06

All timestamps shown in UTC

Latest Resolved IP on Selected Date

185.123.52.110

Most recently resolved hosting IP on selected date

Successful Responses

33

Checks that returned a measurable response

Failed Responses

2

Checks with no response or no returned latency

Failure Rate

6%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for n2.froxlor.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:06 639234253963286387
23 ms 185.123.52.110
34 2026-08-27 10:49 639234243654907465
139 ms 185.123.52.110
33 2026-08-27 10:32 639234233269654413
19 ms 185.123.52.110
32 2026-08-27 10:15 639234222943951923
47 ms 185.123.52.110
31 2026-08-27 09:57 639234212558002823
2043 ms 185.123.52.110
30 2026-08-27 09:40 639234202117531850
45 ms 185.123.52.110
29 2026-08-27 09:22 639234191649612722
9 ms 185.123.52.110
28 2026-08-27 09:05 639234181105879568
46 ms 185.123.52.110
27 2026-08-27 08:48 639234170713214496
39 ms 185.123.52.110
26 2026-08-27 08:30 639234160341037652
4046 ms 185.123.52.110
25 2026-08-27 08:13 639234149799404224
-
24 2026-08-27 07:56 639234139553286469
14 ms 185.123.52.110
23 2026-08-27 07:02 639234107183588293
2026 ms 185.123.52.110
22 2026-08-27 06:45 639234096905435724
21 ms 185.123.52.110
21 2026-08-27 06:28 639234086579410775
16 ms 185.123.52.110
20 2026-08-27 06:10 639234076291157956
17 ms 185.123.52.110
19 2026-08-27 05:53 639234065981939454
25 ms 185.123.52.110
18 2026-08-27 05:36 639234055548642997
2134 ms 185.123.52.110
17 2026-08-27 05:19 639234045267979603
9 ms 185.123.52.110
16 2026-08-27 05:02 639234034999717463
129 ms 185.123.52.110
15 2026-08-27 04:44 639234024739225358
28 ms 185.123.52.110
14 2026-08-27 04:27 639234014311170162
39 ms 185.123.52.110
13 2026-08-27 04:09 639234003806017640
19 ms 185.123.52.110
12 2026-08-27 03:52 639233993356203030
22 ms 185.123.52.110
11 2026-08-27 02:59 639233961301716608
12 ms 185.123.52.110
10 2026-08-27 02:41 639233950834200647
13 ms 185.123.52.110
9 2026-08-27 02:24 639233940431849026
14 ms 185.123.52.110
8 2026-08-27 02:07 639233930110596398
17 ms 185.123.52.110
7 2026-08-27 01:49 639233919705434540
65 ms 185.123.52.110
6 2026-08-27 01:32 639233909452807845
11 ms 185.123.52.110
5 2026-08-27 01:15 639233899096420820
9 ms 185.123.52.110
4 2026-08-27 00:58 639233888707824939
-
3 2026-08-27 00:41 639233878461203802
27 ms 185.123.52.110
2 2026-08-27 00:23 639233868060868209
163 ms 185.123.52.110
1 2026-08-27 00:06 639233857450922991
42 ms 185.123.52.110