DNS response history for dns2.birth.ne.jp

dns2.birth.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-26. For this date, NameServerHistory found 27 DNS check records, 27 successful responses, 0 failed responses, and 589 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 dns2.birth.ne.jp.
Records on Selected Date

27

Historical checks stored for this nameserver on selected date

Average Latency

589 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 08:44

All timestamps shown in UTC

Latest Resolved IP on Selected Date

202.232.39.131

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 dns2.birth.ne.jp

Showing DNS history for 2026-08-26 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-26 08:44 639233297961740122
583 ms 202.232.39.131
26 2026-08-26 08:27 639233287487159094
573 ms 202.232.39.131
25 2026-08-26 08:09 639233276995531707
597 ms 202.232.39.131
24 2026-08-26 07:52 639233266521568229
596 ms 202.232.39.131
23 2026-08-26 07:34 639233256081047431
584 ms 202.232.39.131
22 2026-08-26 06:40 639233223620132921
596 ms 202.232.39.131
21 2026-08-26 06:23 639233213287814244
574 ms 202.232.39.131
20 2026-08-26 06:06 639233202925983161
555 ms 202.232.39.131
19 2026-08-26 05:48 639233192644780696
577 ms 202.232.39.131
18 2026-08-26 05:31 639233182401183833
555 ms 202.232.39.131
17 2026-08-26 05:14 639233172074181051
590 ms 202.232.39.131
16 2026-08-26 04:57 639233161808421455
622 ms 202.232.39.131
15 2026-08-26 04:40 639233151357344052
600 ms 202.232.39.131
14 2026-08-26 04:22 639233141034116946
623 ms 202.232.39.131
13 2026-08-26 04:05 639233130828334142
578 ms 202.232.39.131
12 2026-08-26 03:48 639233120373450007
616 ms 202.232.39.131
11 2026-08-26 03:31 639233110066216193
578 ms 202.232.39.131
10 2026-08-26 02:38 639233078065410564
569 ms 202.232.39.131
9 2026-08-26 02:20 639233067787457832
562 ms 202.232.39.131
8 2026-08-26 02:03 639233057501801162
564 ms 202.232.39.131
7 2026-08-26 01:46 639233047089431703
560 ms 202.232.39.131
6 2026-08-26 01:29 639233036754790688
564 ms 202.232.39.131
5 2026-08-26 01:12 639233026412602472
598 ms 202.232.39.131
4 2026-08-26 00:54 639233016064066127
568 ms 202.232.39.131
3 2026-08-26 00:37 639233005922655772
554 ms 202.232.39.131
2 2026-08-26 00:20 639232995672256907
574 ms 202.232.39.131
1 2026-08-26 00:03 639232985300872416
793 ms 202.232.39.131