DNS response history for ns1.negropos.com

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

34

Historical checks stored for this nameserver on selected date

Average Latency

385 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 14:03

All timestamps shown in UTC

Latest Resolved IP on Selected Date

37.156.246.78

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

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:03 639231765923559455
34 ms 37.156.246.78
33 2026-08-24 13:47 639231755868832964
56 ms 37.156.246.78
32 2026-08-24 13:30 639231745628278877
186 ms 37.156.246.78
31 2026-08-24 13:12 639231735407682062
100 ms 37.156.246.78
30 2026-08-24 12:20 639231703815441688
111 ms 37.156.246.78
29 2026-08-24 12:03 639231693747052549
28 ms 37.156.246.78
28 2026-08-24 11:46 639231683712487276
88 ms 37.156.246.78
27 2026-08-24 11:29 639231673513573868
2027 ms 37.156.246.78
26 2026-08-24 10:36 639231641791249939
96 ms 37.156.246.78
25 2026-08-24 10:20 639231631866211033
8 ms 37.156.246.78
24 2026-08-24 10:03 639231621644955316
2067 ms 37.156.246.78
23 2026-08-24 09:46 639231611478799259
2283 ms 37.156.246.78
22 2026-08-24 08:53 639231579923718211
293 ms 37.156.246.78
21 2026-08-24 08:37 639231569810702936
104 ms 37.156.246.78
20 2026-08-24 08:20 639231559762411619
101 ms 37.156.246.78
19 2026-08-24 08:03 639231549663595407
131 ms 37.156.246.78
18 2026-08-24 07:10 639231518076817246
8 ms 37.156.246.78
17 2026-08-24 06:54 639231508078650885
2148 ms 37.156.246.78
16 2026-08-24 06:37 639231498210697093
119 ms 37.156.246.78
15 2026-08-24 06:21 639231488109699360
86 ms 37.156.246.78
14 2026-08-24 05:28 639231456772510692
187 ms 37.156.246.78
13 2026-08-24 05:12 639231447084631185
115 ms 37.156.246.78
12 2026-08-24 04:56 639231437208519473
3 ms 37.156.246.78
11 2026-08-24 04:39 639231427209627490
180 ms 37.156.246.78
10 2026-08-24 03:46 639231395791246644
32 ms 37.156.246.78
9 2026-08-24 03:30 639231386075551458
98 ms 37.156.246.78
8 2026-08-24 03:14 639231376208713791
89 ms 37.156.246.78
7 2026-08-24 02:57 639231366170589276
182 ms 37.156.246.78
6 2026-08-24 02:05 639231334732159368
7 ms 37.156.246.78
5 2026-08-24 01:49 639231325035670078
3 ms 37.156.246.78
4 2026-08-24 01:32 639231315132253837
85 ms 37.156.246.78
3 2026-08-24 01:15 639231305014280808
2011 ms 37.156.246.78
2 2026-08-24 00:23 639231273779380675
8 ms 37.156.246.78
1 2026-08-24 00:07 639231264180839154
7 ms 37.156.246.78