DNS response history for ns2.terrabet.win

ns2.terrabet.win 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 36 DNS check records, 36 successful responses, 0 failed responses, and 270 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.terrabet.win.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

270 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:06

All timestamps shown in UTC

Latest Resolved IP on Selected Date

192.142.0.100

Most recently resolved hosting IP on selected date

Successful Responses

36

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.terrabet.win

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
36 2026-08-26 12:06 639233424567558554
66 ms 192.142.0.100
35 2026-08-26 11:48 639233414056832719
32 ms 84.201.6.137
34 2026-08-26 11:31 639233403515141099
35 ms 195.54.174.165
33 2026-08-26 10:36 639233370841350248
54 ms 195.54.174.165
32 2026-08-26 10:19 639233360361507238
27 ms 195.54.174.165
31 2026-08-26 10:01 639233350067824371
47 ms 195.54.174.165
30 2026-08-26 09:44 639233339545274518
53 ms 192.142.0.100
29 2026-08-26 09:27 639233329214918079
58 ms 192.142.0.100
28 2026-08-26 09:09 639233318749762337
56 ms 195.54.174.165
27 2026-08-26 08:52 639233308387917838
37 ms 195.54.174.165
26 2026-08-26 08:35 639233297961740122
37 ms 192.142.0.100
25 2026-08-26 08:17 639233287487159094
138 ms 195.54.174.165
24 2026-08-26 08:00 639233276995531707
175 ms 195.54.174.165
23 2026-08-26 07:42 639233266521568229
32 ms 84.201.6.137
22 2026-08-26 07:25 639233256081047431
61 ms 195.54.174.165
21 2026-08-26 06:31 639233223620132921
44 ms 195.54.174.165
20 2026-08-26 06:14 639233213287814244
30 ms 195.54.174.165
19 2026-08-26 05:56 639233202925983161
189 ms 84.201.6.137
18 2026-08-26 05:39 639233192644780696
58 ms 192.142.0.100
17 2026-08-26 05:22 639233182401183833
35 ms 195.54.174.165
16 2026-08-26 05:05 639233172074181051
30 ms 195.54.174.165
15 2026-08-26 04:48 639233161808421455
39 ms 195.54.174.165
14 2026-08-26 04:30 639233151357344052
173 ms 195.54.174.165
13 2026-08-26 04:13 639233141034116946
31 ms 195.54.174.165
12 2026-08-26 03:56 639233130828334142
37 ms 195.54.174.165
11 2026-08-26 03:39 639233120373450007
62 ms 195.54.174.165
10 2026-08-26 03:21 639233110066216193
53 ms 195.54.174.165
9 2026-08-26 02:28 639233078065410564
59 ms 192.142.0.100
8 2026-08-26 02:11 639233067787457832
26 ms 84.201.6.137
7 2026-08-26 01:54 639233057501801162
2034 ms 84.201.6.137
6 2026-08-26 01:37 639233047089431703
2030 ms 195.54.174.165
5 2026-08-26 01:19 639233036754790688
18 ms 84.201.6.137
4 2026-08-26 01:02 639233026412602472
103 ms 192.142.0.100
3 2026-08-26 00:45 639233016064066127
76 ms 192.142.0.100
2 2026-08-26 00:28 639233005922655772
3604 ms 192.142.0.100
1 2026-08-26 00:11 639232995672256907
71 ms 192.142.0.100