DNS response history for ns2.perfectbasement-marketing.com

ns2.perfectbasement-marketing.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 33 DNS check records, 33 successful responses, 0 failed responses, and 283 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.perfectbasement-marketing.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

283 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:40

All timestamps shown in UTC

Latest Resolved IP on Selected Date

92.204.41.150

Most recently resolved hosting IP on selected date

Successful Responses

33

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.perfectbasement-marketing.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
33 2026-08-25 11:40 639232545839529039
35 ms 92.204.41.150
32 2026-08-25 11:23 639232535349285207
31 ms 92.204.41.150
31 2026-08-25 11:05 639232524938080723
40 ms 92.204.41.150
30 2026-08-25 10:11 639232492740373468
11 ms 92.204.41.150
29 2026-08-25 09:54 639232482235303141
2015 ms 92.204.41.150
28 2026-08-25 09:37 639232471861770303
96 ms 92.204.41.150
27 2026-08-25 09:20 639232461630217327
59 ms 92.204.41.150
26 2026-08-25 09:02 639232451282965990
2065 ms 92.204.41.150
25 2026-08-25 08:45 639232440814614938
2071 ms 92.204.41.150
24 2026-08-25 08:28 639232430410720425
57 ms 92.204.41.150
23 2026-08-25 08:10 639232420003096185
46 ms 92.204.41.150
22 2026-08-25 07:53 639232409467287444
24 ms 92.204.41.150
21 2026-08-25 07:35 639232399077195997
23 ms 92.204.41.150
20 2026-08-25 07:18 639232388731528337
73 ms 92.204.41.150
19 2026-08-25 07:01 639232378288598612
45 ms 92.204.41.150
18 2026-08-25 06:07 639232346196373643
82 ms 92.204.41.150
17 2026-08-25 05:50 639232336112370741
19 ms 92.204.41.150
16 2026-08-25 05:34 639232326146508970
29 ms 92.204.41.150
15 2026-08-25 05:17 639232316189381720
54 ms 92.204.41.150
14 2026-08-25 05:01 639232306217998913
49 ms 92.204.41.150
13 2026-08-25 04:44 639232296255744174
2019 ms 92.204.41.150
12 2026-08-25 04:27 639232286095760789
32 ms 92.204.41.150
11 2026-08-25 04:10 639232276086186273
34 ms 92.204.41.150
10 2026-08-25 03:53 639232265900986425
37 ms 92.204.41.150
9 2026-08-25 03:36 639232255723518075
30 ms 92.204.41.150
8 2026-08-25 03:19 639232245484452890
44 ms 92.204.41.150
7 2026-08-25 03:02 639232235157175331
7 ms 92.204.41.150
6 2026-08-25 02:09 639232203197189095
30 ms 92.204.41.150
5 2026-08-25 01:52 639232192844564298
57 ms 92.204.41.150
4 2026-08-25 01:35 639232182496008942
16 ms 92.204.41.150
3 2026-08-25 01:17 639232172197053132
37 ms 92.204.41.150
2 2026-08-25 00:24 639232140250307418
26 ms 92.204.41.150
1 2026-08-25 00:07 639232129927860324
33 ms 92.204.41.150