DNS response history for ns1.neobb.ne.jp

ns1.neobb.ne.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 28 DNS check records, 28 successful responses, 0 failed responses, and 477 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 ns1.neobb.ne.jp.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

477 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 11:52

All timestamps shown in UTC

Latest Resolved IP on Selected Date

61.206.7.67

Most recently resolved hosting IP on selected date

Successful Responses

28

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 ns1.neobb.ne.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
28 2026-08-24 11:52 639231683712487276
11 ms 61.206.7.67
27 2026-08-24 11:35 639231673513573868
3 ms 61.206.7.67
26 2026-08-24 10:42 639231641791249939
281 ms 61.206.7.67
25 2026-08-24 10:26 639231631866211033
538 ms 61.206.7.67
24 2026-08-24 10:09 639231621644955316
518 ms 61.206.7.67
23 2026-08-24 09:52 639231611478799259
279 ms 61.206.7.67
22 2026-08-24 08:59 639231579923718211
290 ms 61.206.7.67
21 2026-08-24 08:43 639231569810702936
275 ms 61.206.7.67
20 2026-08-24 08:26 639231559762411619
518 ms 61.206.7.67
19 2026-08-24 08:09 639231549663595407
545 ms 61.206.7.67
18 2026-08-24 07:16 639231518076817246
4 ms 61.206.7.67
17 2026-08-24 07:00 639231508078650885
4 ms 61.206.7.67
16 2026-08-24 06:43 639231498210697093
3 ms 61.206.7.67
15 2026-08-24 06:26 639231488109699360
504 ms 61.206.7.67
14 2026-08-24 05:34 639231456772510692
540 ms 61.206.7.67
13 2026-08-24 05:18 639231447084631185
279 ms 61.206.7.67
12 2026-08-24 05:01 639231437208519473
297 ms 61.206.7.67
11 2026-08-24 04:45 639231427209627490
538 ms 61.206.7.67
10 2026-08-24 03:52 639231395791246644
530 ms 61.206.7.67
9 2026-08-24 03:36 639231386075551458
532 ms 61.206.7.67
8 2026-08-24 03:20 639231376208713791
531 ms 61.206.7.67
7 2026-08-24 03:03 639231366170589276
2258 ms 61.206.7.67
6 2026-08-24 02:11 639231334732159368
3 ms 61.206.7.67
5 2026-08-24 01:54 639231325035670078
287 ms 61.206.7.67
4 2026-08-24 01:38 639231315132253837
531 ms 61.206.7.67
3 2026-08-24 01:21 639231305014280808
2446 ms 61.206.7.67
2 2026-08-24 00:29 639231273779380675
528 ms 61.206.7.67
1 2026-08-24 00:13 639231264180839154
275 ms 61.206.7.67