DNS response history for ns2.oneisp.net

ns2.oneisp.net 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 34 DNS check records, 34 successful responses, 0 failed responses, and 237 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.oneisp.net.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

237 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 14:09

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.130.112.36

Most recently resolved hosting IP on selected date

Successful Responses

34

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.oneisp.net

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
34 2026-08-24 14:09 639231765923559455
349 ms 103.130.112.36
33 2026-08-24 13:52 639231755868832964
355 ms 103.130.112.36
32 2026-08-24 13:35 639231745628278877
344 ms 103.130.112.36
31 2026-08-24 13:18 639231735407682062
182 ms 103.130.112.36
30 2026-08-24 12:25 639231703815441688
355 ms 103.130.112.36
29 2026-08-24 12:09 639231693747052549
218 ms 103.130.112.36
28 2026-08-24 11:52 639231683712487276
212 ms 103.130.112.36
27 2026-08-24 11:35 639231673513573868
360 ms 103.130.112.36
26 2026-08-24 10:42 639231641791249939
358 ms 103.130.112.36
25 2026-08-24 10:25 639231631866211033
355 ms 103.130.112.36
24 2026-08-24 10:09 639231621644955316
325 ms 103.130.112.36
23 2026-08-24 09:52 639231611478799259
173 ms 103.130.112.36
22 2026-08-24 08:59 639231579923718211
5 ms 103.130.112.36
21 2026-08-24 08:42 639231569810702936
2 ms 103.130.112.36
20 2026-08-24 08:25 639231559762411619
365 ms 103.130.112.36
19 2026-08-24 08:08 639231549663595407
356 ms 103.130.112.36
18 2026-08-24 07:16 639231518076817246
369 ms 103.130.112.36
17 2026-08-24 06:59 639231508078650885
5 ms 103.130.112.36
16 2026-08-24 06:43 639231498210697093
3 ms 103.130.112.36
15 2026-08-24 06:26 639231488109699360
356 ms 103.130.112.36
14 2026-08-24 05:34 639231456772510692
360 ms 103.130.112.36
13 2026-08-24 05:17 639231447084631185
3 ms 103.130.112.36
12 2026-08-24 05:01 639231437208519473
3 ms 103.130.112.36
11 2026-08-24 04:44 639231427209627490
361 ms 103.130.112.36
10 2026-08-24 03:52 639231395791246644
337 ms 103.130.112.36
9 2026-08-24 03:36 639231386075551458
349 ms 103.130.112.36
8 2026-08-24 03:19 639231376208713791
4 ms 103.130.112.36
7 2026-08-24 03:03 639231366170589276
357 ms 103.130.112.36
6 2026-08-24 02:10 639231334732159368
350 ms 103.130.112.36
5 2026-08-24 01:54 639231325035670078
2 ms 103.130.112.36
4 2026-08-24 01:38 639231315132253837
354 ms 103.130.112.36
3 2026-08-24 01:21 639231305014280808
346 ms 103.130.112.36
2 2026-08-24 00:28 639231273779380675
180 ms 103.130.112.36
1 2026-08-24 00:12 639231264180839154
3 ms 103.130.112.36