DNS response history for ns2.tforce.link

ns2.tforce.link 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-28. For this date, NameServerHistory found 40 DNS check records, 40 successful responses, 0 failed responses, and 334 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.tforce.link.
Records on Selected Date

40

Historical checks stored for this nameserver on selected date

Average Latency

334 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-28 16:50

All timestamps shown in UTC

Latest Resolved IP on Selected Date

3.33.188.145

Most recently resolved hosting IP on selected date

Successful Responses

40

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.tforce.link

Showing DNS history for 2026-08-28 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
40 2026-08-28 16:50 639235322621629103
72 ms 3.33.188.145
39 2026-08-28 16:33 639235312230592801
16 ms 207.174.61.1
38 2026-08-28 16:16 639235301738139314
42 ms 207.174.61.1
37 2026-08-28 15:58 639235291168160936
24 ms 3.33.188.145
36 2026-08-28 15:04 639235258803654519
200 ms 3.33.188.145
35 2026-08-28 14:47 639235248596087996
155 ms 3.33.188.145
34 2026-08-28 14:30 639235238225955920
32 ms 3.33.188.145
33 2026-08-28 14:12 639235227727862105
131 ms 207.174.61.1
32 2026-08-28 13:18 639235195230848570
2033 ms 3.33.188.145
31 2026-08-28 13:01 639235184840503274
34 ms 3.33.188.145
30 2026-08-28 12:43 639235174453894956
40 ms 3.33.188.145
29 2026-08-28 12:26 639235163898672622
55 ms 3.33.188.145
28 2026-08-28 11:33 639235132147470568
209 ms 3.33.188.145
27 2026-08-28 11:16 639235121907744088
76 ms 3.33.188.145
26 2026-08-28 10:59 639235111428014262
30 ms 3.33.188.145
25 2026-08-28 10:41 639235100921813626
59 ms 3.33.188.145
24 2026-08-28 09:47 639235068670703481
91 ms 3.33.188.145
23 2026-08-28 09:30 639235058337459445
14 ms 3.33.188.145
22 2026-08-28 09:13 639235047825109146
16 ms 3.33.188.145
21 2026-08-28 08:55 639235037383229033
214 ms 3.33.188.145
20 2026-08-28 08:02 639235005619242711
82 ms 207.174.61.1
19 2026-08-28 07:45 639234995310346584
31 ms 3.33.188.145
18 2026-08-28 07:28 639234984946548933
2116 ms 207.174.61.1
17 2026-08-28 07:10 639234974608077290
27 ms 3.33.188.145
16 2026-08-28 06:17 639234942529845595
231 ms 3.33.188.145
15 2026-08-28 06:00 639234932259126627
29 ms 3.33.188.145
14 2026-08-28 05:43 639234921916735988
158 ms 3.33.188.145
13 2026-08-28 05:25 639234911470038027
39 ms 3.33.188.145
12 2026-08-28 04:32 639234879588411654
242 ms 3.33.188.145
11 2026-08-28 04:15 639234869341589104
4080 ms 207.174.61.1
10 2026-08-28 03:58 639234859012216675
33 ms 3.33.188.145
9 2026-08-28 03:40 639234848695364934
56 ms 3.33.188.145
8 2026-08-28 02:48 639234816952458162
45 ms 3.33.188.145
7 2026-08-28 02:31 639234806773081598
195 ms 3.33.188.145
6 2026-08-28 02:13 639234796382955255
34 ms 3.33.188.145
5 2026-08-28 01:56 639234786015782563
131 ms 207.174.61.1
4 2026-08-28 01:02 639234753811917646
26 ms 3.33.188.145
3 2026-08-28 00:46 639234743739767811
2029 ms 3.33.188.145
2 2026-08-28 00:28 639234733372362811
201 ms 3.33.188.145
1 2026-08-28 00:11 639234723048550337
30 ms 3.33.188.145