DNS response history for ns2.trimiya.com

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

29

Historical checks stored for this nameserver on selected date

Average Latency

523 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:01

All timestamps shown in UTC

Latest Resolved IP on Selected Date

65.254.80.244

Most recently resolved hosting IP on selected date

Successful Responses

29

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.trimiya.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
29 2026-08-25 10:01 639232482235303141
215 ms 65.254.80.244
28 2026-08-25 09:43 639232471861770303
358 ms 65.254.80.244
27 2026-08-25 09:26 639232461630217327
213 ms 65.254.80.244
26 2026-08-25 09:09 639232451282965990
2008 ms 65.254.80.244
25 2026-08-25 08:51 639232440814614938
432 ms 65.254.80.244
24 2026-08-25 08:34 639232430410720425
34 ms 65.254.80.244
23 2026-08-25 08:17 639232420003096185
251 ms 65.254.80.244
22 2026-08-25 07:59 639232409467287444
417 ms 65.254.80.244
21 2026-08-25 07:42 639232399077195997
278 ms 65.254.80.244
20 2026-08-25 07:25 639232388731528337
8 ms 65.254.80.244
19 2026-08-25 07:07 639232378288598612
409 ms 65.254.80.244
18 2026-08-25 06:14 639232346196373643
211 ms 65.254.80.244
17 2026-08-25 05:57 639232336112370741
4 ms 65.254.80.244
16 2026-08-25 05:40 639232326146508970
331 ms 65.254.80.244
15 2026-08-25 05:24 639232316189381720
2362 ms 65.254.80.244
14 2026-08-25 05:07 639232306217998913
2252 ms 65.254.80.244
13 2026-08-25 04:50 639232296255744174
3 ms 65.254.80.244
12 2026-08-25 04:33 639232286095760789
328 ms 65.254.80.244
11 2026-08-25 04:17 639232276086186273
408 ms 65.254.80.244
10 2026-08-25 04:00 639232265900986425
397 ms 65.254.80.244
9 2026-08-25 03:43 639232255723518075
2 ms 65.254.80.244
8 2026-08-25 03:26 639232245484452890
403 ms 65.254.80.244
7 2026-08-25 03:09 639232235157175331
212 ms 65.254.80.244
6 2026-08-25 02:15 639232203197189095
418 ms 65.254.80.244
5 2026-08-25 01:58 639232192844564298
31 ms 65.254.80.244
4 2026-08-25 01:41 639232182496008942
203 ms 65.254.80.244
3 2026-08-25 01:24 639232172197053132
408 ms 65.254.80.244
2 2026-08-25 00:30 639232140250307418
2339 ms 65.254.80.244
1 2026-08-25 00:13 639232129927860324
245 ms 65.254.80.244