DNS response history for server39.sanjoseseo.company

server39.sanjoseseo.company 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-09-01. For this date, NameServerHistory found 37 DNS check records, 37 successful responses, 0 failed responses, and 833 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 server39.sanjoseseo.company.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

833 ms

Calculated from available response records

Latest Check on Selected Date

2026-09-01 12:47

All timestamps shown in UTC

Latest Resolved IP on Selected Date

66.23.195.156

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 server39.sanjoseseo.company

Showing DNS history for 2026-09-01 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-09-01 12:47 639238628486902752
4 ms 66.23.195.156
36 2026-09-01 12:30 639238617906743100
4 ms 66.23.195.156
35 2026-09-01 12:12 639238607506044626
130 ms 66.23.195.156
34 2026-09-01 11:55 639238597040761406
806 ms 66.23.195.156
33 2026-09-01 11:37 639238586261546969
658 ms 66.23.195.156
32 2026-09-01 11:19 639238575587642333
401 ms 66.23.195.156
31 2026-09-01 10:25 639238543127398267
1507 ms 66.23.195.156
30 2026-09-01 10:08 639238532668234016
533 ms 66.23.195.156
29 2026-09-01 09:50 639238522029321761
8 ms 66.23.195.156
28 2026-09-01 09:32 639238511519050351
758 ms 66.23.195.156
27 2026-09-01 09:15 639238500942239673
8 ms 66.23.195.156
26 2026-09-01 08:57 639238490412377398
4 ms 66.23.195.156
25 2026-09-01 08:40 639238479833203021
1059 ms 66.23.195.156
24 2026-09-01 08:22 639238469140507479
592 ms 66.23.195.156
23 2026-09-01 08:04 639238458443560361
4 ms 66.23.195.156
22 2026-09-01 07:46 639238447694851502
1249 ms 66.23.195.156
21 2026-09-01 07:28 639238436624109087
1392 ms 66.23.195.156
20 2026-09-01 07:10 639238425565611335
1529 ms 66.23.195.156
19 2026-09-01 06:14 639238392250222581
372 ms 66.23.195.156
18 2026-09-01 05:56 639238381322537831
839 ms 66.23.195.156
17 2026-09-01 05:38 639238370248186084
1628 ms 66.23.195.156
16 2026-09-01 05:19 639238359264687845
1154 ms 66.23.195.156
15 2026-09-01 05:01 639238348534621818
252 ms 66.23.195.156
14 2026-09-01 04:43 639238337725739433
1775 ms 66.23.195.156
13 2026-09-01 04:25 639238326844749368
263 ms 66.23.195.156
12 2026-09-01 04:07 639238315792024737
847 ms 66.23.195.156
11 2026-09-01 03:48 639238304931064768
250 ms 66.23.195.156
10 2026-09-01 03:30 639238294131483803
1664 ms 66.23.195.156
9 2026-09-01 03:12 639238283314985519
1619 ms 66.23.195.156
8 2026-09-01 02:54 639238272374093187
1495 ms 66.23.195.156
7 2026-09-01 02:00 639238240032549922
1128 ms 66.23.195.156
6 2026-09-01 01:42 639238229204177368
1615 ms 66.23.195.156
5 2026-09-01 01:24 639238218326150282
1661 ms 66.23.195.156
4 2026-09-01 01:06 639238207574700853
1463 ms 66.23.195.156
3 2026-09-01 00:48 639238196660283915
239 ms 66.23.195.156
2 2026-09-01 00:30 639238185782358546
1466 ms 66.23.195.156
1 2026-09-01 00:12 639238175054391781
462 ms 66.23.195.156