DNS response history for ns2.ssv1.my.id

ns2.ssv1.my.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 30 DNS check records, 30 successful responses, 0 failed responses, and 283 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.ssv1.my.id.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

283 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 12:25

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.167.112.5

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.ssv1.my.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
30 2026-08-24 12:25 639231703815441688
3 ms 103.167.112.5
29 2026-08-24 12:09 639231693747052549
195 ms 103.167.112.5
28 2026-08-24 11:52 639231683712487276
336 ms 103.167.112.5
27 2026-08-24 11:35 639231673513573868
436 ms 103.167.112.5
26 2026-08-24 10:42 639231641791249939
4 ms 103.167.112.5
25 2026-08-24 10:25 639231631866211033
222 ms 103.167.112.5
24 2026-08-24 10:09 639231621644955316
180 ms 103.167.112.5
23 2026-08-24 09:51 639231611478799259
362 ms 103.167.112.5
22 2026-08-24 08:59 639231579923718211
209 ms 103.167.112.5
21 2026-08-24 08:42 639231569810702936
201 ms 103.167.112.5
20 2026-08-24 08:25 639231559762411619
172 ms 103.167.112.5
19 2026-08-24 08:08 639231549663595407
344 ms 103.167.112.5
18 2026-08-24 07:16 639231518076817246
172 ms 103.167.112.5
17 2026-08-24 06:59 639231508078650885
186 ms 103.167.112.5
16 2026-08-24 06:42 639231498210697093
337 ms 103.167.112.5
15 2026-08-24 06:26 639231488109699360
333 ms 103.167.112.5
14 2026-08-24 05:34 639231456772510692
32 ms 103.167.112.5
13 2026-08-24 05:17 639231447084631185
325 ms 103.167.112.5
12 2026-08-24 05:01 639231437208519473
204 ms 103.167.112.5
11 2026-08-24 04:44 639231427209627490
336 ms 103.167.112.5
10 2026-08-24 03:52 639231395791246644
331 ms 103.167.112.5
9 2026-08-24 03:36 639231386075551458
3 ms 103.167.112.5
8 2026-08-24 03:19 639231376208713791
331 ms 103.167.112.5
7 2026-08-24 03:03 639231366170589276
192 ms 103.167.112.5
6 2026-08-24 02:10 639231334732159368
188 ms 103.167.112.5
5 2026-08-24 01:54 639231325035670078
2007 ms 103.167.112.5
4 2026-08-24 01:37 639231315132253837
333 ms 103.167.112.5
3 2026-08-24 01:21 639231305014280808
177 ms 103.167.112.5
2 2026-08-24 00:28 639231273779380675
181 ms 103.167.112.5
1 2026-08-24 00:12 639231264180839154
169 ms 103.167.112.5