DNS response history for ns1.noveweb.com.br

ns1.noveweb.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-26. For this date, NameServerHistory found 34 DNS check records, 34 successful responses, 0 failed responses, and 408 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 ns1.noveweb.com.br.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

408 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:36

All timestamps shown in UTC

Latest Resolved IP on Selected Date

129.121.40.127

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 ns1.noveweb.com.br

Showing DNS history for 2026-08-26 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-26 11:36 639233403515141099
142 ms 129.121.40.127
33 2026-08-26 10:42 639233370841350248
292 ms 129.121.40.127
32 2026-08-26 10:25 639233360361507238
139 ms 129.121.40.127
31 2026-08-26 10:07 639233350067824371
475 ms 129.121.40.127
30 2026-08-26 09:50 639233339545274518
215 ms 129.121.40.127
29 2026-08-26 09:32 639233329214918079
2008 ms 129.121.40.127
28 2026-08-26 09:15 639233318749762337
295 ms 129.121.40.127
27 2026-08-26 08:58 639233308387917838
212 ms 129.121.40.127
26 2026-08-26 08:40 639233297961740122
285 ms 129.121.40.127
25 2026-08-26 08:23 639233287487159094
288 ms 129.121.40.127
24 2026-08-26 08:06 639233276995531707
293 ms 129.121.40.127
23 2026-08-26 07:48 639233266521568229
234 ms 129.121.40.127
22 2026-08-26 07:30 639233256081047431
517 ms 129.121.40.127
21 2026-08-26 06:37 639233223620132921
164 ms 129.121.40.127
20 2026-08-26 06:19 639233213287814244
293 ms 129.121.40.127
19 2026-08-26 06:02 639233202925983161
309 ms 129.121.40.127
18 2026-08-26 05:45 639233192644780696
203 ms 129.121.40.127
17 2026-08-26 05:28 639233182401183833
281 ms 129.121.40.127
16 2026-08-26 05:11 639233172074181051
283 ms 129.121.40.127
15 2026-08-26 04:53 639233161808421455
2216 ms 129.121.40.127
14 2026-08-26 04:36 639233151357344052
287 ms 129.121.40.127
13 2026-08-26 04:19 639233141034116946
141 ms 129.121.40.127
12 2026-08-26 04:02 639233130828334142
140 ms 129.121.40.127
11 2026-08-26 03:45 639233120373450007
289 ms 129.121.40.127
10 2026-08-26 03:27 639233110066216193
302 ms 129.121.40.127
9 2026-08-26 02:34 639233078065410564
145 ms 129.121.40.127
8 2026-08-26 02:17 639233067787457832
212 ms 129.121.40.127
7 2026-08-26 02:00 639233057501801162
137 ms 129.121.40.127
6 2026-08-26 01:42 639233047089431703
2202 ms 129.121.40.127
5 2026-08-26 01:25 639233036754790688
205 ms 129.121.40.127
4 2026-08-26 01:08 639233026412602472
202 ms 129.121.40.127
3 2026-08-26 00:51 639233016064066127
142 ms 129.121.40.127
2 2026-08-26 00:33 639233005922655772
303 ms 129.121.40.127
1 2026-08-26 00:16 639232995672256907
8 ms 129.121.40.127