DNS response history for ns2.insideinfor.com.br

ns2.insideinfor.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-30. For this date, NameServerHistory found 38 DNS check records, 38 successful responses, 0 failed responses, and 347 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.insideinfor.com.br.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

347 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-30 12:11

All timestamps shown in UTC

Latest Resolved IP on Selected Date

50.28.8.125

Most recently resolved hosting IP on selected date

Successful Responses

38

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.insideinfor.com.br

Showing DNS history for 2026-08-30 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
38 2026-08-30 12:11 639236878057367680
343 ms 50.28.8.125
37 2026-08-30 11:54 639236867916029489
3 ms 50.28.8.125
36 2026-08-30 11:37 639236858088772005
290 ms 50.28.8.125
35 2026-08-30 11:21 639236848158742395
10 ms 50.28.8.125
34 2026-08-30 11:04 639236838137395574
6 ms 50.28.8.125
33 2026-08-30 10:47 639236827967386881
295 ms 50.28.8.125
32 2026-08-30 10:30 639236817708615077
291 ms 50.28.8.125
31 2026-08-30 09:37 639236785770651804
283 ms 50.28.8.125
30 2026-08-30 09:20 639236775820686373
274 ms 50.28.8.125
29 2026-08-30 09:04 639236765768339082
287 ms 50.28.8.125
28 2026-08-30 08:47 639236755602384085
301 ms 50.28.8.125
27 2026-08-30 08:30 639236745600094925
332 ms 50.28.8.125
26 2026-08-30 08:13 639236735311262753
294 ms 50.28.8.125
25 2026-08-30 07:56 639236724996745235
281 ms 50.28.8.125
24 2026-08-30 07:39 639236714839899761
295 ms 50.28.8.125
23 2026-08-30 07:22 639236704748431488
3 ms 50.28.8.125
22 2026-08-30 07:05 639236694430128550
3 ms 50.28.8.125
21 2026-08-30 06:48 639236684143292417
297 ms 50.28.8.125
20 2026-08-30 06:31 639236673972499943
4 ms 50.28.8.125
19 2026-08-30 05:37 639236642126522802
283 ms 50.28.8.125
18 2026-08-30 05:21 639236632183518198
290 ms 50.28.8.125
17 2026-08-30 05:04 639236622289312589
285 ms 50.28.8.125
16 2026-08-30 04:48 639236612490676525
431 ms 50.28.8.125
15 2026-08-30 04:31 639236602582494852
295 ms 50.28.8.125
14 2026-08-30 04:15 639236592511706469
300 ms 50.28.8.125
13 2026-08-30 03:58 639236582441006869
289 ms 50.28.8.125
12 2026-08-30 03:41 639236572478785089
296 ms 50.28.8.125
11 2026-08-30 03:25 639236562556749999
8 ms 50.28.8.125
10 2026-08-30 03:08 639236552353482281
283 ms 50.28.8.125
9 2026-08-30 02:51 639236542188881607
279 ms 50.28.8.125
8 2026-08-30 02:34 639236531885440105
286 ms 50.28.8.125
7 2026-08-30 01:40 639236499922985383
2291 ms 50.28.8.125
6 2026-08-30 01:24 639236489713594431
295 ms 50.28.8.125
5 2026-08-30 01:07 639236479750443901
2215 ms 50.28.8.125
4 2026-08-30 00:50 639236469719936375
275 ms 50.28.8.125
3 2026-08-30 00:33 639236459579244885
289 ms 50.28.8.125
2 2026-08-30 00:17 639236449582837549
290 ms 50.28.8.125
1 2026-08-30 00:00 639236439461653110
305 ms 50.28.8.125