DNS response history for ns1.treecode.mx

ns1.treecode.mx 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 37 DNS check records, 37 successful responses, 0 failed responses, and 304 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 ns1.treecode.mx.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

304 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:13

All timestamps shown in UTC

Latest Resolved IP on Selected Date

162.240.154.67

Most recently resolved hosting IP on selected date

Successful Responses

37

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 ns1.treecode.mx

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
37 2026-08-26 12:13 639233424567558554
352 ms 162.240.154.67
36 2026-08-26 11:56 639233414056832719
176 ms 162.240.154.67
35 2026-08-26 11:38 639233403515141099
353 ms 162.240.154.67
34 2026-08-26 10:44 639233370841350248
176 ms 162.240.154.67
33 2026-08-26 10:26 639233360361507238
490 ms 162.240.154.67
32 2026-08-26 10:09 639233350067824371
349 ms 162.240.154.67
31 2026-08-26 09:52 639233339545274518
384 ms 162.240.154.67
30 2026-08-26 09:34 639233329214918079
614 ms 162.240.154.67
29 2026-08-26 09:17 639233318749762337
188 ms 162.240.154.67
28 2026-08-26 09:00 639233308387917838
400 ms 162.240.154.67
27 2026-08-26 08:42 639233297961740122
381 ms 162.240.154.67
26 2026-08-26 08:25 639233287487159094
377 ms 162.240.154.67
25 2026-08-26 08:08 639233276995531707
506 ms 162.240.154.67
24 2026-08-26 07:50 639233266521568229
507 ms 162.240.154.67
23 2026-08-26 07:32 639233256081047431
494 ms 162.240.154.67
22 2026-08-26 06:38 639233223620132921
354 ms 162.240.154.67
21 2026-08-26 06:21 639233213287814244
4 ms 162.240.154.67
20 2026-08-26 06:04 639233202925983161
174 ms 162.240.154.67
19 2026-08-26 05:47 639233192644780696
354 ms 162.240.154.67
18 2026-08-26 05:29 639233182401183833
354 ms 162.240.154.67
17 2026-08-26 05:13 639233172074181051
358 ms 162.240.154.67
16 2026-08-26 04:55 639233161808421455
355 ms 162.240.154.67
15 2026-08-26 04:38 639233151357344052
205 ms 162.240.154.67
14 2026-08-26 04:21 639233141034116946
352 ms 162.240.154.67
13 2026-08-26 04:04 639233130828334142
352 ms 162.240.154.67
12 2026-08-26 03:46 639233120373450007
3 ms 162.240.154.67
11 2026-08-26 03:29 639233110066216193
353 ms 162.240.154.67
10 2026-08-26 02:36 639233078065410564
176 ms 162.240.154.67
9 2026-08-26 02:19 639233067787457832
3 ms 162.240.154.67
8 2026-08-26 02:01 639233057501801162
353 ms 162.240.154.67
7 2026-08-26 01:44 639233047089431703
351 ms 162.240.154.67
6 2026-08-26 01:27 639233036754790688
352 ms 162.240.154.67
5 2026-08-26 01:10 639233026412602472
3 ms 162.240.154.67
4 2026-08-26 00:52 639233016064066127
357 ms 162.240.154.67
3 2026-08-26 00:35 639233005922655772
2 ms 162.240.154.67
2 2026-08-26 00:18 639232995672256907
352 ms 162.240.154.67
1 2026-08-26 00:01 639232985300872416
350 ms 162.240.154.67