DNS response history for ns2.plusign.com

ns2.plusign.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 248 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.plusign.com.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

248 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:28

All timestamps shown in UTC

Latest Resolved IP on Selected Date

209.95.48.157

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.plusign.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:28 639232535349285207
146 ms 209.95.48.157
31 2026-08-25 11:10 639232524938080723
156 ms 209.95.48.157
30 2026-08-25 10:17 639232492740373468
277 ms 209.95.48.157
29 2026-08-25 10:00 639232482235303141
283 ms 209.95.48.157
28 2026-08-25 09:42 639232471861770303
443 ms 209.95.48.157
27 2026-08-25 09:25 639232461630217327
165 ms 209.95.48.157
26 2026-08-25 09:08 639232451282965990
163 ms 209.95.48.157
25 2026-08-25 08:50 639232440814614938
285 ms 209.95.48.157
24 2026-08-25 08:33 639232430410720425
143 ms 209.95.48.157
23 2026-08-25 08:16 639232420003096185
281 ms 209.95.48.157
22 2026-08-25 07:58 639232409467287444
291 ms 209.95.48.157
21 2026-08-25 07:41 639232399077195997
148 ms 209.95.48.157
20 2026-08-25 07:23 639232388731528337
285 ms 209.95.48.157
19 2026-08-25 07:06 639232378288598612
284 ms 209.95.48.157
18 2026-08-25 06:13 639232346196373643
162 ms 209.95.48.157
17 2026-08-25 05:56 639232336112370741
298 ms 209.95.48.157
16 2026-08-25 05:39 639232326146508970
274 ms 209.95.48.157
15 2026-08-25 05:22 639232316189381720
273 ms 209.95.48.157
14 2026-08-25 05:06 639232306217998913
275 ms 209.95.48.157
13 2026-08-25 04:49 639232296255744174
278 ms 209.95.48.157
12 2026-08-25 04:32 639232286095760789
286 ms 209.95.48.157
11 2026-08-25 04:15 639232276086186273
150 ms 209.95.48.157
10 2026-08-25 03:59 639232265900986425
142 ms 209.95.48.157
9 2026-08-25 03:42 639232255723518075
277 ms 209.95.48.157
8 2026-08-25 03:25 639232245484452890
279 ms 209.95.48.157
7 2026-08-25 03:08 639232235157175331
283 ms 209.95.48.157
6 2026-08-25 02:14 639232203197189095
276 ms 209.95.48.157
5 2026-08-25 01:57 639232192844564298
286 ms 209.95.48.157
4 2026-08-25 01:40 639232182496008942
282 ms 209.95.48.157
3 2026-08-25 01:23 639232172197053132
282 ms 209.95.48.157
2 2026-08-25 00:29 639232140250307418
199 ms 209.95.48.157
1 2026-08-25 00:12 639232129927860324
279 ms 209.95.48.157