DNS response history for ns2.apisnetworks.com

ns2.apisnetworks.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-25. For this date, NameServerHistory found 35 DNS check records, 35 successful responses, 0 failed responses, and 250 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.apisnetworks.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

250 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:15

All timestamps shown in UTC

Latest Resolved IP on Selected Date

96.126.122.82

Most recently resolved hosting IP on selected date

Successful Responses

35

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.apisnetworks.com

Showing DNS history for 2026-08-25 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
35 2026-08-25 12:15 639232566381512620
188 ms 96.126.122.82
34 2026-08-25 11:58 639232556111768563
15 ms 96.126.122.82
33 2026-08-25 11:41 639232545839529039
2134 ms 96.126.122.82
32 2026-08-25 11:24 639232535349285207
8 ms 96.126.122.82
31 2026-08-25 11:06 639232524938080723
2113 ms 96.126.122.82
30 2026-08-25 10:12 639232492740373468
238 ms 96.126.122.82
29 2026-08-25 09:55 639232482235303141
7 ms 96.126.122.82
28 2026-08-25 09:38 639232471861770303
14 ms 96.126.122.82
27 2026-08-25 09:21 639232461630217327
264 ms 96.126.122.82
26 2026-08-25 09:03 639232451282965990
21 ms 96.126.122.82
25 2026-08-25 08:46 639232440814614938
27 ms 96.126.122.82
24 2026-08-25 08:29 639232430410720425
262 ms 96.126.122.82
23 2026-08-25 08:11 639232420003096185
251 ms 96.126.122.82
22 2026-08-25 07:54 639232409467287444
142 ms 96.126.122.82
21 2026-08-25 07:36 639232399077195997
244 ms 96.126.122.82
20 2026-08-25 07:19 639232388731528337
30 ms 96.126.122.82
19 2026-08-25 07:02 639232378288598612
264 ms 96.126.122.82
18 2026-08-25 06:08 639232346196373643
255 ms 96.126.122.82
17 2026-08-25 05:51 639232336112370741
248 ms 96.126.122.82
16 2026-08-25 05:35 639232326146508970
139 ms 96.126.122.82
15 2026-08-25 05:18 639232316189381720
32 ms 96.126.122.82
14 2026-08-25 05:02 639232306217998913
268 ms 96.126.122.82
13 2026-08-25 04:45 639232296255744174
239 ms 96.126.122.82
12 2026-08-25 04:28 639232286095760789
231 ms 96.126.122.82
11 2026-08-25 04:11 639232276086186273
10 ms 96.126.122.82
10 2026-08-25 03:55 639232265900986425
28 ms 96.126.122.82
9 2026-08-25 03:37 639232255723518075
12 ms 96.126.122.82
8 2026-08-25 03:20 639232245484452890
9 ms 96.126.122.82
7 2026-08-25 03:03 639232235157175331
272 ms 96.126.122.82
6 2026-08-25 02:10 639232203197189095
233 ms 96.126.122.82
5 2026-08-25 01:53 639232192844564298
229 ms 96.126.122.82
4 2026-08-25 01:36 639232182496008942
7 ms 96.126.122.82
3 2026-08-25 01:18 639232172197053132
29 ms 96.126.122.82
2 2026-08-25 00:25 639232140250307418
250 ms 96.126.122.82
1 2026-08-25 00:08 639232129927860324
21 ms 96.126.122.82