DNS response history for ns1-r1-sanjose.webserversystems.com

ns1-r1-sanjose.webserversystems.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-27. For this date, NameServerHistory found 34 DNS check records, 34 successful responses, 0 failed responses, and 335 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 ns1-r1-sanjose.webserversystems.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

335 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 10:54

All timestamps shown in UTC

Latest Resolved IP on Selected Date

162.144.228.85

Most recently resolved hosting IP on selected date

Successful Responses

34

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 ns1-r1-sanjose.webserversystems.com

Showing DNS history for 2026-08-27 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
34 2026-08-27 10:54 639234243654907465
152 ms 162.144.228.85
33 2026-08-27 10:37 639234233269654413
173 ms 162.144.228.85
32 2026-08-27 10:20 639234222943951923
147 ms 162.144.228.85
31 2026-08-27 10:02 639234212558002823
147 ms 162.144.228.85
30 2026-08-27 09:45 639234202117531850
168 ms 162.144.228.85
29 2026-08-27 09:28 639234191649612722
160 ms 162.144.228.85
28 2026-08-27 09:10 639234181105879568
153 ms 162.144.228.85
27 2026-08-27 08:53 639234170713214496
150 ms 162.144.228.85
26 2026-08-27 08:35 639234160341037652
170 ms 162.144.228.85
25 2026-08-27 08:18 639234149799404224
151 ms 162.144.228.85
24 2026-08-27 08:01 639234139553286469
157 ms 162.144.228.85
23 2026-08-27 07:07 639234107183588293
146 ms 162.144.228.85
22 2026-08-27 06:50 639234096905435724
147 ms 162.144.228.85
21 2026-08-27 06:33 639234086579410775
2173 ms 162.144.228.85
20 2026-08-27 06:15 639234076291157956
149 ms 162.144.228.85
19 2026-08-27 05:58 639234065981939454
156 ms 162.144.228.85
18 2026-08-27 05:41 639234055548642997
143 ms 162.144.228.85
17 2026-08-27 05:24 639234045267979603
156 ms 162.144.228.85
16 2026-08-27 05:07 639234034999717463
148 ms 162.144.228.85
15 2026-08-27 04:49 639234024739225358
149 ms 162.144.228.85
14 2026-08-27 04:32 639234014311170162
153 ms 162.144.228.85
13 2026-08-27 04:15 639234003806017640
171 ms 162.144.228.85
12 2026-08-27 03:57 639233993356203030
199 ms 162.144.228.85
11 2026-08-27 03:04 639233961301716608
2149 ms 162.144.228.85
10 2026-08-27 02:47 639233950834200647
147 ms 162.144.228.85
9 2026-08-27 02:29 639233940431849026
146 ms 162.144.228.85
8 2026-08-27 02:12 639233930110596398
197 ms 162.144.228.85
7 2026-08-27 01:55 639233919705434540
2202 ms 162.144.228.85
6 2026-08-27 01:37 639233909452807845
149 ms 162.144.228.85
5 2026-08-27 01:20 639233899096420820
187 ms 162.144.228.85
4 2026-08-27 01:03 639233888707824939
150 ms 162.144.228.85
3 2026-08-27 00:46 639233878461203802
151 ms 162.144.228.85
2 2026-08-27 00:28 639233868060868209
148 ms 162.144.228.85
1 2026-08-27 00:11 639233857450922991
147 ms 162.144.228.85