DNS response history for ns2.infocred.bo

ns2.infocred.bo 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, 29 successful responses, 1 failed responses, and 403 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.infocred.bo.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

403 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:21

All timestamps shown in UTC

Latest Resolved IP on Selected Date

181.188.173.210

Most recently resolved hosting IP on selected date

Successful Responses

29

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.infocred.bo

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:21 639232492740373468
218 ms 181.188.173.210
29 2026-08-25 10:04 639232482235303141
220 ms 181.188.173.210
28 2026-08-25 09:46 639232471861770303
224 ms 181.188.173.210
27 2026-08-25 09:29 639232461630217327
1991 ms 181.188.173.210
26 2026-08-25 09:12 639232451282965990
714 ms 181.188.173.210
25 2026-08-25 08:55 639232440814614938
213 ms 181.188.173.210
24 2026-08-25 08:37 639232430410720425
212 ms 181.188.173.210
23 2026-08-25 08:20 639232420003096185
210 ms 181.188.173.210
22 2026-08-25 08:03 639232409467287444
911 ms 181.188.173.210
21 2026-08-25 07:45 639232399077195997
211 ms 181.188.173.210
20 2026-08-25 07:28 639232388731528337
210 ms 181.188.173.210
19 2026-08-25 07:10 639232378288598612
210 ms 181.188.173.210
18 2026-08-25 06:17 639232346196373643
209 ms 181.188.173.210
17 2026-08-25 06:00 639232336112370741
-
16 2026-08-25 05:43 639232326146508970
218 ms 181.188.173.210
15 2026-08-25 05:27 639232316189381720
712 ms 181.188.173.210
14 2026-08-25 05:10 639232306217998913
214 ms 181.188.173.210
13 2026-08-25 04:53 639232296255744174
709 ms 181.188.173.210
12 2026-08-25 04:37 639232286095760789
209 ms 181.188.173.210
11 2026-08-25 04:20 639232276086186273
208 ms 181.188.173.210
10 2026-08-25 04:03 639232265900986425
212 ms 181.188.173.210
9 2026-08-25 03:46 639232255723518075
222 ms 181.188.173.210
8 2026-08-25 03:29 639232245484452890
208 ms 181.188.173.210
7 2026-08-25 03:12 639232235157175331
212 ms 181.188.173.210
6 2026-08-25 02:18 639232203197189095
711 ms 181.188.173.210
5 2026-08-25 02:01 639232192844564298
238 ms 181.188.173.210
4 2026-08-25 01:44 639232182496008942
716 ms 181.188.173.210
3 2026-08-25 01:27 639232172197053132
211 ms 181.188.173.210
2 2026-08-25 00:33 639232140250307418
216 ms 181.188.173.210
1 2026-08-25 00:17 639232129927860324
712 ms 181.188.173.210