DNS response history for ns2.p-link.co.id

ns2.p-link.co.id 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 248 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.p-link.co.id.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

248 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:42

All timestamps shown in UTC

Latest Resolved IP on Selected Date

202.43.117.12

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 ns2.p-link.co.id

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:42 639232576780683689
162 ms 202.43.117.12
35 2026-08-25 12:24 639232566381512620
340 ms 202.43.117.12
34 2026-08-25 12:07 639232556111768563
324 ms 202.43.117.12
33 2026-08-25 11:50 639232545839529039
164 ms 202.43.117.12
32 2026-08-25 11:33 639232535349285207
327 ms 202.43.117.12
31 2026-08-25 11:15 639232524938080723
334 ms 202.43.117.12
30 2026-08-25 10:21 639232492740373468
168 ms 202.43.117.12
29 2026-08-25 10:04 639232482235303141
328 ms 202.43.117.12
28 2026-08-25 09:47 639232471861770303
7 ms 202.43.117.12
27 2026-08-25 09:29 639232461630217327
161 ms 202.43.117.12
26 2026-08-25 09:12 639232451282965990
341 ms 202.43.117.12
25 2026-08-25 08:55 639232440814614938
303 ms 202.43.117.12
24 2026-08-25 08:38 639232430410720425
179 ms 202.43.117.12
23 2026-08-25 08:20 639232420003096185
328 ms 202.43.117.12
22 2026-08-25 08:03 639232409467287444
324 ms 202.43.117.12
21 2026-08-25 07:45 639232399077195997
331 ms 202.43.117.12
20 2026-08-25 07:28 639232388731528337
327 ms 202.43.117.12
19 2026-08-25 07:11 639232378288598612
323 ms 202.43.117.12
18 2026-08-25 06:17 639232346196373643
336 ms 202.43.117.12
17 2026-08-25 06:00 639232336112370741
4 ms 202.43.117.12
16 2026-08-25 05:43 639232326146508970
328 ms 202.43.117.12
15 2026-08-25 05:27 639232316189381720
330 ms 202.43.117.12
14 2026-08-25 05:10 639232306217998913
2 ms 202.43.117.12
13 2026-08-25 04:54 639232296255744174
346 ms 202.43.117.12
12 2026-08-25 04:37 639232286095760789
3 ms 202.43.117.12
11 2026-08-25 04:20 639232276086186273
341 ms 202.43.117.12
10 2026-08-25 04:03 639232265900986425
164 ms 202.43.117.12
9 2026-08-25 03:46 639232255723518075
163 ms 202.43.117.12
8 2026-08-25 03:29 639232245484452890
322 ms 202.43.117.12
7 2026-08-25 03:12 639232235157175331
494 ms 202.43.117.12
6 2026-08-25 02:19 639232203197189095
3 ms 202.43.117.12
5 2026-08-25 02:02 639232192844564298
332 ms 202.43.117.12
4 2026-08-25 01:44 639232182496008942
332 ms 202.43.117.12
3 2026-08-25 01:27 639232172197053132
329 ms 202.43.117.12
2 2026-08-25 00:34 639232140250307418
4 ms 202.43.117.12
1 2026-08-25 00:17 639232129927860324
317 ms 202.43.117.12