DNS response history for ns2.terabyte-computing.com

ns2.terabyte-computing.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 36 DNS check records, 36 successful responses, 0 failed responses, and 330 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.terabyte-computing.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

330 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:08

All timestamps shown in UTC

Latest Resolved IP on Selected Date

93.186.146.122

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.terabyte-computing.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
36 2026-08-26 12:08 639233424567558554
70 ms 93.186.146.122
35 2026-08-26 11:51 639233414056832719
75 ms 93.186.146.122
34 2026-08-26 11:33 639233403515141099
72 ms 93.186.146.122
33 2026-08-26 10:38 639233370841350248
85 ms 93.186.146.122
32 2026-08-26 10:21 639233360361507238
75 ms 93.186.146.122
31 2026-08-26 10:04 639233350067824371
255 ms 93.186.146.122
30 2026-08-26 09:47 639233339545274518
77 ms 93.186.146.122
29 2026-08-26 09:29 639233329214918079
46 ms 93.186.146.122
28 2026-08-26 09:12 639233318749762337
138 ms 93.186.146.122
27 2026-08-26 08:55 639233308387917838
173 ms 93.186.146.122
26 2026-08-26 08:37 639233297961740122
158 ms 93.186.146.122
25 2026-08-26 08:20 639233287487159094
2160 ms 93.186.146.122
24 2026-08-26 08:02 639233276995531707
71 ms 93.186.146.122
23 2026-08-26 07:45 639233266521568229
2138 ms 93.186.146.122
22 2026-08-26 07:27 639233256081047431
114 ms 93.186.146.122
21 2026-08-26 06:33 639233223620132921
73 ms 93.186.146.122
20 2026-08-26 06:16 639233213287814244
84 ms 93.186.146.122
19 2026-08-26 05:59 639233202925983161
204 ms 93.186.146.122
18 2026-08-26 05:42 639233192644780696
125 ms 93.186.146.122
17 2026-08-26 05:24 639233182401183833
91 ms 93.186.146.122
16 2026-08-26 05:07 639233172074181051
2137 ms 93.186.146.122
15 2026-08-26 04:50 639233161808421455
114 ms 93.186.146.122
14 2026-08-26 04:33 639233151357344052
183 ms 93.186.146.122
13 2026-08-26 04:16 639233141034116946
73 ms 93.186.146.122
12 2026-08-26 03:59 639233130828334142
87 ms 93.186.146.122
11 2026-08-26 03:41 639233120373450007
76 ms 93.186.146.122
10 2026-08-26 03:24 639233110066216193
81 ms 93.186.146.122
9 2026-08-26 02:31 639233078065410564
2204 ms 93.186.146.122
8 2026-08-26 02:14 639233067787457832
53 ms 93.186.146.122
7 2026-08-26 01:56 639233057501801162
162 ms 93.186.146.122
6 2026-08-26 01:39 639233047089431703
84 ms 93.186.146.122
5 2026-08-26 01:22 639233036754790688
70 ms 93.186.146.122
4 2026-08-26 01:05 639233026412602472
71 ms 93.186.146.122
3 2026-08-26 00:47 639233016064066127
81 ms 93.186.146.122
2 2026-08-26 00:30 639233005922655772
74 ms 93.186.146.122
1 2026-08-26 00:13 639232995672256907
54 ms 93.186.146.122