DNS response history for br29.eigyo.co.jp

br29.eigyo.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 32 DNS check records, 32 successful responses, 0 failed responses, and 387 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 br29.eigyo.co.jp.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

387 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

210.233.79.83

Most recently resolved hosting IP on selected date

Successful Responses

32

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 br29.eigyo.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
32 2026-08-25 11:33 639232535349285207
552 ms 210.233.79.83
31 2026-08-25 11:15 639232524938080723
551 ms 210.233.79.83
30 2026-08-25 10:21 639232492740373468
541 ms 210.233.79.83
29 2026-08-25 10:04 639232482235303141
3 ms 210.233.79.83
28 2026-08-25 09:47 639232471861770303
558 ms 210.233.79.83
27 2026-08-25 09:29 639232461630217327
545 ms 210.233.79.83
26 2026-08-25 09:12 639232451282965990
360 ms 210.233.79.83
25 2026-08-25 08:55 639232440814614938
544 ms 210.233.79.83
24 2026-08-25 08:38 639232430410720425
303 ms 210.233.79.83
23 2026-08-25 08:20 639232420003096185
6 ms 210.233.79.83
22 2026-08-25 08:03 639232409467287444
460 ms 210.233.79.83
21 2026-08-25 07:45 639232399077195997
554 ms 210.233.79.83
20 2026-08-25 07:28 639232388731528337
332 ms 210.233.79.83
19 2026-08-25 07:11 639232378288598612
575 ms 210.233.79.83
18 2026-08-25 06:17 639232346196373643
562 ms 210.233.79.83
17 2026-08-25 06:00 639232336112370741
2 ms 210.233.79.83
16 2026-08-25 05:43 639232326146508970
543 ms 210.233.79.83
15 2026-08-25 05:27 639232316189381720
545 ms 210.233.79.83
14 2026-08-25 05:10 639232306217998913
3 ms 210.233.79.83
13 2026-08-25 04:54 639232296255744174
398 ms 210.233.79.83
12 2026-08-25 04:37 639232286095760789
5 ms 210.233.79.83
11 2026-08-25 04:20 639232276086186273
538 ms 210.233.79.83
10 2026-08-25 04:03 639232265900986425
539 ms 210.233.79.83
9 2026-08-25 03:46 639232255723518075
3 ms 210.233.79.83
8 2026-08-25 03:29 639232245484452890
441 ms 210.233.79.83
7 2026-08-25 03:12 639232235157175331
584 ms 210.233.79.83
6 2026-08-25 02:19 639232203197189095
475 ms 210.233.79.83
5 2026-08-25 02:02 639232192844564298
3 ms 210.233.79.83
4 2026-08-25 01:44 639232182496008942
574 ms 210.233.79.83
3 2026-08-25 01:27 639232172197053132
444 ms 210.233.79.83
2 2026-08-25 00:34 639232140250307418
480 ms 210.233.79.83
1 2026-08-25 00:17 639232129927860324
370 ms 210.233.79.83