DNS response history for ns2.transcurrents.com

ns2.transcurrents.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, 34 successful responses, 0 failed responses, and 224 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.transcurrents.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

224 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:35

All timestamps shown in UTC

Latest Resolved IP on Selected Date

78.46.105.27

Most recently resolved hosting IP on selected date

Successful Responses

34

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.transcurrents.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:35 639233403515141099
241 ms 78.46.105.27
33 2026-08-26 10:41 639233370841350248
115 ms 78.46.105.27
32 2026-08-26 10:23 639233360361507238
228 ms 78.46.105.27
31 2026-08-26 10:06 639233350067824371
21 ms 78.46.105.27
30 2026-08-26 09:49 639233339545274518
2008 ms 78.46.105.27
29 2026-08-26 09:31 639233329214918079
224 ms 78.46.105.27
28 2026-08-26 09:14 639233318749762337
162 ms 78.46.105.27
27 2026-08-26 08:57 639233308387917838
227 ms 78.46.105.27
26 2026-08-26 08:39 639233297961740122
149 ms 78.46.105.27
25 2026-08-26 08:22 639233287487159094
219 ms 78.46.105.27
24 2026-08-26 08:05 639233276995531707
109 ms 78.46.105.27
23 2026-08-26 07:47 639233266521568229
231 ms 78.46.105.27
22 2026-08-26 07:29 639233256081047431
128 ms 78.46.105.27
21 2026-08-26 06:36 639233223620132921
144 ms 78.46.105.27
20 2026-08-26 06:18 639233213287814244
117 ms 78.46.105.27
19 2026-08-26 06:01 639233202925983161
229 ms 78.46.105.27
18 2026-08-26 05:44 639233192644780696
221 ms 78.46.105.27
17 2026-08-26 05:27 639233182401183833
227 ms 78.46.105.27
16 2026-08-26 05:10 639233172074181051
223 ms 78.46.105.27
15 2026-08-26 04:52 639233161808421455
220 ms 78.46.105.27
14 2026-08-26 04:35 639233151357344052
114 ms 78.46.105.27
13 2026-08-26 04:18 639233141034116946
129 ms 78.46.105.27
12 2026-08-26 04:01 639233130828334142
226 ms 78.46.105.27
11 2026-08-26 03:43 639233120373450007
110 ms 78.46.105.27
10 2026-08-26 03:26 639233110066216193
116 ms 78.46.105.27
9 2026-08-26 02:33 639233078065410564
221 ms 78.46.105.27
8 2026-08-26 02:16 639233067787457832
123 ms 78.46.105.27
7 2026-08-26 01:58 639233057501801162
217 ms 78.46.105.27
6 2026-08-26 01:41 639233047089431703
228 ms 78.46.105.27
5 2026-08-26 01:24 639233036754790688
219 ms 78.46.105.27
4 2026-08-26 01:07 639233026412602472
7 ms 78.46.105.27
3 2026-08-26 00:49 639233016064066127
124 ms 78.46.105.27
2 2026-08-26 00:32 639233005922655772
225 ms 78.46.105.27
1 2026-08-26 00:15 639232995672256907
110 ms 78.46.105.27