DNS response history for ns2.triumphglobalhealth.com

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

30

Historical checks stored for this nameserver on selected date

Average Latency

334 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:18

All timestamps shown in UTC

Latest Resolved IP on Selected Date

184.168.121.185

Most recently resolved hosting IP on selected date

Successful Responses

30

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.triumphglobalhealth.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
30 2026-08-25 10:18 639232492740373468
323 ms 184.168.121.185
29 2026-08-25 10:01 639232482235303141
3 ms 184.168.121.185
28 2026-08-25 09:43 639232471861770303
186 ms 184.168.121.185
27 2026-08-25 09:26 639232461630217327
2409 ms 184.168.121.185
26 2026-08-25 09:09 639232451282965990
328 ms 184.168.121.185
25 2026-08-25 08:52 639232440814614938
322 ms 184.168.121.185
24 2026-08-25 08:34 639232430410720425
328 ms 184.168.121.185
23 2026-08-25 08:17 639232420003096185
5 ms 184.168.121.185
22 2026-08-25 08:00 639232409467287444
179 ms 184.168.121.185
21 2026-08-25 07:42 639232399077195997
322 ms 184.168.121.185
20 2026-08-25 07:25 639232388731528337
326 ms 184.168.121.185
19 2026-08-25 07:07 639232378288598612
329 ms 184.168.121.185
18 2026-08-25 06:14 639232346196373643
319 ms 184.168.121.185
17 2026-08-25 05:57 639232336112370741
340 ms 184.168.121.185
16 2026-08-25 05:40 639232326146508970
329 ms 184.168.121.185
15 2026-08-25 05:24 639232316189381720
325 ms 184.168.121.185
14 2026-08-25 05:07 639232306217998913
10 ms 184.168.121.185
13 2026-08-25 04:51 639232296255744174
376 ms 184.168.121.185
12 2026-08-25 04:34 639232286095760789
177 ms 184.168.121.185
11 2026-08-25 04:17 639232276086186273
324 ms 184.168.121.185
10 2026-08-25 04:00 639232265900986425
330 ms 184.168.121.185
9 2026-08-25 03:43 639232255723518075
7 ms 184.168.121.185
8 2026-08-25 03:26 639232245484452890
168 ms 184.168.121.185
7 2026-08-25 03:09 639232235157175331
324 ms 184.168.121.185
6 2026-08-25 02:16 639232203197189095
324 ms 184.168.121.185
5 2026-08-25 01:58 639232192844564298
321 ms 184.168.121.185
4 2026-08-25 01:41 639232182496008942
322 ms 184.168.121.185
3 2026-08-25 01:24 639232172197053132
323 ms 184.168.121.185
2 2026-08-25 00:31 639232140250307418
323 ms 184.168.121.185
1 2026-08-25 00:14 639232129927860324
320 ms 184.168.121.185