DNS response history for ns2.trigwebdesign.net

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

29

Historical checks stored for this nameserver on selected date

Average Latency

467 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:57

All timestamps shown in UTC

Latest Resolved IP on Selected Date

70.39.150.2

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.trigwebdesign.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
29 2026-08-25 09:57 639232482235303141
2218 ms 70.39.150.2
28 2026-08-25 09:39 639232471861770303
6 ms 70.39.150.2
27 2026-08-25 09:22 639232461630217327
5 ms 70.39.150.2
26 2026-08-25 09:05 639232451282965990
104 ms 70.39.150.2
25 2026-08-25 08:47 639232440814614938
107 ms 70.39.150.2
24 2026-08-25 08:30 639232430410720425
188 ms 70.39.150.2
23 2026-08-25 08:13 639232420003096185
2043 ms 70.39.150.2
22 2026-08-25 07:55 639232409467287444
101 ms 70.39.150.2
21 2026-08-25 07:38 639232399077195997
2168 ms 70.39.150.2
20 2026-08-25 07:21 639232388731528337
205 ms 70.39.150.2
19 2026-08-25 07:03 639232378288598612
205 ms 70.39.150.2
18 2026-08-25 06:10 639232346196373643
17 ms 70.39.150.2
17 2026-08-25 05:53 639232336112370741
190 ms 70.39.150.2
16 2026-08-25 05:36 639232326146508970
15 ms 70.39.150.2
15 2026-08-25 05:20 639232316189381720
322 ms 70.39.150.2
14 2026-08-25 05:03 639232306217998913
22 ms 70.39.150.2
13 2026-08-25 04:47 639232296255744174
2139 ms 70.39.150.2
12 2026-08-25 04:30 639232286095760789
3 ms 70.39.150.2
11 2026-08-25 04:13 639232276086186273
2 ms 70.39.150.2
10 2026-08-25 03:56 639232265900986425
166 ms 70.39.150.2
9 2026-08-25 03:39 639232255723518075
2119 ms 70.39.150.2
8 2026-08-25 03:22 639232245484452890
199 ms 70.39.150.2
7 2026-08-25 03:05 639232235157175331
169 ms 70.39.150.2
6 2026-08-25 02:11 639232203197189095
202 ms 70.39.150.2
5 2026-08-25 01:54 639232192844564298
127 ms 70.39.150.2
4 2026-08-25 01:37 639232182496008942
199 ms 70.39.150.2
3 2026-08-25 01:20 639232172197053132
2 ms 70.39.150.2
2 2026-08-25 00:26 639232140250307418
189 ms 70.39.150.2
1 2026-08-25 00:09 639232129927860324
114 ms 70.39.150.2