DNS response history for ns2.pornok.org

ns2.pornok.org 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 300 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.pornok.org.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

300 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:40

All timestamps shown in UTC

Latest Resolved IP on Selected Date

167.114.173.60

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.pornok.org

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:40 639232471861770303
103 ms 167.114.173.60
27 2026-08-25 09:23 639232461630217327
106 ms 167.114.173.60
26 2026-08-25 09:06 639232451282965990
231 ms 167.114.173.60
25 2026-08-25 08:48 639232440814614938
113 ms 167.114.173.60
24 2026-08-25 08:31 639232430410720425
131 ms 167.114.173.60
23 2026-08-25 08:14 639232420003096185
106 ms 167.114.173.60
22 2026-08-25 07:56 639232409467287444
5 ms 167.114.173.60
21 2026-08-25 07:39 639232399077195997
110 ms 167.114.173.60
20 2026-08-25 07:21 639232388731528337
591 ms 167.114.173.60
19 2026-08-25 07:04 639232378288598612
2236 ms 167.114.173.60
18 2026-08-25 06:10 639232346196373643
332 ms 167.114.173.60
17 2026-08-25 05:54 639232336112370741
107 ms 167.114.173.60
16 2026-08-25 05:37 639232326146508970
345 ms 167.114.173.60
15 2026-08-25 05:20 639232316189381720
104 ms 167.114.173.60
14 2026-08-25 05:04 639232306217998913
118 ms 167.114.173.60
13 2026-08-25 04:47 639232296255744174
2105 ms 167.114.173.60
12 2026-08-25 04:30 639232286095760789
107 ms 167.114.173.60
11 2026-08-25 04:13 639232276086186273
124 ms 167.114.173.60
10 2026-08-25 03:57 639232265900986425
221 ms 167.114.173.60
9 2026-08-25 03:40 639232255723518075
7 ms 167.114.173.60
8 2026-08-25 03:23 639232245484452890
107 ms 167.114.173.60
7 2026-08-25 03:05 639232235157175331
8 ms 167.114.173.60
6 2026-08-25 02:12 639232203197189095
239 ms 167.114.173.60
5 2026-08-25 01:55 639232192844564298
248 ms 167.114.173.60
4 2026-08-25 01:38 639232182496008942
103 ms 167.114.173.60
3 2026-08-25 01:20 639232172197053132
115 ms 167.114.173.60
2 2026-08-25 00:27 639232140250307418
8 ms 167.114.173.60
1 2026-08-25 00:10 639232129927860324
278 ms 167.114.173.60