DNS response history for ns1.gadingonline.co.id

ns1.gadingonline.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-26. For this date, NameServerHistory found 37 DNS check records, 37 successful responses, 0 failed responses, and 354 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.gadingonline.co.id.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

354 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:12

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.84.194.195

Most recently resolved hosting IP on selected date

Successful Responses

37

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.gadingonline.co.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
37 2026-08-26 12:12 639233424567558554
180 ms 103.84.194.195
36 2026-08-26 11:54 639233414056832719
179 ms 103.84.194.195
35 2026-08-26 11:37 639233403515141099
171 ms 103.84.194.195
34 2026-08-26 10:42 639233370841350248
168 ms 103.84.194.195
33 2026-08-26 10:25 639233360361507238
333 ms 103.84.194.195
32 2026-08-26 10:07 639233350067824371
340 ms 103.84.194.195
31 2026-08-26 09:50 639233339545274518
166 ms 103.84.194.195
30 2026-08-26 09:33 639233329214918079
322 ms 103.84.194.195
29 2026-08-26 09:15 639233318749762337
326 ms 103.84.194.195
28 2026-08-26 08:58 639233308387917838
181 ms 103.84.194.195
27 2026-08-26 08:41 639233297961740122
2184 ms 103.84.194.195
26 2026-08-26 08:23 639233287487159094
193 ms 103.84.194.195
25 2026-08-26 08:06 639233276995531707
501 ms 103.84.194.195
24 2026-08-26 07:48 639233266521568229
342 ms 103.84.194.195
23 2026-08-26 07:31 639233256081047431
346 ms 103.84.194.195
22 2026-08-26 06:37 639233223620132921
188 ms 103.84.194.195
21 2026-08-26 06:20 639233213287814244
1368 ms 103.84.194.195
20 2026-08-26 06:02 639233202925983161
9 ms 103.84.194.195
19 2026-08-26 05:45 639233192644780696
328 ms 103.84.194.195
18 2026-08-26 05:28 639233182401183833
343 ms 103.84.194.195
17 2026-08-26 05:11 639233172074181051
171 ms 103.84.194.195
16 2026-08-26 04:54 639233161808421455
338 ms 103.84.194.195
15 2026-08-26 04:36 639233151357344052
238 ms 103.84.194.195
14 2026-08-26 04:19 639233141034116946
334 ms 103.84.194.195
13 2026-08-26 04:02 639233130828334142
188 ms 103.84.194.195
12 2026-08-26 03:45 639233120373450007
572 ms 103.84.194.195
11 2026-08-26 03:27 639233110066216193
339 ms 103.84.194.195
10 2026-08-26 02:34 639233078065410564
196 ms 103.84.194.195
9 2026-08-26 02:17 639233067787457832
348 ms 103.84.194.195
8 2026-08-26 02:00 639233057501801162
173 ms 103.84.194.195
7 2026-08-26 01:43 639233047089431703
333 ms 103.84.194.195
6 2026-08-26 01:25 639233036754790688
331 ms 103.84.194.195
5 2026-08-26 01:08 639233026412602472
335 ms 103.84.194.195
4 2026-08-26 00:51 639233016064066127
164 ms 103.84.194.195
3 2026-08-26 00:34 639233005922655772
210 ms 103.84.194.195
2 2026-08-26 00:17 639232995672256907
332 ms 103.84.194.195
1 2026-08-26 00:00 639232985300872416
326 ms 103.84.194.195