DNS response history for ns2.tricom.net

ns2.tricom.net 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 32 DNS check records, 32 successful responses, 0 failed responses, and 513 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.tricom.net.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

513 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:32

All timestamps shown in UTC

Latest Resolved IP on Selected Date

200.42.213.21

Most recently resolved hosting IP on selected date

Successful Responses

32

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.tricom.net

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
32 2026-08-25 11:32 639232535349285207
2526 ms 200.42.213.21
31 2026-08-25 11:15 639232524938080723
308 ms 200.42.213.21
30 2026-08-25 10:21 639232492740373468
855 ms 200.42.213.21
29 2026-08-25 10:04 639232482235303141
148 ms 200.42.213.21
28 2026-08-25 09:46 639232471861770303
154 ms 200.42.213.21
27 2026-08-25 09:29 639232461630217327
593 ms 200.42.213.21
26 2026-08-25 09:12 639232451282965990
157 ms 200.42.213.21
25 2026-08-25 08:55 639232440814614938
490 ms 200.42.213.21
24 2026-08-25 08:37 639232430410720425
812 ms 200.42.213.21
23 2026-08-25 08:20 639232420003096185
150 ms 200.42.213.21
22 2026-08-25 08:02 639232409467287444
447 ms 200.42.213.21
21 2026-08-25 07:45 639232399077195997
204 ms 200.42.213.21
20 2026-08-25 07:28 639232388731528337
592 ms 200.42.213.21
19 2026-08-25 07:10 639232378288598612
454 ms 200.42.213.21
18 2026-08-25 06:17 639232346196373643
452 ms 200.42.213.21
17 2026-08-25 06:00 639232336112370741
583 ms 200.42.213.21
16 2026-08-25 05:43 639232326146508970
650 ms 200.42.213.21
15 2026-08-25 05:26 639232316189381720
290 ms 200.42.213.21
14 2026-08-25 05:10 639232306217998913
473 ms 200.42.213.21
13 2026-08-25 04:53 639232296255744174
292 ms 200.42.213.21
12 2026-08-25 04:36 639232286095760789
156 ms 200.42.213.21
11 2026-08-25 04:19 639232276086186273
301 ms 200.42.213.21
10 2026-08-25 04:03 639232265900986425
2619 ms 200.42.213.21
9 2026-08-25 03:46 639232255723518075
390 ms 200.42.213.21
8 2026-08-25 03:29 639232245484452890
28 ms 200.42.213.21
7 2026-08-25 03:12 639232235157175331
299 ms 200.42.213.21
6 2026-08-25 02:18 639232203197189095
298 ms 200.42.213.21
5 2026-08-25 02:01 639232192844564298
285 ms 200.42.213.21
4 2026-08-25 01:44 639232182496008942
877 ms 200.42.213.21
3 2026-08-25 01:27 639232172197053132
147 ms 200.42.213.21
2 2026-08-25 00:33 639232140250307418
381 ms 200.42.213.21
1 2026-08-25 00:16 639232129927860324
8 ms 200.42.213.21