DNS response history for ns2.bparke.net

ns2.bparke.net 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 28 DNS check records, 28 successful responses, 0 failed responses, and 908 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.bparke.net.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

908 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:31

All timestamps shown in UTC

Latest Resolved IP on Selected Date

72.34.35.43

Most recently resolved hosting IP on selected date

Successful Responses

28

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.bparke.net

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
28 2026-08-25 09:31 639232461630217327
420 ms 72.34.35.43
27 2026-08-25 09:13 639232451282965990
435 ms 72.34.35.43
26 2026-08-25 08:56 639232440814614938
421 ms 72.34.35.43
25 2026-08-25 08:39 639232430410720425
933 ms 72.34.35.43
24 2026-08-25 08:21 639232420003096185
302 ms 72.34.35.43
23 2026-08-25 08:04 639232409467287444
916 ms 72.34.35.43
22 2026-08-25 07:47 639232399077195997
1914 ms 72.34.35.43
21 2026-08-25 07:29 639232388731528337
1825 ms 72.34.35.43
20 2026-08-25 07:12 639232378288598612
1929 ms 72.34.35.43
19 2026-08-25 06:18 639232346196373643
929 ms 72.34.35.43
18 2026-08-25 06:01 639232336112370741
919 ms 72.34.35.43
17 2026-08-25 05:45 639232326146508970
1929 ms 72.34.35.43
16 2026-08-25 05:28 639232316189381720
929 ms 72.34.35.43
15 2026-08-25 05:11 639232306217998913
801 ms 72.34.35.43
14 2026-08-25 04:55 639232296255744174
420 ms 72.34.35.43
13 2026-08-25 04:38 639232286095760789
145 ms 72.34.35.43
12 2026-08-25 04:21 639232276086186273
927 ms 72.34.35.43
11 2026-08-25 04:04 639232265900986425
923 ms 72.34.35.43
10 2026-08-25 03:47 639232255723518075
1425 ms 72.34.35.43
9 2026-08-25 03:30 639232245484452890
438 ms 72.34.35.43
8 2026-08-25 03:13 639232235157175331
928 ms 72.34.35.43
7 2026-08-25 02:20 639232203197189095
936 ms 72.34.35.43
6 2026-08-25 02:03 639232192844564298
926 ms 72.34.35.43
5 2026-08-25 01:46 639232182496008942
928 ms 72.34.35.43
4 2026-08-25 01:28 639232172197053132
423 ms 72.34.35.43
3 2026-08-25 00:35 639232140250307418
570 ms 72.34.35.43
2 2026-08-25 00:18 639232129927860324
919 ms 72.34.35.43
1 2026-08-25 00:01 639232119551972438
924 ms 72.34.35.43