DNS response history for ns3.brand.jprs

ns3.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 27 DNS check records, 27 successful responses, 0 failed responses, and 654 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 ns3.brand.jprs.
Records on Selected Date

27

Historical checks stored for this nameserver on selected date

Average Latency

654 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

203.105.65.178

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 ns3.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
27 2026-08-25 09:29 639232461630217327
2817 ms 203.105.65.178
26 2026-08-25 09:12 639232451282965990
242 ms 203.105.65.178
25 2026-08-25 08:54 639232440814614938
792 ms 203.105.65.178
24 2026-08-25 08:37 639232430410720425
786 ms 203.105.65.178
23 2026-08-25 08:20 639232420003096185
651 ms 203.105.65.178
22 2026-08-25 08:02 639232409467287444
763 ms 203.105.65.178
21 2026-08-25 07:45 639232399077195997
874 ms 203.105.65.178
20 2026-08-25 07:27 639232388731528337
250 ms 203.105.65.178
19 2026-08-25 07:10 639232378288598612
765 ms 203.105.65.178
18 2026-08-25 06:16 639232346196373643
2490 ms 203.105.65.178
17 2026-08-25 05:59 639232336112370741
253 ms 203.105.65.178
16 2026-08-25 05:43 639232326146508970
493 ms 203.105.65.178
15 2026-08-25 05:26 639232316189381720
644 ms 203.105.65.178
14 2026-08-25 05:10 639232306217998913
246 ms 203.105.65.178
13 2026-08-25 04:53 639232296255744174
237 ms 203.105.65.178
12 2026-08-25 04:36 639232286095760789
663 ms 203.105.65.178
11 2026-08-25 04:19 639232276086186273
246 ms 203.105.65.178
10 2026-08-25 04:03 639232265900986425
237 ms 203.105.65.178
9 2026-08-25 03:46 639232255723518075
237 ms 203.105.65.178
8 2026-08-25 03:28 639232245484452890
626 ms 203.105.65.178
7 2026-08-25 03:11 639232235157175331
772 ms 203.105.65.178
6 2026-08-25 02:18 639232203197189095
249 ms 203.105.65.178
5 2026-08-25 02:01 639232192844564298
254 ms 203.105.65.178
4 2026-08-25 01:44 639232182496008942
655 ms 203.105.65.178
3 2026-08-25 01:26 639232172197053132
517 ms 203.105.65.178
2 2026-08-25 00:33 639232140250307418
653 ms 203.105.65.178
1 2026-08-25 00:16 639232129927860324
248 ms 203.105.65.178