DNS response history for ns4.nic.jprs

ns4.nic.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 36 DNS check records, 36 successful responses, 0 failed responses, and 431 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 ns4.nic.jprs.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

431 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:40

All timestamps shown in UTC

Latest Resolved IP on Selected Date

203.105.65.181

Most recently resolved hosting IP on selected date

Successful Responses

36

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 ns4.nic.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
36 2026-08-25 12:40 639232576780683689
242 ms 203.105.65.181
35 2026-08-25 12:23 639232566381512620
253 ms 203.105.65.181
34 2026-08-25 12:05 639232556111768563
242 ms 203.105.65.181
33 2026-08-25 11:48 639232545839529039
254 ms 203.105.65.181
32 2026-08-25 11:31 639232535349285207
241 ms 203.105.65.181
31 2026-08-25 11:13 639232524938080723
4538 ms 203.105.65.181
30 2026-08-25 10:20 639232492740373468
243 ms 203.105.65.181
29 2026-08-25 10:03 639232482235303141
8 ms 203.105.65.181
28 2026-08-25 09:45 639232471861770303
674 ms 203.105.65.181
27 2026-08-25 09:28 639232461630217327
3 ms 203.105.65.181
26 2026-08-25 09:11 639232451282965990
6 ms 203.105.65.181
25 2026-08-25 08:53 639232440814614938
4 ms 203.105.65.181
24 2026-08-25 08:36 639232430410720425
5 ms 203.105.65.181
23 2026-08-25 08:19 639232420003096185
250 ms 203.105.65.181
22 2026-08-25 08:01 639232409467287444
251 ms 203.105.65.181
21 2026-08-25 07:44 639232399077195997
255 ms 203.105.65.181
20 2026-08-25 07:26 639232388731528337
2290 ms 203.105.65.181
19 2026-08-25 07:09 639232378288598612
643 ms 203.105.65.181
18 2026-08-25 06:15 639232346196373643
3 ms 203.105.65.181
17 2026-08-25 05:58 639232336112370741
249 ms 203.105.65.181
16 2026-08-25 05:42 639232326146508970
2004 ms 203.105.65.181
15 2026-08-25 05:25 639232316189381720
19 ms 203.105.65.181
14 2026-08-25 05:09 639232306217998913
11 ms 203.105.65.181
13 2026-08-25 04:52 639232296255744174
3 ms 203.105.65.181
12 2026-08-25 04:35 639232286095760789
3 ms 203.105.65.181
11 2026-08-25 04:18 639232276086186273
267 ms 203.105.65.181
10 2026-08-25 04:02 639232265900986425
264 ms 203.105.65.181
9 2026-08-25 03:45 639232255723518075
258 ms 203.105.65.181
8 2026-08-25 03:28 639232245484452890
245 ms 203.105.65.181
7 2026-08-25 03:10 639232235157175331
253 ms 203.105.65.181
6 2026-08-25 02:17 639232203197189095
241 ms 203.105.65.181
5 2026-08-25 02:00 639232192844564298
250 ms 203.105.65.181
4 2026-08-25 01:43 639232182496008942
245 ms 203.105.65.181
3 2026-08-25 01:25 639232172197053132
4 ms 203.105.65.181
2 2026-08-25 00:32 639232140250307418
3 ms 203.105.65.181
1 2026-08-25 00:15 639232129927860324
787 ms 203.105.65.181