DNS response history for ns.rcc.co.jp

ns.rcc.co.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 29 DNS check records, 29 successful responses, 0 failed responses, and 544 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 ns.rcc.co.jp.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

544 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:47

All timestamps shown in UTC

Latest Resolved IP on Selected Date

210.160.44.1

Most recently resolved hosting IP on selected date

Successful Responses

29

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 ns.rcc.co.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
29 2026-08-25 09:47 639232471861770303
532 ms 210.160.44.1
28 2026-08-25 09:30 639232461630217327
563 ms 210.160.44.1
27 2026-08-25 09:13 639232451282965990
1113 ms 210.160.44.1
26 2026-08-25 08:55 639232440814614938
3 ms 210.160.44.1
25 2026-08-25 08:38 639232430410720425
536 ms 210.160.44.1
24 2026-08-25 08:21 639232420003096185
552 ms 210.160.44.1
23 2026-08-25 08:03 639232409467287444
547 ms 210.160.44.1
22 2026-08-25 07:46 639232399077195997
537 ms 210.160.44.1
21 2026-08-25 07:28 639232388731528337
902 ms 210.160.44.1
20 2026-08-25 07:11 639232378288598612
527 ms 210.160.44.1
19 2026-08-25 06:17 639232346196373643
524 ms 210.160.44.1
18 2026-08-25 06:00 639232336112370741
529 ms 210.160.44.1
17 2026-08-25 05:44 639232326146508970
7 ms 210.160.44.1
16 2026-08-25 05:27 639232316189381720
542 ms 210.160.44.1
15 2026-08-25 05:11 639232306217998913
3 ms 210.160.44.1
14 2026-08-25 04:54 639232296255744174
498 ms 210.160.44.1
13 2026-08-25 04:37 639232286095760789
528 ms 210.160.44.1
12 2026-08-25 04:20 639232276086186273
526 ms 210.160.44.1
11 2026-08-25 04:04 639232265900986425
510 ms 210.160.44.1
10 2026-08-25 03:47 639232255723518075
550 ms 210.160.44.1
9 2026-08-25 03:30 639232245484452890
527 ms 210.160.44.1
8 2026-08-25 03:13 639232235157175331
528 ms 210.160.44.1
7 2026-08-25 02:19 639232203197189095
1279 ms 210.160.44.1
6 2026-08-25 02:02 639232192844564298
521 ms 210.160.44.1
5 2026-08-25 01:45 639232182496008942
522 ms 210.160.44.1
4 2026-08-25 01:27 639232172197053132
1029 ms 210.160.44.1
3 2026-08-25 00:34 639232140250307418
534 ms 210.160.44.1
2 2026-08-25 00:17 639232129927860324
529 ms 210.160.44.1
1 2026-08-25 00:00 639232119551972438
264 ms 210.160.44.1