DNS response history for ns2.brand.jprs

ns2.brand.jprs 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 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 ns2.brand.jprs.
Records on Selected Date

29

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 10:04

All timestamps shown in UTC

Latest Resolved IP on Selected Date

202.11.16.59

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 ns2.brand.jprs

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 10:04 639232482235303141
261 ms 202.11.16.59
28 2026-08-25 09:46 639232471861770303
662 ms 202.11.16.59
27 2026-08-25 09:29 639232461630217327
239 ms 202.11.16.59
26 2026-08-25 09:12 639232451282965990
744 ms 202.11.16.59
25 2026-08-25 08:54 639232440814614938
664 ms 202.11.16.59
24 2026-08-25 08:37 639232430410720425
261 ms 202.11.16.59
23 2026-08-25 08:20 639232420003096185
761 ms 202.11.16.59
22 2026-08-25 08:02 639232409467287444
251 ms 202.11.16.59
21 2026-08-25 07:45 639232399077195997
654 ms 202.11.16.59
20 2026-08-25 07:27 639232388731528337
779 ms 202.11.16.59
19 2026-08-25 07:10 639232378288598612
241 ms 202.11.16.59
18 2026-08-25 06:16 639232346196373643
648 ms 202.11.16.59
17 2026-08-25 05:59 639232336112370741
242 ms 202.11.16.59
16 2026-08-25 05:43 639232326146508970
250 ms 202.11.16.59
15 2026-08-25 05:26 639232316189381720
256 ms 202.11.16.59
14 2026-08-25 05:10 639232306217998913
246 ms 202.11.16.59
13 2026-08-25 04:53 639232296255744174
253 ms 202.11.16.59
12 2026-08-25 04:36 639232286095760789
250 ms 202.11.16.59
11 2026-08-25 04:19 639232276086186273
3 ms 202.11.16.59
10 2026-08-25 04:03 639232265900986425
247 ms 202.11.16.59
9 2026-08-25 03:46 639232255723518075
262 ms 202.11.16.59
8 2026-08-25 03:29 639232245484452890
253 ms 202.11.16.59
7 2026-08-25 03:11 639232235157175331
237 ms 202.11.16.59
6 2026-08-25 02:18 639232203197189095
659 ms 202.11.16.59
5 2026-08-25 02:01 639232192844564298
240 ms 202.11.16.59
4 2026-08-25 01:44 639232182496008942
4 ms 202.11.16.59
3 2026-08-25 01:26 639232172197053132
670 ms 202.11.16.59
2 2026-08-25 00:33 639232140250307418
747 ms 202.11.16.59
1 2026-08-25 00:16 639232129927860324
237 ms 202.11.16.59