DNS response history for ns2.infostreamz.com

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

34

Historical checks stored for this nameserver on selected date

Average Latency

485 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:03

All timestamps shown in UTC

Latest Resolved IP on Selected Date

195.250.20.175

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 ns2.infostreamz.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
34 2026-08-25 12:03 639232556111768563
278 ms 195.250.20.175
33 2026-08-25 11:46 639232545839529039
264 ms 195.250.20.175
32 2026-08-25 11:28 639232535349285207
267 ms 195.250.20.175
31 2026-08-25 11:11 639232524938080723
281 ms 195.250.20.175
30 2026-08-25 10:17 639232492740373468
387 ms 195.250.20.175
29 2026-08-25 10:00 639232482235303141
266 ms 195.250.20.175
28 2026-08-25 09:42 639232471861770303
269 ms 195.250.20.175
27 2026-08-25 09:25 639232461630217327
273 ms 195.250.20.175
26 2026-08-25 09:08 639232451282965990
265 ms 195.250.20.175
25 2026-08-25 08:51 639232440814614938
150 ms 195.250.20.175
24 2026-08-25 08:33 639232430410720425
4372 ms 195.250.20.175
23 2026-08-25 08:16 639232420003096185
267 ms 195.250.20.175
22 2026-08-25 07:59 639232409467287444
278 ms 195.250.20.175
21 2026-08-25 07:41 639232399077195997
186 ms 195.250.20.175
20 2026-08-25 07:24 639232388731528337
263 ms 195.250.20.175
19 2026-08-25 07:07 639232378288598612
2137 ms 195.250.20.175
18 2026-08-25 06:13 639232346196373643
264 ms 195.250.20.175
17 2026-08-25 05:56 639232336112370741
151 ms 195.250.20.175
16 2026-08-25 05:40 639232326146508970
4 ms 195.250.20.175
15 2026-08-25 05:23 639232316189381720
281 ms 195.250.20.175
14 2026-08-25 05:06 639232306217998913
255 ms 195.250.20.175
13 2026-08-25 04:50 639232296255744174
271 ms 195.250.20.175
12 2026-08-25 04:33 639232286095760789
270 ms 195.250.20.175
11 2026-08-25 04:16 639232276086186273
267 ms 195.250.20.175
10 2026-08-25 03:59 639232265900986425
2384 ms 195.250.20.175
9 2026-08-25 03:42 639232255723518075
269 ms 195.250.20.175
8 2026-08-25 03:25 639232245484452890
294 ms 195.250.20.175
7 2026-08-25 03:08 639232235157175331
314 ms 195.250.20.175
6 2026-08-25 02:15 639232203197189095
281 ms 195.250.20.175
5 2026-08-25 01:58 639232192844564298
9 ms 195.250.20.175
4 2026-08-25 01:40 639232182496008942
296 ms 195.250.20.175
3 2026-08-25 01:23 639232172197053132
151 ms 195.250.20.175
2 2026-08-25 00:30 639232140250307418
254 ms 195.250.20.175
1 2026-08-25 00:13 639232129927860324
282 ms 195.250.20.175