DNS response history for ns2.brdomain.jp

ns2.brdomain.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 27 DNS check records, 27 successful responses, 0 failed responses, and 686 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 ns2.brdomain.jp.
Records on Selected Date

27

Historical checks stored for this nameserver on selected date

Average Latency

686 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:29

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.199.133.190

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 ns2.brdomain.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
27 2026-08-25 09:29 639232461630217327
484 ms 103.199.133.190
26 2026-08-25 09:12 639232451282965990
484 ms 103.199.133.190
25 2026-08-25 08:54 639232440814614938
481 ms 103.199.133.190
24 2026-08-25 08:37 639232430410720425
472 ms 103.199.133.190
23 2026-08-25 08:20 639232420003096185
489 ms 103.199.133.190
22 2026-08-25 08:02 639232409467287444
499 ms 103.199.133.190
21 2026-08-25 07:45 639232399077195997
486 ms 103.199.133.190
20 2026-08-25 07:27 639232388731528337
510 ms 103.199.133.190
19 2026-08-25 07:10 639232378288598612
504 ms 103.199.133.190
18 2026-08-25 06:16 639232346196373643
471 ms 103.199.133.190
17 2026-08-25 06:00 639232336112370741
2249 ms 103.199.133.190
16 2026-08-25 05:43 639232326146508970
477 ms 103.199.133.190
15 2026-08-25 05:26 639232316189381720
473 ms 103.199.133.190
14 2026-08-25 05:10 639232306217998913
469 ms 103.199.133.190
13 2026-08-25 04:53 639232296255744174
465 ms 103.199.133.190
12 2026-08-25 04:36 639232286095760789
480 ms 103.199.133.190
11 2026-08-25 04:19 639232276086186273
475 ms 103.199.133.190
10 2026-08-25 04:03 639232265900986425
2266 ms 103.199.133.190
9 2026-08-25 03:46 639232255723518075
484 ms 103.199.133.190
8 2026-08-25 03:29 639232245484452890
476 ms 103.199.133.190
7 2026-08-25 03:11 639232235157175331
476 ms 103.199.133.190
6 2026-08-25 02:18 639232203197189095
2475 ms 103.199.133.190
5 2026-08-25 02:01 639232192844564298
459 ms 103.199.133.190
4 2026-08-25 01:44 639232182496008942
481 ms 103.199.133.190
3 2026-08-25 01:26 639232172197053132
472 ms 103.199.133.190
2 2026-08-25 00:33 639232140250307418
473 ms 103.199.133.190
1 2026-08-25 00:16 639232129927860324
488 ms 103.199.133.190