DNS response history for ns3.yess.jp

ns3.yess.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-26. For this date, NameServerHistory found 27 DNS check records, 27 successful responses, 0 failed responses, and 338 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 ns3.yess.jp.
Records on Selected Date

27

Historical checks stored for this nameserver on selected date

Average Latency

338 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 08:43

All timestamps shown in UTC

Latest Resolved IP on Selected Date

133.18.105.76

Most recently resolved hosting IP on selected date

Successful Responses

27

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 ns3.yess.jp

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
27 2026-08-26 08:43 639233297961740122
263 ms 133.18.105.76
26 2026-08-26 08:25 639233287487159094
526 ms 133.18.105.76
25 2026-08-26 08:08 639233276995531707
281 ms 133.18.105.76
24 2026-08-26 07:50 639233266521568229
527 ms 133.18.105.76
23 2026-08-26 07:33 639233256081047431
28 ms 133.18.105.76
22 2026-08-26 06:39 639233223620132921
531 ms 133.18.105.76
21 2026-08-26 06:22 639233213287814244
527 ms 133.18.105.76
20 2026-08-26 06:04 639233202925983161
517 ms 133.18.105.76
19 2026-08-26 05:47 639233192644780696
509 ms 133.18.105.76
18 2026-08-26 05:30 639233182401183833
256 ms 133.18.105.76
17 2026-08-26 05:13 639233172074181051
538 ms 133.18.105.76
16 2026-08-26 04:56 639233161808421455
249 ms 133.18.105.76
15 2026-08-26 04:39 639233151357344052
527 ms 133.18.105.76
14 2026-08-26 04:21 639233141034116946
381 ms 133.18.105.76
13 2026-08-26 04:04 639233130828334142
510 ms 133.18.105.76
12 2026-08-26 03:47 639233120373450007
515 ms 133.18.105.76
11 2026-08-26 03:29 639233110066216193
254 ms 133.18.105.76
10 2026-08-26 02:36 639233078065410564
343 ms 133.18.105.76
9 2026-08-26 02:19 639233067787457832
8 ms 133.18.105.76
8 2026-08-26 02:02 639233057501801162
9 ms 133.18.105.76
7 2026-08-26 01:45 639233047089431703
279 ms 133.18.105.76
6 2026-08-26 01:27 639233036754790688
527 ms 133.18.105.76
5 2026-08-26 01:10 639233026412602472
511 ms 133.18.105.76
4 2026-08-26 00:53 639233016064066127
3 ms 133.18.105.76
3 2026-08-26 00:36 639233005922655772
256 ms 133.18.105.76
2 2026-08-26 00:19 639232995672256907
3 ms 133.18.105.76
1 2026-08-26 00:02 639232985300872416
251 ms 133.18.105.76