DNS response history for bose.ccmp.jp

bose.ccmp.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 33 DNS check records, 33 successful responses, 0 failed responses, and 537 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 bose.ccmp.jp.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

537 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:33

All timestamps shown in UTC

Latest Resolved IP on Selected Date

133.125.34.195

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 bose.ccmp.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
33 2026-08-25 11:33 639232535349285207
536 ms 133.125.34.195
32 2026-08-25 11:16 639232524938080723
254 ms 133.125.34.195
31 2026-08-25 10:22 639232492740373468
798 ms 133.125.34.195
30 2026-08-25 10:05 639232482235303141
544 ms 133.125.34.195
29 2026-08-25 09:47 639232471861770303
513 ms 133.125.34.195
28 2026-08-25 09:30 639232461630217327
538 ms 133.125.34.195
27 2026-08-25 09:13 639232451282965990
549 ms 133.125.34.195
26 2026-08-25 08:56 639232440814614938
544 ms 133.125.34.195
25 2026-08-25 08:38 639232430410720425
536 ms 133.125.34.195
24 2026-08-25 08:21 639232420003096185
553 ms 133.125.34.195
23 2026-08-25 08:04 639232409467287444
556 ms 133.125.34.195
22 2026-08-25 07:46 639232399077195997
777 ms 133.125.34.195
21 2026-08-25 07:29 639232388731528337
534 ms 133.125.34.195
20 2026-08-25 07:11 639232378288598612
542 ms 133.125.34.195
19 2026-08-25 06:18 639232346196373643
529 ms 133.125.34.195
18 2026-08-25 06:01 639232336112370741
522 ms 133.125.34.195
17 2026-08-25 05:44 639232326146508970
548 ms 133.125.34.195
16 2026-08-25 05:27 639232316189381720
253 ms 133.125.34.195
15 2026-08-25 05:11 639232306217998913
540 ms 133.125.34.195
14 2026-08-25 04:54 639232296255744174
544 ms 133.125.34.195
13 2026-08-25 04:37 639232286095760789
540 ms 133.125.34.195
12 2026-08-25 04:21 639232276086186273
523 ms 133.125.34.195
11 2026-08-25 04:04 639232265900986425
543 ms 133.125.34.195
10 2026-08-25 03:47 639232255723518075
548 ms 133.125.34.195
9 2026-08-25 03:30 639232245484452890
533 ms 133.125.34.195
8 2026-08-25 03:13 639232235157175331
546 ms 133.125.34.195
7 2026-08-25 02:19 639232203197189095
533 ms 133.125.34.195
6 2026-08-25 02:02 639232192844564298
542 ms 133.125.34.195
5 2026-08-25 01:45 639232182496008942
538 ms 133.125.34.195
4 2026-08-25 01:28 639232172197053132
547 ms 133.125.34.195
3 2026-08-25 00:34 639232140250307418
533 ms 133.125.34.195
2 2026-08-25 00:18 639232129927860324
537 ms 133.125.34.195
1 2026-08-25 00:00 639232119551972438
547 ms 133.125.34.195