DNS response history for luxor.warcorp.com

luxor.warcorp.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 35 DNS check records, 35 successful responses, 0 failed responses, and 497 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 luxor.warcorp.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

497 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:07

All timestamps shown in UTC

Latest Resolved IP on Selected Date

108.26.139.60

Most recently resolved hosting IP on selected date

Successful Responses

35

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 luxor.warcorp.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
35 2026-08-25 12:07 639232556111768563
1046 ms 108.26.139.60
34 2026-08-25 11:50 639232545839529039
339 ms 108.26.139.60
33 2026-08-25 11:33 639232535349285207
392 ms 108.26.139.60
32 2026-08-25 11:15 639232524938080723
373 ms 108.26.139.60
31 2026-08-25 10:22 639232492740373468
342 ms 108.26.139.60
30 2026-08-25 10:05 639232482235303141
499 ms 108.26.139.60
29 2026-08-25 09:47 639232471861770303
521 ms 108.26.139.60
28 2026-08-25 09:30 639232461630217327
366 ms 108.26.139.60
27 2026-08-25 09:13 639232451282965990
394 ms 108.26.139.60
26 2026-08-25 08:55 639232440814614938
349 ms 108.26.139.60
25 2026-08-25 08:38 639232430410720425
623 ms 108.26.139.60
24 2026-08-25 08:21 639232420003096185
782 ms 108.26.139.60
23 2026-08-25 08:03 639232409467287444
353 ms 108.26.139.60
22 2026-08-25 07:46 639232399077195997
495 ms 108.26.139.60
21 2026-08-25 07:28 639232388731528337
485 ms 108.26.139.60
20 2026-08-25 07:11 639232378288598612
309 ms 108.26.139.60
19 2026-08-25 06:17 639232346196373643
305 ms 108.26.139.60
18 2026-08-25 06:00 639232336112370741
363 ms 108.26.139.60
17 2026-08-25 05:44 639232326146508970
438 ms 108.26.139.60
16 2026-08-25 05:27 639232316189381720
438 ms 108.26.139.60
15 2026-08-25 05:11 639232306217998913
751 ms 108.26.139.60
14 2026-08-25 04:54 639232296255744174
370 ms 108.26.139.60
13 2026-08-25 04:37 639232286095760789
437 ms 108.26.139.60
12 2026-08-25 04:20 639232276086186273
309 ms 108.26.139.60
11 2026-08-25 04:04 639232265900986425
633 ms 108.26.139.60
10 2026-08-25 03:47 639232255723518075
390 ms 108.26.139.60
9 2026-08-25 03:30 639232245484452890
1204 ms 108.26.139.60
8 2026-08-25 03:13 639232235157175331
397 ms 108.26.139.60
7 2026-08-25 02:19 639232203197189095
309 ms 108.26.139.60
6 2026-08-25 02:02 639232192844564298
593 ms 108.26.139.60
5 2026-08-25 01:45 639232182496008942
614 ms 108.26.139.60
4 2026-08-25 01:27 639232172197053132
334 ms 108.26.139.60
3 2026-08-25 00:34 639232140250307418
885 ms 108.26.139.60
2 2026-08-25 00:17 639232129927860324
383 ms 108.26.139.60
1 2026-08-25 00:00 639232119551972438
566 ms 108.26.139.60