DNS response history for ns2.boundwork.com

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

31

Historical checks stored for this nameserver on selected date

Average Latency

462 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:04

All timestamps shown in UTC

Latest Resolved IP on Selected Date

195.123.184.2

Most recently resolved hosting IP on selected date

Successful Responses

31

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.boundwork.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
31 2026-08-26 10:04 639233350067824371
64 ms 195.123.184.2
30 2026-08-26 09:47 639233339545274518
4081 ms 195.123.184.2
29 2026-08-26 09:29 639233329214918079
84 ms 195.123.184.2
28 2026-08-26 09:12 639233318749762337
54 ms 195.123.184.2
27 2026-08-26 08:54 639233308387917838
91 ms 195.123.184.2
26 2026-08-26 08:37 639233297961740122
67 ms 195.123.184.2
25 2026-08-26 08:20 639233287487159094
65 ms 195.123.184.2
24 2026-08-26 08:02 639233276995531707
50 ms 195.123.184.2
23 2026-08-26 07:45 639233266521568229
60 ms 195.123.184.2
22 2026-08-26 07:27 639233256081047431
69 ms 195.123.184.2
21 2026-08-26 06:33 639233223620132921
83 ms 195.123.184.2
20 2026-08-26 06:16 639233213287814244
57 ms 195.123.184.2
19 2026-08-26 05:59 639233202925983161
47 ms 195.123.184.2
18 2026-08-26 05:41 639233192644780696
4073 ms 195.123.184.2
17 2026-08-26 05:24 639233182401183833
82 ms 195.123.184.2
16 2026-08-26 05:07 639233172074181051
89 ms 195.123.184.2
15 2026-08-26 04:50 639233161808421455
92 ms 195.123.184.2
14 2026-08-26 04:33 639233151357344052
103 ms 195.123.184.2
13 2026-08-26 04:15 639233141034116946
133 ms 195.123.184.2
12 2026-08-26 03:58 639233130828334142
56 ms 195.123.184.2
11 2026-08-26 03:41 639233120373450007
94 ms 195.123.184.2
10 2026-08-26 03:24 639233110066216193
57 ms 195.123.184.2
9 2026-08-26 02:30 639233078065410564
49 ms 195.123.184.2
8 2026-08-26 02:13 639233067787457832
105 ms 195.123.184.2
7 2026-08-26 01:56 639233057501801162
50 ms 195.123.184.2
6 2026-08-26 01:39 639233047089431703
74 ms 195.123.184.2
5 2026-08-26 01:22 639233036754790688
46 ms 195.123.184.2
4 2026-08-26 01:05 639233026412602472
73 ms 195.123.184.2
3 2026-08-26 00:47 639233016064066127
120 ms 195.123.184.2
2 2026-08-26 00:30 639233005922655772
4079 ms 195.123.184.2
1 2026-08-26 00:13 639232995672256907
86 ms 195.123.184.2