DNS response history for n1.openresty.com

n1.openresty.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 37 DNS check records, 37 successful responses, 0 failed responses, and 390 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 n1.openresty.com.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

390 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:56

All timestamps shown in UTC

Latest Resolved IP on Selected Date

52.11.111.175

Most recently resolved hosting IP on selected date

Successful Responses

37

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 n1.openresty.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
37 2026-08-25 12:56 639232587225721862
320 ms 52.11.111.175
36 2026-08-25 12:39 639232576780683689
321 ms 52.11.111.175
35 2026-08-25 12:21 639232566381512620
311 ms 52.11.111.175
34 2026-08-25 12:04 639232556111768563
2174 ms 52.11.111.175
33 2026-08-25 11:47 639232545839529039
320 ms 52.11.111.175
32 2026-08-25 11:30 639232535349285207
170 ms 52.11.111.175
31 2026-08-25 11:12 639232524938080723
322 ms 52.11.111.175
30 2026-08-25 10:19 639232492740373468
313 ms 52.11.111.175
29 2026-08-25 10:01 639232482235303141
356 ms 52.11.111.175
28 2026-08-25 09:44 639232471861770303
208 ms 52.11.111.175
27 2026-08-25 09:27 639232461630217327
262 ms 52.11.111.175
26 2026-08-25 09:10 639232451282965990
320 ms 52.11.111.175
25 2026-08-25 08:52 639232440814614938
35 ms 52.11.111.175
24 2026-08-25 08:35 639232430410720425
325 ms 52.11.111.175
23 2026-08-25 08:18 639232420003096185
331 ms 52.11.111.175
22 2026-08-25 08:00 639232409467287444
164 ms 52.11.111.175
21 2026-08-25 07:43 639232399077195997
317 ms 52.11.111.175
20 2026-08-25 07:25 639232388731528337
317 ms 52.11.111.175
19 2026-08-25 07:08 639232378288598612
199 ms 52.11.111.175
18 2026-08-25 06:14 639232346196373643
330 ms 52.11.111.175
17 2026-08-25 05:57 639232336112370741
343 ms 52.11.111.175
16 2026-08-25 05:41 639232326146508970
314 ms 52.11.111.175
15 2026-08-25 05:24 639232316189381720
326 ms 52.11.111.175
14 2026-08-25 05:08 639232306217998913
161 ms 52.11.111.175
13 2026-08-25 04:51 639232296255744174
311 ms 52.11.111.175
12 2026-08-25 04:34 639232286095760789
306 ms 52.11.111.175
11 2026-08-25 04:17 639232276086186273
325 ms 52.11.111.175
10 2026-08-25 04:01 639232265900986425
493 ms 52.11.111.175
9 2026-08-25 03:44 639232255723518075
313 ms 52.11.111.175
8 2026-08-25 03:27 639232245484452890
315 ms 52.11.111.175
7 2026-08-25 03:09 639232235157175331
324 ms 52.11.111.175
6 2026-08-25 02:16 639232203197189095
319 ms 52.11.111.175
5 2026-08-25 01:59 639232192844564298
325 ms 52.11.111.175
4 2026-08-25 01:42 639232182496008942
2181 ms 52.11.111.175
3 2026-08-25 01:24 639232172197053132
160 ms 52.11.111.175
2 2026-08-25 00:31 639232140250307418
167 ms 52.11.111.175
1 2026-08-25 00:14 639232129927860324
314 ms 52.11.111.175