DNS response history for ns2.streaming.jp

ns2.streaming.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-24. For this date, NameServerHistory found 33 DNS check records, 33 successful responses, 0 failed responses, and 593 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.streaming.jp.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

593 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 13:54

All timestamps shown in UTC

Latest Resolved IP on Selected Date

153.120.4.229

Most recently resolved hosting IP on selected date

Successful Responses

33

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.streaming.jp

Showing DNS history for 2026-08-24 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
33 2026-08-24 13:54 639231755868832964
526 ms 153.120.4.229
32 2026-08-24 13:37 639231745628278877
537 ms 153.120.4.229
31 2026-08-24 13:19 639231735407682062
556 ms 153.120.4.229
30 2026-08-24 12:27 639231703815441688
550 ms 153.120.4.229
29 2026-08-24 12:10 639231693747052549
536 ms 153.120.4.229
28 2026-08-24 11:53 639231683712487276
735 ms 153.120.4.229
27 2026-08-24 11:36 639231673513573868
529 ms 153.120.4.229
26 2026-08-24 10:43 639231641791249939
563 ms 153.120.4.229
25 2026-08-24 10:27 639231631866211033
553 ms 153.120.4.229
24 2026-08-24 10:10 639231621644955316
534 ms 153.120.4.229
23 2026-08-24 09:53 639231611478799259
540 ms 153.120.4.229
22 2026-08-24 09:00 639231579923718211
558 ms 153.120.4.229
21 2026-08-24 08:44 639231569810702936
550 ms 153.120.4.229
20 2026-08-24 08:27 639231559762411619
537 ms 153.120.4.229
19 2026-08-24 08:10 639231549663595407
559 ms 153.120.4.229
18 2026-08-24 07:17 639231518076817246
584 ms 153.120.4.229
17 2026-08-24 07:01 639231508078650885
569 ms 153.120.4.229
16 2026-08-24 06:44 639231498210697093
549 ms 153.120.4.229
15 2026-08-24 06:27 639231488109699360
582 ms 153.120.4.229
14 2026-08-24 05:35 639231456772510692
2400 ms 153.120.4.229
13 2026-08-24 05:19 639231447084631185
533 ms 153.120.4.229
12 2026-08-24 05:02 639231437208519473
526 ms 153.120.4.229
11 2026-08-24 04:46 639231427209627490
537 ms 153.120.4.229
10 2026-08-24 03:53 639231395791246644
544 ms 153.120.4.229
9 2026-08-24 03:37 639231386075551458
376 ms 153.120.4.229
8 2026-08-24 03:21 639231376208713791
267 ms 153.120.4.229
7 2026-08-24 03:04 639231366170589276
563 ms 153.120.4.229
6 2026-08-24 02:12 639231334732159368
426 ms 153.120.4.229
5 2026-08-24 01:55 639231325035670078
541 ms 153.120.4.229
4 2026-08-24 01:39 639231315132253837
574 ms 153.120.4.229
3 2026-08-24 01:22 639231305014280808
554 ms 153.120.4.229
2 2026-08-24 00:30 639231273779380675
535 ms 153.120.4.229
1 2026-08-24 00:14 639231264180839154
537 ms 153.120.4.229