DNS response history for ns4.neobb.ne.jp

ns4.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-25. For this date, NameServerHistory found 28 DNS check records, 28 successful responses, 0 failed responses, and 483 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 ns4.neobb.ne.jp.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

483 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:46

All timestamps shown in UTC

Latest Resolved IP on Selected Date

61.206.7.68

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 ns4.neobb.ne.jp

Showing DNS history for 2026-08-25 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-25 09:46 639232471861770303
537 ms 61.206.7.68
27 2026-08-25 09:29 639232461630217327
315 ms 61.206.7.68
26 2026-08-25 09:12 639232451282965990
545 ms 61.206.7.68
25 2026-08-25 08:54 639232440814614938
539 ms 61.206.7.68
24 2026-08-25 08:37 639232430410720425
546 ms 61.206.7.68
23 2026-08-25 08:20 639232420003096185
298 ms 61.206.7.68
22 2026-08-25 08:02 639232409467287444
281 ms 61.206.7.68
21 2026-08-25 07:45 639232399077195997
543 ms 61.206.7.68
20 2026-08-25 07:27 639232388731528337
543 ms 61.206.7.68
19 2026-08-25 07:10 639232378288598612
546 ms 61.206.7.68
18 2026-08-25 06:16 639232346196373643
5 ms 61.206.7.68
17 2026-08-25 06:00 639232336112370741
2010 ms 61.206.7.68
16 2026-08-25 05:43 639232326146508970
559 ms 61.206.7.68
15 2026-08-25 05:26 639232316189381720
569 ms 61.206.7.68
14 2026-08-25 05:10 639232306217998913
3 ms 61.206.7.68
13 2026-08-25 04:53 639232296255744174
539 ms 61.206.7.68
12 2026-08-25 04:36 639232286095760789
3 ms 61.206.7.68
11 2026-08-25 04:19 639232276086186273
560 ms 61.206.7.68
10 2026-08-25 04:03 639232265900986425
541 ms 61.206.7.68
9 2026-08-25 03:46 639232255723518075
3 ms 61.206.7.68
8 2026-08-25 03:29 639232245484452890
518 ms 61.206.7.68
7 2026-08-25 03:12 639232235157175331
543 ms 61.206.7.68
6 2026-08-25 02:18 639232203197189095
390 ms 61.206.7.68
5 2026-08-25 02:01 639232192844564298
670 ms 61.206.7.68
4 2026-08-25 01:44 639232182496008942
797 ms 61.206.7.68
3 2026-08-25 01:27 639232172197053132
575 ms 61.206.7.68
2 2026-08-25 00:33 639232140250307418
3 ms 61.206.7.68
1 2026-08-25 00:16 639232129927860324
533 ms 61.206.7.68