DNS response history for ns2.indexnet.com.br

ns2.indexnet.com.br 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 37 DNS check records, 35 successful responses, 2 failed responses, and 223 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.indexnet.com.br.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

223 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:45

All timestamps shown in UTC

Latest Resolved IP on Selected Date

129.121.42.141

Most recently resolved hosting IP on selected date

Successful Responses

35

Checks that returned a measurable response

Failed Responses

2

Checks with no response or no returned latency

Failure Rate

5%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.indexnet.com.br

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
37 2026-08-25 12:45 639232587225721862
28 ms 129.121.42.141
36 2026-08-25 12:28 639232576780683689
41 ms 129.121.42.141
35 2026-08-25 12:11 639232566381512620
2293 ms 129.121.42.141
34 2026-08-25 11:54 639232556111768563
36 ms 129.121.42.141
33 2026-08-25 11:37 639232545839529039
228 ms 129.121.42.141
32 2026-08-25 11:19 639232535349285207
41 ms 129.121.42.141
31 2026-08-25 11:02 639232524938080723
66 ms 129.121.42.141
30 2026-08-25 10:08 639232492740373468
64 ms 129.121.42.141
29 2026-08-25 09:51 639232482235303141
45 ms 129.121.42.141
28 2026-08-25 09:33 639232471861770303
-
27 2026-08-25 09:16 639232461630217327
-
26 2026-08-25 08:59 639232451282965990
2013 ms 129.121.42.141
25 2026-08-25 08:42 639232440814614938
105 ms 129.121.42.141
24 2026-08-25 08:24 639232430410720425
49 ms 129.121.42.141
23 2026-08-25 08:07 639232420003096185
90 ms 129.121.42.141
22 2026-08-25 07:49 639232409467287444
27 ms 129.121.42.141
21 2026-08-25 07:32 639232399077195997
6 ms 129.121.42.141
20 2026-08-25 07:15 639232388731528337
14 ms 129.121.42.141
19 2026-08-25 06:57 639232378288598612
65 ms 129.121.42.141
18 2026-08-25 06:04 639232346196373643
59 ms 129.121.42.141
17 2026-08-25 05:47 639232336112370741
24 ms 129.121.42.141
16 2026-08-25 05:30 639232326146508970
48 ms 129.121.42.141
15 2026-08-25 05:14 639232316189381720
78 ms 129.121.42.141
14 2026-08-25 04:57 639232306217998913
43 ms 129.121.42.141
13 2026-08-25 04:41 639232296255744174
47 ms 129.121.42.141
12 2026-08-25 04:24 639232286095760789
20 ms 129.121.42.141
11 2026-08-25 04:07 639232276086186273
38 ms 129.121.42.141
10 2026-08-25 03:50 639232265900986425
71 ms 129.121.42.141
9 2026-08-25 03:33 639232255723518075
12 ms 129.121.42.141
8 2026-08-25 03:16 639232245484452890
14 ms 129.121.42.141
7 2026-08-25 02:59 639232235157175331
2016 ms 129.121.42.141
6 2026-08-25 02:06 639232203197189095
12 ms 129.121.42.141
5 2026-08-25 01:48 639232192844564298
14 ms 129.121.42.141
4 2026-08-25 01:31 639232182496008942
40 ms 129.121.42.141
3 2026-08-25 01:14 639232172197053132
26 ms 129.121.42.141
2 2026-08-25 00:21 639232140250307418
22 ms 129.121.42.141
1 2026-08-25 00:03 639232129927860324
14 ms 129.121.42.141