DNS response history for ns2.pugetsoundtechnology.com

ns2.pugetsoundtechnology.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-26. For this date, NameServerHistory found 35 DNS check records, 35 successful responses, 0 failed responses, and 402 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.pugetsoundtechnology.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

402 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:53

All timestamps shown in UTC

Latest Resolved IP on Selected Date

108.161.137.72

Most recently resolved hosting IP on selected date

Successful Responses

35

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

Showing DNS history for 2026-08-26 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
35 2026-08-26 11:53 639233414056832719
330 ms 108.161.137.72
34 2026-08-26 11:36 639233403515141099
275 ms 108.161.137.72
33 2026-08-26 10:41 639233370841350248
283 ms 108.161.137.72
32 2026-08-26 10:24 639233360361507238
399 ms 108.161.137.72
31 2026-08-26 10:06 639233350067824371
8 ms 108.161.137.72
30 2026-08-26 09:49 639233339545274518
269 ms 108.161.137.72
29 2026-08-26 09:32 639233329214918079
267 ms 108.161.137.72
28 2026-08-26 09:14 639233318749762337
277 ms 108.161.137.72
27 2026-08-26 08:57 639233308387917838
277 ms 108.161.137.72
26 2026-08-26 08:40 639233297961740122
13 ms 108.161.137.72
25 2026-08-26 08:22 639233287487159094
535 ms 108.161.137.72
24 2026-08-26 08:05 639233276995531707
282 ms 108.161.137.72
23 2026-08-26 07:47 639233266521568229
267 ms 108.161.137.72
22 2026-08-26 07:30 639233256081047431
127 ms 108.161.137.72
21 2026-08-26 06:36 639233223620132921
296 ms 108.161.137.72
20 2026-08-26 06:19 639233213287814244
271 ms 108.161.137.72
19 2026-08-26 06:01 639233202925983161
402 ms 108.161.137.72
18 2026-08-26 05:44 639233192644780696
286 ms 108.161.137.72
17 2026-08-26 05:27 639233182401183833
264 ms 108.161.137.72
16 2026-08-26 05:10 639233172074181051
295 ms 108.161.137.72
15 2026-08-26 04:53 639233161808421455
298 ms 108.161.137.72
14 2026-08-26 04:35 639233151357344052
546 ms 108.161.137.72
13 2026-08-26 04:18 639233141034116946
540 ms 108.161.137.72
12 2026-08-26 04:01 639233130828334142
268 ms 108.161.137.72
11 2026-08-26 03:44 639233120373450007
289 ms 108.161.137.72
10 2026-08-26 03:26 639233110066216193
268 ms 108.161.137.72
9 2026-08-26 02:33 639233078065410564
265 ms 108.161.137.72
8 2026-08-26 02:16 639233067787457832
9 ms 108.161.137.72
7 2026-08-26 01:59 639233057501801162
4535 ms 108.161.137.72
6 2026-08-26 01:42 639233047089431703
33 ms 108.161.137.72
5 2026-08-26 01:24 639233036754790688
256 ms 108.161.137.72
4 2026-08-26 01:07 639233026412602472
269 ms 108.161.137.72
3 2026-08-26 00:50 639233016064066127
265 ms 108.161.137.72
2 2026-08-26 00:33 639233005922655772
271 ms 108.161.137.72
1 2026-08-26 00:16 639232995672256907
550 ms 108.161.137.72