DNS response history for ns2.treeo.com

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

33

Historical checks stored for this nameserver on selected date

Average Latency

184 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 10:38

All timestamps shown in UTC

Latest Resolved IP on Selected Date

104.165.111.101

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.treeo.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
33 2026-08-27 10:38 639234233269654413
137 ms 104.165.111.101
32 2026-08-27 10:21 639234222943951923
4 ms 104.165.111.101
31 2026-08-27 10:03 639234212558002823
238 ms 104.165.111.101
30 2026-08-27 09:46 639234202117531850
304 ms 104.165.111.101
29 2026-08-27 09:29 639234191649612722
265 ms 104.165.111.101
28 2026-08-27 09:11 639234181105879568
241 ms 104.165.111.101
27 2026-08-27 08:54 639234170713214496
242 ms 104.165.111.101
26 2026-08-27 08:36 639234160341037652
122 ms 104.165.111.101
25 2026-08-27 08:19 639234149799404224
250 ms 104.165.111.101
24 2026-08-27 08:02 639234139553286469
119 ms 104.165.111.101
23 2026-08-27 07:08 639234107183588293
121 ms 104.165.111.101
22 2026-08-27 06:51 639234096905435724
4 ms 104.165.111.101
21 2026-08-27 06:34 639234086579410775
5 ms 104.165.111.101
20 2026-08-27 06:16 639234076291157956
9 ms 104.165.111.101
19 2026-08-27 05:59 639234065981939454
233 ms 104.165.111.101
18 2026-08-27 05:42 639234055548642997
239 ms 104.165.111.101
17 2026-08-27 05:25 639234045267979603
232 ms 104.165.111.101
16 2026-08-27 05:08 639234034999717463
229 ms 104.165.111.101
15 2026-08-27 04:50 639234024739225358
224 ms 104.165.111.101
14 2026-08-27 04:33 639234014311170162
228 ms 104.165.111.101
13 2026-08-27 04:16 639234003806017640
116 ms 104.165.111.101
12 2026-08-27 03:58 639233993356203030
117 ms 104.165.111.101
11 2026-08-27 03:05 639233961301716608
123 ms 104.165.111.101
10 2026-08-27 02:48 639233950834200647
224 ms 104.165.111.101
9 2026-08-27 02:30 639233940431849026
238 ms 104.165.111.101
8 2026-08-27 02:13 639233930110596398
249 ms 104.165.111.101
7 2026-08-27 01:56 639233919705434540
266 ms 104.165.111.101
6 2026-08-27 01:38 639233909452807845
118 ms 104.165.111.101
5 2026-08-27 01:21 639233899096420820
230 ms 104.165.111.101
4 2026-08-27 01:04 639233888707824939
233 ms 104.165.111.101
3 2026-08-27 00:47 639233878461203802
232 ms 104.165.111.101
2 2026-08-27 00:29 639233868060868209
232 ms 104.165.111.101
1 2026-08-27 00:12 639233857450922991
235 ms 104.165.111.101