DNS response history for ns1.jaringan.pro

ns1.jaringan.pro 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 30 DNS check records, 30 successful responses, 0 failed responses, and 552 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 ns1.jaringan.pro.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

552 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:18

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.160.63.223

Most recently resolved hosting IP on selected date

Successful Responses

30

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 ns1.jaringan.pro

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
30 2026-08-25 10:18 639232492740373468
4 ms 103.160.63.223
29 2026-08-25 10:01 639232482235303141
4 ms 103.160.63.223
28 2026-08-25 09:43 639232471861770303
2046 ms 103.160.63.223
27 2026-08-25 09:26 639232461630217327
8 ms 103.160.63.223
26 2026-08-25 09:09 639232451282965990
3 ms 103.160.63.223
25 2026-08-25 08:51 639232440814614938
585 ms 103.160.63.223
24 2026-08-25 08:34 639232430410720425
408 ms 103.160.63.223
23 2026-08-25 08:17 639232420003096185
4 ms 103.160.63.223
22 2026-08-25 07:59 639232409467287444
341 ms 103.160.63.223
21 2026-08-25 07:42 639232399077195997
543 ms 103.160.63.223
20 2026-08-25 07:24 639232388731528337
357 ms 103.160.63.223
19 2026-08-25 07:07 639232378288598612
2277 ms 103.160.63.223
18 2026-08-25 06:13 639232346196373643
432 ms 103.160.63.223
17 2026-08-25 05:56 639232336112370741
2174 ms 103.160.63.223
16 2026-08-25 05:40 639232326146508970
268 ms 103.160.63.223
15 2026-08-25 05:23 639232316189381720
3 ms 103.160.63.223
14 2026-08-25 05:07 639232306217998913
3 ms 103.160.63.223
13 2026-08-25 04:50 639232296255744174
360 ms 103.160.63.223
12 2026-08-25 04:33 639232286095760789
3 ms 103.160.63.223
11 2026-08-25 04:16 639232276086186273
2568 ms 103.160.63.223
10 2026-08-25 04:00 639232265900986425
361 ms 103.160.63.223
9 2026-08-25 03:43 639232255723518075
4 ms 103.160.63.223
8 2026-08-25 03:26 639232245484452890
256 ms 103.160.63.223
7 2026-08-25 03:08 639232235157175331
4 ms 103.160.63.223
6 2026-08-25 02:15 639232203197189095
2271 ms 103.160.63.223
5 2026-08-25 01:58 639232192844564298
16 ms 103.160.63.223
4 2026-08-25 01:41 639232182496008942
339 ms 103.160.63.223
3 2026-08-25 01:23 639232172197053132
344 ms 103.160.63.223
2 2026-08-25 00:30 639232140250307418
337 ms 103.160.63.223
1 2026-08-25 00:13 639232129927860324
226 ms 103.160.63.223