DNS response history for ns2.trd2nft.com

ns2.trd2nft.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-28. For this date, NameServerHistory found 29 DNS check records, 29 successful responses, 0 failed responses, and 363 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.trd2nft.com.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

363 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-28 12:32

All timestamps shown in UTC

Latest Resolved IP on Selected Date

162.240.160.133

Most recently resolved hosting IP on selected date

Successful Responses

29

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.trd2nft.com

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
29 2026-08-28 12:32 639235163898672622
350 ms 162.240.160.133
28 2026-08-28 11:39 639235132147470568
596 ms 162.240.160.133
27 2026-08-28 11:22 639235121907744088
349 ms 162.240.160.133
26 2026-08-28 11:05 639235111428014262
350 ms 162.240.160.133
25 2026-08-28 10:47 639235100921813626
349 ms 162.240.160.133
24 2026-08-28 09:54 639235068670703481
345 ms 162.240.160.133
23 2026-08-28 09:36 639235058337459445
354 ms 162.240.160.133
22 2026-08-28 09:19 639235047825109146
357 ms 162.240.160.133
21 2026-08-28 09:01 639235037383229033
353 ms 162.240.160.133
20 2026-08-28 08:08 639235005619242711
371 ms 162.240.160.133
19 2026-08-28 07:51 639234995310346584
351 ms 162.240.160.133
18 2026-08-28 07:34 639234984946548933
347 ms 162.240.160.133
17 2026-08-28 07:17 639234974608077290
211 ms 162.240.160.133
16 2026-08-28 06:23 639234942529845595
349 ms 162.240.160.133
15 2026-08-28 06:06 639234932259126627
3 ms 162.240.160.133
14 2026-08-28 05:49 639234921916735988
351 ms 162.240.160.133
13 2026-08-28 05:32 639234911470038027
351 ms 162.240.160.133
12 2026-08-28 04:38 639234879588411654
347 ms 162.240.160.133
11 2026-08-28 04:21 639234869341589104
349 ms 162.240.160.133
10 2026-08-28 04:04 639234859012216675
358 ms 162.240.160.133
9 2026-08-28 03:47 639234848695364934
353 ms 162.240.160.133
8 2026-08-28 02:54 639234816952458162
347 ms 162.240.160.133
7 2026-08-28 02:37 639234806773081598
350 ms 162.240.160.133
6 2026-08-28 02:20 639234796382955255
353 ms 162.240.160.133
5 2026-08-28 02:02 639234786015782563
376 ms 162.240.160.133
4 2026-08-28 01:09 639234753811917646
421 ms 162.240.160.133
3 2026-08-28 00:52 639234743739767811
404 ms 162.240.160.133
2 2026-08-28 00:35 639234733372362811
732 ms 162.240.160.133
1 2026-08-28 00:17 639234723048550337
408 ms 162.240.160.133