DNS response history for ns2.tarungtotonews.com

ns2.tarungtotonews.com 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 30 DNS check records, 30 successful responses, 0 failed responses, and 256 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.tarungtotonews.com.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

256 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 12:26

All timestamps shown in UTC

Latest Resolved IP on Selected Date

15.235.131.75

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 ns2.tarungtotonews.com

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
30 2026-08-24 12:26 639231703815441688
419 ms 15.235.131.75
29 2026-08-24 12:09 639231693747052549
409 ms 15.235.131.75
28 2026-08-24 11:52 639231683712487276
425 ms 15.235.131.75
27 2026-08-24 11:36 639231673513573868
167 ms 15.235.131.75
26 2026-08-24 10:42 639231641791249939
417 ms 15.235.131.75
25 2026-08-24 10:26 639231631866211033
262 ms 15.235.131.75
24 2026-08-24 10:09 639231621644955316
415 ms 15.235.131.75
23 2026-08-24 09:52 639231611478799259
417 ms 15.235.131.75
22 2026-08-24 09:00 639231579923718211
408 ms 15.235.131.75
21 2026-08-24 08:43 639231569810702936
355 ms 15.235.131.75
20 2026-08-24 08:26 639231559762411619
165 ms 15.235.131.75
19 2026-08-24 08:09 639231549663595407
254 ms 15.235.131.75
18 2026-08-24 07:16 639231518076817246
410 ms 15.235.131.75
17 2026-08-24 07:00 639231508078650885
3 ms 15.235.131.75
16 2026-08-24 06:43 639231498210697093
3 ms 15.235.131.75
15 2026-08-24 06:27 639231488109699360
413 ms 15.235.131.75
14 2026-08-24 05:34 639231456772510692
328 ms 15.235.131.75
13 2026-08-24 05:18 639231447084631185
7 ms 15.235.131.75
12 2026-08-24 05:01 639231437208519473
336 ms 15.235.131.75
11 2026-08-24 04:45 639231427209627490
410 ms 15.235.131.75
10 2026-08-24 03:52 639231395791246644
3 ms 15.235.131.75
9 2026-08-24 03:36 639231386075551458
327 ms 15.235.131.75
8 2026-08-24 03:20 639231376208713791
330 ms 15.235.131.75
7 2026-08-24 03:03 639231366170589276
322 ms 15.235.131.75
6 2026-08-24 02:11 639231334732159368
3 ms 15.235.131.75
5 2026-08-24 01:54 639231325035670078
171 ms 15.235.131.75
4 2026-08-24 01:38 639231315132253837
178 ms 15.235.131.75
3 2026-08-24 01:22 639231305014280808
324 ms 15.235.131.75
2 2026-08-24 00:29 639231273779380675
5 ms 15.235.131.75
1 2026-08-24 00:13 639231264180839154
3 ms 15.235.131.75