DNS response history for pdx.ketrenos.com

pdx.ketrenos.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 31 DNS check records, 31 successful responses, 0 failed responses, and 985 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 pdx.ketrenos.com.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

985 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:23

All timestamps shown in UTC

Latest Resolved IP on Selected Date

50.39.247.22

Most recently resolved hosting IP on selected date

Successful Responses

31

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 pdx.ketrenos.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
31 2026-08-25 10:23 639232492740373468
321 ms 50.39.247.22
30 2026-08-25 10:06 639232482235303141
320 ms 50.39.247.22
29 2026-08-25 09:48 639232471861770303
2211 ms 50.39.247.22
28 2026-08-25 09:31 639232461630217327
324 ms 50.39.247.22
27 2026-08-25 09:14 639232451282965990
2163 ms 50.39.247.22
26 2026-08-25 08:57 639232440814614938
335 ms 50.39.247.22
25 2026-08-25 08:39 639232430410720425
2167 ms 50.39.247.22
24 2026-08-25 08:22 639232420003096185
337 ms 50.39.247.22
23 2026-08-25 08:04 639232409467287444
163 ms 50.39.247.22
22 2026-08-25 07:47 639232399077195997
174 ms 50.39.247.22
21 2026-08-25 07:30 639232388731528337
2175 ms 50.39.247.22
20 2026-08-25 07:12 639232378288598612
329 ms 50.39.247.22
19 2026-08-25 06:18 639232346196373643
2206 ms 50.39.247.22
18 2026-08-25 06:02 639232336112370741
341 ms 50.39.247.22
17 2026-08-25 05:45 639232326146508970
2172 ms 50.39.247.22
16 2026-08-25 05:28 639232316189381720
2 ms 50.39.247.22
15 2026-08-25 05:12 639232306217998913
2 ms 50.39.247.22
14 2026-08-25 04:55 639232296255744174
2204 ms 50.39.247.22
13 2026-08-25 04:38 639232286095760789
347 ms 50.39.247.22
12 2026-08-25 04:21 639232276086186273
163 ms 50.39.247.22
11 2026-08-25 04:05 639232265900986425
2166 ms 50.39.247.22
10 2026-08-25 03:48 639232255723518075
158 ms 50.39.247.22
9 2026-08-25 03:31 639232245484452890
321 ms 50.39.247.22
8 2026-08-25 03:14 639232235157175331
2164 ms 50.39.247.22
7 2026-08-25 02:20 639232203197189095
2164 ms 50.39.247.22
6 2026-08-25 02:03 639232192844564298
2268 ms 50.39.247.22
5 2026-08-25 01:46 639232182496008942
4 ms 50.39.247.22
4 2026-08-25 01:29 639232172197053132
318 ms 50.39.247.22
3 2026-08-25 00:35 639232140250307418
3 ms 50.39.247.22
2 2026-08-25 00:18 639232129927860324
2179 ms 50.39.247.22
1 2026-08-25 00:01 639232119551972438
335 ms 50.39.247.22