DNS response history for ns2.terasynctech.com

ns2.terasynctech.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 34 DNS check records, 28 successful responses, 6 failed responses, and 458 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.terasynctech.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

458 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:36

All timestamps shown in UTC

Latest Resolved IP on Selected Date

64.235.33.56

Most recently resolved hosting IP on selected date

Successful Responses

28

Checks that returned a measurable response

Failed Responses

6

Checks with no response or no returned latency

Failure Rate

18%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.terasynctech.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
34 2026-08-26 11:36 639233403515141099
33 ms 64.235.33.56
33 2026-08-26 10:41 639233370841350248
2055 ms 64.235.33.56
32 2026-08-26 10:24 639233360361507238
34 ms 64.235.33.56
31 2026-08-26 10:06 639233350067824371
41 ms 64.235.33.56
30 2026-08-26 09:49 639233339545274518
-
29 2026-08-26 09:32 639233329214918079
2011 ms 64.235.33.56
28 2026-08-26 09:14 639233318749762337
2033 ms 64.235.33.56
27 2026-08-26 08:57 639233308387917838
38 ms 64.235.33.56
26 2026-08-26 08:40 639233297961740122
32 ms 64.235.33.56
25 2026-08-26 08:22 639233287487159094
2019 ms 64.235.33.56
24 2026-08-26 08:05 639233276995531707
51 ms 64.235.33.56
23 2026-08-26 07:47 639233266521568229
34 ms 64.235.33.56
22 2026-08-26 07:30 639233256081047431
36 ms 64.235.33.56
21 2026-08-26 06:36 639233223620132921
3 ms 64.235.33.56
20 2026-08-26 06:19 639233213287814244
38 ms 64.235.33.56
19 2026-08-26 06:01 639233202925983161
34 ms 64.235.33.56
18 2026-08-26 05:44 639233192644780696
3 ms 64.235.33.56
17 2026-08-26 05:27 639233182401183833
124 ms 64.235.33.56
16 2026-08-26 05:10 639233172074181051
4 ms 64.235.33.56
15 2026-08-26 04:53 639233161808421455
2 ms 64.235.33.56
14 2026-08-26 04:35 639233151357344052
37 ms 64.235.33.56
13 2026-08-26 04:18 639233141034116946
18 ms 64.235.33.56
12 2026-08-26 04:01 639233130828334142
19 ms 64.235.33.56
11 2026-08-26 03:44 639233120373450007
19 ms 64.235.33.56
10 2026-08-26 03:26 639233110066216193
19 ms 64.235.33.56
9 2026-08-26 02:33 639233078065410564
35 ms 64.235.33.56
8 2026-08-26 02:16 639233067787457832
18 ms 64.235.33.56
7 2026-08-26 01:59 639233057501801162
-
6 2026-08-26 01:42 639233047089431703
-
5 2026-08-26 01:24 639233036754790688
2007 ms 64.235.33.56
4 2026-08-26 01:07 639233026412602472
-
3 2026-08-26 00:50 639233016064066127
2033 ms 64.235.33.56
2 2026-08-26 00:33 639233005922655772
-
1 2026-08-26 00:16 639232995672256907
-