DNS response history for ns2.t-computing.com

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

32

Historical checks stored for this nameserver on selected date

Average Latency

173 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:20

All timestamps shown in UTC

Latest Resolved IP on Selected Date

213.133.105.6

Most recently resolved hosting IP on selected date

Successful Responses

32

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.t-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
32 2026-08-26 10:20 639233360361507238
69 ms 213.133.105.6
31 2026-08-26 10:02 639233350067824371
59 ms 213.133.105.6
30 2026-08-26 09:45 639233339545274518
41 ms 213.133.105.6
29 2026-08-26 09:28 639233329214918079
51 ms 213.133.105.6
28 2026-08-26 09:10 639233318749762337
59 ms 213.133.105.6
27 2026-08-26 08:53 639233308387917838
9 ms 213.133.105.6
26 2026-08-26 08:35 639233297961740122
133 ms 213.133.105.6
25 2026-08-26 08:18 639233287487159094
2041 ms 213.133.105.6
24 2026-08-26 08:01 639233276995531707
22 ms 213.133.105.6
23 2026-08-26 07:43 639233266521568229
63 ms 213.133.105.6
22 2026-08-26 07:26 639233256081047431
64 ms 213.133.105.6
21 2026-08-26 06:32 639233223620132921
64 ms 213.133.105.6
20 2026-08-26 06:14 639233213287814244
59 ms 213.133.105.6
19 2026-08-26 05:57 639233202925983161
41 ms 213.133.105.6
18 2026-08-26 05:40 639233192644780696
29 ms 213.133.105.6
17 2026-08-26 05:23 639233182401183833
34 ms 213.133.105.6
16 2026-08-26 05:06 639233172074181051
50 ms 213.133.105.6
15 2026-08-26 04:49 639233161808421455
21 ms 213.133.105.6
14 2026-08-26 04:31 639233151357344052
39 ms 213.133.105.6
13 2026-08-26 04:14 639233141034116946
93 ms 213.133.105.6
12 2026-08-26 03:57 639233130828334142
2063 ms 213.133.105.6
11 2026-08-26 03:40 639233120373450007
30 ms 213.133.105.6
10 2026-08-26 03:22 639233110066216193
61 ms 213.133.105.6
9 2026-08-26 02:29 639233078065410564
35 ms 213.133.105.6
8 2026-08-26 02:12 639233067787457832
52 ms 213.133.105.6
7 2026-08-26 01:55 639233057501801162
33 ms 213.133.105.6
6 2026-08-26 01:37 639233047089431703
38 ms 213.133.105.6
5 2026-08-26 01:20 639233036754790688
33 ms 213.133.105.6
4 2026-08-26 01:03 639233026412602472
63 ms 213.133.105.6
3 2026-08-26 00:46 639233016064066127
9 ms 213.133.105.6
2 2026-08-26 00:29 639233005922655772
52 ms 213.133.105.6
1 2026-08-26 00:12 639232995672256907
29 ms 213.133.105.6