DNS response history for ns2.trilog.com

ns2.trilog.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-25. For this date, NameServerHistory found 33 DNS check records, 33 successful responses, 0 failed responses, and 266 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.trilog.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

266 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:45

All timestamps shown in UTC

Latest Resolved IP on Selected Date

51.222.84.132

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

Showing DNS history for 2026-08-25 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-25 11:45 639232545839529039
131 ms 51.222.84.132
32 2026-08-25 11:27 639232535349285207
113 ms 51.222.84.132
31 2026-08-25 11:10 639232524938080723
2108 ms 51.222.84.132
30 2026-08-25 10:16 639232492740373468
114 ms 51.222.84.132
29 2026-08-25 09:59 639232482235303141
207 ms 51.222.84.132
28 2026-08-25 09:41 639232471861770303
191 ms 51.222.84.132
27 2026-08-25 09:24 639232461630217327
100 ms 51.222.84.132
26 2026-08-25 09:07 639232451282965990
220 ms 51.222.84.132
25 2026-08-25 08:50 639232440814614938
219 ms 51.222.84.132
24 2026-08-25 08:32 639232430410720425
7 ms 51.222.84.132
23 2026-08-25 08:15 639232420003096185
102 ms 51.222.84.132
22 2026-08-25 07:58 639232409467287444
204 ms 51.222.84.132
21 2026-08-25 07:40 639232399077195997
100 ms 51.222.84.132
20 2026-08-25 07:23 639232388731528337
485 ms 51.222.84.132
19 2026-08-25 07:05 639232378288598612
193 ms 51.222.84.132
18 2026-08-25 06:12 639232346196373643
202 ms 51.222.84.132
17 2026-08-25 05:55 639232336112370741
30 ms 51.222.84.132
16 2026-08-25 05:38 639232326146508970
227 ms 51.222.84.132
15 2026-08-25 05:22 639232316189381720
149 ms 51.222.84.132
14 2026-08-25 05:05 639232306217998913
3 ms 51.222.84.132
13 2026-08-25 04:49 639232296255744174
214 ms 51.222.84.132
12 2026-08-25 04:32 639232286095760789
230 ms 51.222.84.132
11 2026-08-25 04:15 639232276086186273
9 ms 51.222.84.132
10 2026-08-25 03:58 639232265900986425
109 ms 51.222.84.132
9 2026-08-25 03:41 639232255723518075
111 ms 51.222.84.132
8 2026-08-25 03:24 639232245484452890
2107 ms 51.222.84.132
7 2026-08-25 03:07 639232235157175331
210 ms 51.222.84.132
6 2026-08-25 02:14 639232203197189095
109 ms 51.222.84.132
5 2026-08-25 01:56 639232192844564298
219 ms 51.222.84.132
4 2026-08-25 01:39 639232182496008942
31 ms 51.222.84.132
3 2026-08-25 01:22 639232172197053132
212 ms 51.222.84.132
2 2026-08-25 00:28 639232140250307418
101 ms 51.222.84.132
1 2026-08-25 00:12 639232129927860324
3 ms 51.222.84.132