DNS response history for ns2.kobayashi.jprs

ns2.kobayashi.jprs 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 27 DNS check records, 27 successful responses, 0 failed responses, and 458 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.kobayashi.jprs.
Records on Selected Date

27

Historical checks stored for this nameserver on selected date

Average Latency

458 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 11:35

All timestamps shown in UTC

Latest Resolved IP on Selected Date

202.11.16.59

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 ns2.kobayashi.jprs

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
27 2026-08-24 11:35 639231673513573868
4 ms 202.11.16.59
26 2026-08-24 10:42 639231641791249939
237 ms 202.11.16.59
25 2026-08-24 10:26 639231631866211033
717 ms 202.11.16.59
24 2026-08-24 10:09 639231621644955316
4 ms 202.11.16.59
23 2026-08-24 09:52 639231611478799259
2 ms 202.11.16.59
22 2026-08-24 08:59 639231579923718211
4 ms 202.11.16.59
21 2026-08-24 08:43 639231569810702936
5 ms 202.11.16.59
20 2026-08-24 08:26 639231559762411619
242 ms 202.11.16.59
19 2026-08-24 08:09 639231549663595407
4489 ms 202.11.16.59
18 2026-08-24 07:16 639231518076817246
641 ms 202.11.16.59
17 2026-08-24 07:00 639231508078650885
3 ms 202.11.16.59
16 2026-08-24 06:43 639231498210697093
32 ms 202.11.16.59
15 2026-08-24 06:26 639231488109699360
5 ms 202.11.16.59
14 2026-08-24 05:34 639231456772510692
237 ms 202.11.16.59
13 2026-08-24 05:18 639231447084631185
925 ms 202.11.16.59
12 2026-08-24 05:01 639231437208519473
4 ms 202.11.16.59
11 2026-08-24 04:45 639231427209627490
238 ms 202.11.16.59
10 2026-08-24 03:52 639231395791246644
3 ms 202.11.16.59
9 2026-08-24 03:36 639231386075551458
4 ms 202.11.16.59
8 2026-08-24 03:20 639231376208713791
631 ms 202.11.16.59
7 2026-08-24 03:03 639231366170589276
1027 ms 202.11.16.59
6 2026-08-24 02:11 639231334732159368
3 ms 202.11.16.59
5 2026-08-24 01:54 639231325035670078
2007 ms 202.11.16.59
4 2026-08-24 01:38 639231315132253837
9 ms 202.11.16.59
3 2026-08-24 01:21 639231305014280808
304 ms 202.11.16.59
2 2026-08-24 00:29 639231273779380675
3 ms 202.11.16.59
1 2026-08-24 00:13 639231264180839154
581 ms 202.11.16.59