DNS response history for ns2.portalify.com

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

27

Historical checks stored for this nameserver on selected date

Average Latency

128 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:25

All timestamps shown in UTC

Latest Resolved IP on Selected Date

83.145.199.50

Most recently resolved hosting IP on selected date

Successful Responses

27

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.portalify.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
27 2026-08-25 09:25 639232461630217327
72 ms 83.145.199.50
26 2026-08-25 09:08 639232451282965990
73 ms 83.145.199.50
25 2026-08-25 08:50 639232440814614938
7 ms 83.145.199.50
24 2026-08-25 08:33 639232430410720425
77 ms 83.145.199.50
23 2026-08-25 08:16 639232420003096185
10 ms 83.145.199.50
22 2026-08-25 07:58 639232409467287444
150 ms 83.145.199.50
21 2026-08-25 07:41 639232399077195997
74 ms 83.145.199.50
20 2026-08-25 07:23 639232388731528337
78 ms 83.145.199.50
19 2026-08-25 07:06 639232378288598612
75 ms 83.145.199.50
18 2026-08-25 06:12 639232346196373643
38 ms 83.145.199.50
17 2026-08-25 05:55 639232336112370741
46 ms 83.145.199.50
16 2026-08-25 05:39 639232326146508970
84 ms 83.145.199.50
15 2026-08-25 05:22 639232316189381720
5 ms 83.145.199.50
14 2026-08-25 05:06 639232306217998913
3 ms 83.145.199.50
13 2026-08-25 04:49 639232296255744174
71 ms 83.145.199.50
12 2026-08-25 04:32 639232286095760789
70 ms 83.145.199.50
11 2026-08-25 04:15 639232276086186273
11 ms 83.145.199.50
10 2026-08-25 03:59 639232265900986425
75 ms 83.145.199.50
9 2026-08-25 03:42 639232255723518075
71 ms 83.145.199.50
8 2026-08-25 03:25 639232245484452890
2041 ms 83.145.199.50
7 2026-08-25 03:07 639232235157175331
37 ms 83.145.199.50
6 2026-08-25 02:14 639232203197189095
41 ms 83.145.199.50
5 2026-08-25 01:57 639232192844564298
70 ms 83.145.199.50
4 2026-08-25 01:40 639232182496008942
69 ms 83.145.199.50
3 2026-08-25 01:22 639232172197053132
37 ms 83.145.199.50
2 2026-08-25 00:29 639232140250307418
37 ms 83.145.199.50
1 2026-08-25 00:12 639232129927860324
36 ms 83.145.199.50