DNS response history for ns2.polypaths.com

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

32

Historical checks stored for this nameserver on selected date

Average Latency

372 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:30

All timestamps shown in UTC

Latest Resolved IP on Selected Date

96.44.131.179

Most recently resolved hosting IP on selected date

Successful Responses

32

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.polypaths.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
32 2026-08-25 11:30 639232535349285207
327 ms 96.44.131.179
31 2026-08-25 11:13 639232524938080723
341 ms 96.44.131.179
30 2026-08-25 10:19 639232492740373468
334 ms 96.44.131.179
29 2026-08-25 10:02 639232482235303141
325 ms 96.44.131.179
28 2026-08-25 09:45 639232471861770303
338 ms 96.44.131.179
27 2026-08-25 09:27 639232461630217327
174 ms 96.44.131.179
26 2026-08-25 09:10 639232451282965990
334 ms 96.44.131.179
25 2026-08-25 08:53 639232440814614938
329 ms 96.44.131.179
24 2026-08-25 08:36 639232430410720425
341 ms 96.44.131.179
23 2026-08-25 08:18 639232420003096185
340 ms 96.44.131.179
22 2026-08-25 08:01 639232409467287444
328 ms 96.44.131.179
21 2026-08-25 07:43 639232399077195997
351 ms 96.44.131.179
20 2026-08-25 07:26 639232388731528337
340 ms 96.44.131.179
19 2026-08-25 07:09 639232378288598612
339 ms 96.44.131.179
18 2026-08-25 06:15 639232346196373643
196 ms 96.44.131.179
17 2026-08-25 05:58 639232336112370741
330 ms 96.44.131.179
16 2026-08-25 05:41 639232326146508970
201 ms 96.44.131.179
15 2026-08-25 05:25 639232316189381720
321 ms 96.44.131.179
14 2026-08-25 05:08 639232306217998913
322 ms 96.44.131.179
13 2026-08-25 04:52 639232296255744174
364 ms 96.44.131.179
12 2026-08-25 04:35 639232286095760789
327 ms 96.44.131.179
11 2026-08-25 04:18 639232276086186273
326 ms 96.44.131.179
10 2026-08-25 04:01 639232265900986425
331 ms 96.44.131.179
9 2026-08-25 03:44 639232255723518075
333 ms 96.44.131.179
8 2026-08-25 03:27 639232245484452890
327 ms 96.44.131.179
7 2026-08-25 03:10 639232235157175331
186 ms 96.44.131.179
6 2026-08-25 02:17 639232203197189095
328 ms 96.44.131.179
5 2026-08-25 02:00 639232192844564298
322 ms 96.44.131.179
4 2026-08-25 01:42 639232182496008942
324 ms 96.44.131.179
3 2026-08-25 01:25 639232172197053132
329 ms 96.44.131.179
2 2026-08-25 00:32 639232140250307418
322 ms 96.44.131.179
1 2026-08-25 00:15 639232129927860324
2172 ms 96.44.131.179