DNS response history for ns2.barayatel.co.id

ns2.barayatel.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-24. For this date, NameServerHistory found 31 DNS check records, 31 successful responses, 0 failed responses, and 447 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.barayatel.co.id.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

447 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 13:18

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.125.118.2

Most recently resolved hosting IP on selected date

Successful Responses

31

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.barayatel.co.id

Showing DNS history for 2026-08-24 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
31 2026-08-24 13:18 639231735407682062
38 ms 103.125.118.2
30 2026-08-24 12:26 639231703815441688
358 ms 103.125.118.2
29 2026-08-24 12:09 639231693747052549
2007 ms 103.125.118.2
28 2026-08-24 11:52 639231683712487276
1335 ms 103.125.118.2
27 2026-08-24 11:35 639231673513573868
345 ms 103.125.118.2
26 2026-08-24 10:42 639231641791249939
344 ms 103.125.118.2
25 2026-08-24 10:26 639231631866211033
8 ms 103.125.118.2
24 2026-08-24 10:09 639231621644955316
171 ms 103.125.118.2
23 2026-08-24 09:52 639231611478799259
5 ms 103.125.118.2
22 2026-08-24 08:59 639231579923718211
175 ms 103.125.118.2
21 2026-08-24 08:43 639231569810702936
2211 ms 103.125.118.2
20 2026-08-24 08:25 639231559762411619
340 ms 103.125.118.2
19 2026-08-24 08:09 639231549663595407
344 ms 103.125.118.2
18 2026-08-24 07:16 639231518076817246
197 ms 103.125.118.2
17 2026-08-24 07:00 639231508078650885
246 ms 103.125.118.2
16 2026-08-24 06:43 639231498210697093
3 ms 103.125.118.2
15 2026-08-24 06:26 639231488109699360
2 ms 103.125.118.2
14 2026-08-24 05:34 639231456772510692
339 ms 103.125.118.2
13 2026-08-24 05:18 639231447084631185
337 ms 103.125.118.2
12 2026-08-24 05:01 639231437208519473
526 ms 103.125.118.2
11 2026-08-24 04:45 639231427209627490
783 ms 103.125.118.2
10 2026-08-24 03:52 639231395791246644
347 ms 103.125.118.2
9 2026-08-24 03:36 639231386075551458
987 ms 103.125.118.2
8 2026-08-24 03:20 639231376208713791
7 ms 103.125.118.2
7 2026-08-24 03:03 639231366170589276
346 ms 103.125.118.2
6 2026-08-24 02:11 639231334732159368
9 ms 103.125.118.2
5 2026-08-24 01:54 639231325035670078
922 ms 103.125.118.2
4 2026-08-24 01:38 639231315132253837
927 ms 103.125.118.2
3 2026-08-24 01:21 639231305014280808
186 ms 103.125.118.2
2 2026-08-24 00:29 639231273779380675
2 ms 103.125.118.2
1 2026-08-24 00:13 639231264180839154
3 ms 103.125.118.2