DNS response history for ns2.corpocredit1.com

ns2.corpocredit1.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 30 DNS check records, 30 successful responses, 0 failed responses, and 304 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.corpocredit1.com.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

304 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:20

All timestamps shown in UTC

Latest Resolved IP on Selected Date

200.74.196.163

Most recently resolved hosting IP on selected date

Successful Responses

30

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.corpocredit1.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
30 2026-08-25 10:20 639232492740373468
289 ms 200.74.196.163
29 2026-08-25 10:02 639232482235303141
306 ms 200.74.196.163
28 2026-08-25 09:45 639232471861770303
161 ms 200.74.196.163
27 2026-08-25 09:28 639232461630217327
321 ms 200.74.196.163
26 2026-08-25 09:10 639232451282965990
7 ms 200.74.196.163
25 2026-08-25 08:53 639232440814614938
334 ms 200.74.196.163
24 2026-08-25 08:36 639232430410720425
409 ms 200.74.196.163
23 2026-08-25 08:18 639232420003096185
174 ms 200.74.196.163
22 2026-08-25 08:01 639232409467287444
6 ms 200.74.196.163
21 2026-08-25 07:43 639232399077195997
301 ms 200.74.196.163
20 2026-08-25 07:26 639232388731528337
295 ms 200.74.196.163
19 2026-08-25 07:09 639232378288598612
318 ms 200.74.196.163
18 2026-08-25 06:15 639232346196373643
3 ms 200.74.196.163
17 2026-08-25 05:58 639232336112370741
4 ms 200.74.196.163
16 2026-08-25 05:42 639232326146508970
3 ms 200.74.196.163
15 2026-08-25 05:25 639232316189381720
297 ms 200.74.196.163
14 2026-08-25 05:09 639232306217998913
315 ms 200.74.196.163
13 2026-08-25 04:52 639232296255744174
143 ms 200.74.196.163
12 2026-08-25 04:35 639232286095760789
2 ms 200.74.196.163
11 2026-08-25 04:18 639232276086186273
300 ms 200.74.196.163
10 2026-08-25 04:01 639232265900986425
292 ms 200.74.196.163
9 2026-08-25 03:44 639232255723518075
320 ms 200.74.196.163
8 2026-08-25 03:27 639232245484452890
316 ms 200.74.196.163
7 2026-08-25 03:10 639232235157175331
508 ms 200.74.196.163
6 2026-08-25 02:17 639232203197189095
2157 ms 200.74.196.163
5 2026-08-25 02:00 639232192844564298
316 ms 200.74.196.163
4 2026-08-25 01:43 639232182496008942
322 ms 200.74.196.163
3 2026-08-25 01:25 639232172197053132
289 ms 200.74.196.163
2 2026-08-25 00:32 639232140250307418
311 ms 200.74.196.163
1 2026-08-25 00:15 639232129927860324
306 ms 200.74.196.163