DNS response history for ns2.perfectmarketingsolution.com

ns2.perfectmarketingsolution.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 498 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.perfectmarketingsolution.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

498 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:02

All timestamps shown in UTC

Latest Resolved IP on Selected Date

209.126.84.220

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.perfectmarketingsolution.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:02 639232556111768563
244 ms 209.126.84.220
33 2026-08-25 11:45 639232545839529039
501 ms 209.126.84.220
32 2026-08-25 11:28 639232535349285207
245 ms 209.126.84.220
31 2026-08-25 11:10 639232524938080723
246 ms 209.126.84.220
30 2026-08-25 10:17 639232492740373468
4178 ms 209.126.84.220
29 2026-08-25 09:59 639232482235303141
250 ms 209.126.84.220
28 2026-08-25 09:42 639232471861770303
246 ms 209.126.84.220
27 2026-08-25 09:25 639232461630217327
244 ms 209.126.84.220
26 2026-08-25 09:07 639232451282965990
268 ms 209.126.84.220
25 2026-08-25 08:50 639232440814614938
7 ms 209.126.84.220
24 2026-08-25 08:33 639232430410720425
235 ms 209.126.84.220
23 2026-08-25 08:15 639232420003096185
243 ms 209.126.84.220
22 2026-08-25 07:58 639232409467287444
265 ms 209.126.84.220
21 2026-08-25 07:41 639232399077195997
2034 ms 209.126.84.220
20 2026-08-25 07:23 639232388731528337
246 ms 209.126.84.220
19 2026-08-25 07:06 639232378288598612
235 ms 209.126.84.220
18 2026-08-25 06:12 639232346196373643
230 ms 209.126.84.220
17 2026-08-25 05:55 639232336112370741
23 ms 209.126.84.220
16 2026-08-25 05:39 639232326146508970
2257 ms 209.126.84.220
15 2026-08-25 05:22 639232316189381720
9 ms 209.126.84.220
14 2026-08-25 05:06 639232306217998913
245 ms 209.126.84.220
13 2026-08-25 04:49 639232296255744174
255 ms 209.126.84.220
12 2026-08-25 04:32 639232286095760789
248 ms 209.126.84.220
11 2026-08-25 04:15 639232276086186273
245 ms 209.126.84.220
10 2026-08-25 03:59 639232265900986425
12 ms 209.126.84.220
9 2026-08-25 03:42 639232255723518075
9 ms 209.126.84.220
8 2026-08-25 03:24 639232245484452890
251 ms 209.126.84.220
7 2026-08-25 03:07 639232235157175331
242 ms 209.126.84.220
6 2026-08-25 02:14 639232203197189095
9 ms 209.126.84.220
5 2026-08-25 01:57 639232192844564298
229 ms 209.126.84.220
4 2026-08-25 01:40 639232182496008942
245 ms 209.126.84.220
3 2026-08-25 01:22 639232172197053132
245 ms 209.126.84.220
2 2026-08-25 00:29 639232140250307418
247 ms 209.126.84.220
1 2026-08-25 00:12 639232129927860324
2244 ms 209.126.84.220