DNS response history for dns2.link.net.id

dns2.link.net.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-26. For this date, NameServerHistory found 39 DNS check records, 39 successful responses, 0 failed responses, and 374 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 dns2.link.net.id.
Records on Selected Date

39

Historical checks stored for this nameserver on selected date

Average Latency

374 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 13:01

All timestamps shown in UTC

Latest Resolved IP on Selected Date

202.137.3.121

Most recently resolved hosting IP on selected date

Successful Responses

39

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 dns2.link.net.id

Showing DNS history for 2026-08-26 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
39 2026-08-26 13:01 639233455747096265
327 ms 202.137.3.121
38 2026-08-26 12:43 639233445367152284
324 ms 202.137.3.121
37 2026-08-26 12:26 639233434974187439
2325 ms 202.137.3.121
36 2026-08-26 12:09 639233424567558554
338 ms 202.137.3.121
35 2026-08-26 11:51 639233414056832719
166 ms 202.137.3.121
34 2026-08-26 11:34 639233403515141099
344 ms 202.137.3.121
33 2026-08-26 10:39 639233370841350248
33 ms 202.137.3.121
32 2026-08-26 10:22 639233360361507238
332 ms 202.137.3.121
31 2026-08-26 10:04 639233350067824371
332 ms 202.137.3.121
30 2026-08-26 09:47 639233339545274518
182 ms 202.137.3.121
29 2026-08-26 09:30 639233329214918079
166 ms 202.137.3.121
28 2026-08-26 09:12 639233318749762337
167 ms 202.137.3.121
27 2026-08-26 08:55 639233308387917838
500 ms 202.137.3.121
26 2026-08-26 08:38 639233297961740122
167 ms 202.137.3.121
25 2026-08-26 08:20 639233287487159094
171 ms 202.137.3.121
24 2026-08-26 08:03 639233276995531707
7 ms 202.137.3.121
23 2026-08-26 07:45 639233266521568229
172 ms 202.137.3.121
22 2026-08-26 07:28 639233256081047431
169 ms 202.137.3.121
21 2026-08-26 06:34 639233223620132921
173 ms 202.137.3.121
20 2026-08-26 06:17 639233213287814244
8 ms 202.137.3.121
19 2026-08-26 05:59 639233202925983161
2033 ms 202.137.3.121
18 2026-08-26 05:42 639233192644780696
350 ms 202.137.3.121
17 2026-08-26 05:25 639233182401183833
328 ms 202.137.3.121
16 2026-08-26 05:08 639233172074181051
53 ms 202.137.3.121
15 2026-08-26 04:51 639233161808421455
265 ms 202.137.3.121
14 2026-08-26 04:33 639233151357344052
279 ms 202.137.3.121
13 2026-08-26 04:16 639233141034116946
360 ms 202.137.3.121
12 2026-08-26 03:59 639233130828334142
326 ms 202.137.3.121
11 2026-08-26 03:42 639233120373450007
345 ms 202.137.3.121
10 2026-08-26 03:24 639233110066216193
326 ms 202.137.3.121
9 2026-08-26 02:31 639233078065410564
321 ms 202.137.3.121
8 2026-08-26 02:14 639233067787457832
13 ms 202.137.3.121
7 2026-08-26 01:57 639233057501801162
498 ms 202.137.3.121
6 2026-08-26 01:40 639233047089431703
163 ms 202.137.3.121
5 2026-08-26 01:22 639233036754790688
335 ms 202.137.3.121
4 2026-08-26 01:05 639233026412602472
11 ms 202.137.3.121
3 2026-08-26 00:48 639233016064066127
165 ms 202.137.3.121
2 2026-08-26 00:31 639233005922655772
2008 ms 202.137.3.121
1 2026-08-26 00:14 639232995672256907
8 ms 202.137.3.121