DNS response history for www3.t-rex.co.jp

www3.t-rex.co.jp 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-27. For this date, NameServerHistory found 29 DNS check records, 29 successful responses, 0 failed responses, and 588 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 www3.t-rex.co.jp.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

588 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 09:33

All timestamps shown in UTC

Latest Resolved IP on Selected Date

117.120.50.79

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 www3.t-rex.co.jp

Showing DNS history for 2026-08-27 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-27 09:33 639234191649612722
564 ms 117.120.50.79
28 2026-08-27 09:16 639234181105879568
574 ms 117.120.50.79
27 2026-08-27 08:58 639234170713214496
573 ms 117.120.50.79
26 2026-08-27 08:41 639234160341037652
709 ms 117.120.50.79
25 2026-08-27 08:24 639234149799404224
576 ms 117.120.50.79
24 2026-08-27 08:06 639234139553286469
828 ms 117.120.50.79
23 2026-08-27 07:12 639234107183588293
570 ms 117.120.50.79
22 2026-08-27 06:55 639234096905435724
553 ms 117.120.50.79
21 2026-08-27 06:38 639234086579410775
588 ms 117.120.50.79
20 2026-08-27 06:21 639234076291157956
5 ms 117.120.50.79
19 2026-08-27 06:04 639234065981939454
816 ms 117.120.50.79
18 2026-08-27 05:47 639234055548642997
578 ms 117.120.50.79
17 2026-08-27 05:29 639234045267979603
799 ms 117.120.50.79
16 2026-08-27 05:12 639234034999717463
594 ms 117.120.50.79
15 2026-08-27 04:55 639234024739225358
534 ms 117.120.50.79
14 2026-08-27 04:38 639234014311170162
552 ms 117.120.50.79
13 2026-08-27 04:20 639234003806017640
580 ms 117.120.50.79
12 2026-08-27 04:03 639233993356203030
573 ms 117.120.50.79
11 2026-08-27 03:09 639233961301716608
597 ms 117.120.50.79
10 2026-08-27 02:52 639233950834200647
574 ms 117.120.50.79
9 2026-08-27 02:35 639233940431849026
579 ms 117.120.50.79
8 2026-08-27 02:17 639233930110596398
552 ms 117.120.50.79
7 2026-08-27 02:00 639233919705434540
788 ms 117.120.50.79
6 2026-08-27 01:43 639233909452807845
557 ms 117.120.50.79
5 2026-08-27 01:26 639233899096420820
558 ms 117.120.50.79
4 2026-08-27 01:08 639233888707824939
555 ms 117.120.50.79
3 2026-08-27 00:51 639233878461203802
574 ms 117.120.50.79
2 2026-08-27 00:34 639233868060868209
556 ms 117.120.50.79
1 2026-08-27 00:17 639233857450922991
595 ms 117.120.50.79