DNS response history for ns2.thamesideclubhouse.com

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

39

Historical checks stored for this nameserver on selected date

Average Latency

273 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:55

All timestamps shown in UTC

Latest Resolved IP on Selected Date

38.180.65.129

Most recently resolved hosting IP on selected date

Successful Responses

39

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.thamesideclubhouse.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
39 2026-08-26 12:55 639233455747096265
75 ms 38.180.65.129
38 2026-08-26 12:38 639233445367152284
47 ms 38.180.65.129
37 2026-08-26 12:21 639233434974187439
118 ms 38.180.65.129
36 2026-08-26 12:03 639233424567558554
54 ms 38.180.65.129
35 2026-08-26 11:46 639233414056832719
81 ms 38.180.65.129
34 2026-08-26 11:28 639233403515141099
79 ms 38.180.65.129
33 2026-08-26 10:34 639233370841350248
55 ms 38.180.65.129
32 2026-08-26 10:16 639233360361507238
57 ms 38.180.65.129
31 2026-08-26 09:59 639233350067824371
65 ms 38.180.65.129
30 2026-08-26 09:42 639233339545274518
75 ms 38.180.65.129
29 2026-08-26 09:25 639233329214918079
149 ms 38.180.65.129
28 2026-08-26 09:07 639233318749762337
97 ms 38.180.65.129
27 2026-08-26 08:50 639233308387917838
61 ms 38.180.65.129
26 2026-08-26 08:32 639233297961740122
67 ms 38.180.65.129
25 2026-08-26 08:15 639233287487159094
28 ms 38.180.65.129
24 2026-08-26 07:57 639233276995531707
64 ms 38.180.65.129
23 2026-08-26 07:40 639233266521568229
68 ms 38.180.65.129
22 2026-08-26 07:23 639233256081047431
88 ms 38.180.65.129
21 2026-08-26 06:28 639233223620132921
64 ms 38.180.65.129
20 2026-08-26 06:11 639233213287814244
167 ms 38.180.65.129
19 2026-08-26 05:54 639233202925983161
52 ms 38.180.65.129
18 2026-08-26 05:37 639233192644780696
36 ms 38.180.65.129
17 2026-08-26 05:20 639233182401183833
92 ms 38.180.65.129
16 2026-08-26 05:03 639233172074181051
85 ms 38.180.65.129
15 2026-08-26 04:45 639233161808421455
90 ms 38.180.65.129
14 2026-08-26 04:28 639233151357344052
2071 ms 38.180.65.129
13 2026-08-26 04:11 639233141034116946
36 ms 38.180.65.129
12 2026-08-26 03:54 639233130828334142
12 ms 38.180.65.129
11 2026-08-26 03:36 639233120373450007
28 ms 38.180.65.129
10 2026-08-26 03:19 639233110066216193
65 ms 38.180.65.129
9 2026-08-26 02:26 639233078065410564
36 ms 38.180.65.129
8 2026-08-26 02:09 639233067787457832
8 ms 38.180.65.129
7 2026-08-26 01:52 639233057501801162
4043 ms 38.180.65.129
6 2026-08-26 01:34 639233047089431703
157 ms 38.180.65.129
5 2026-08-26 01:17 639233036754790688
50 ms 38.180.65.129
4 2026-08-26 01:00 639233026412602472
73 ms 38.180.65.129
3 2026-08-26 00:43 639233016064066127
2028 ms 38.180.65.129
2 2026-08-26 00:26 639233005922655772
60 ms 38.180.65.129
1 2026-08-26 00:09 639232995672256907
72 ms 38.180.65.129