DNS response history for ns1.notarypublicsanfranciscoca.com

ns1.notarypublicsanfranciscoca.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-09-01. For this date, NameServerHistory found 37 DNS check records, 37 successful responses, 0 failed responses, and 525 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.notarypublicsanfranciscoca.com.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

525 ms

Calculated from available response records

Latest Check on Selected Date

2026-09-01 12:46

All timestamps shown in UTC

Latest Resolved IP on Selected Date

108.160.157.36

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 ns1.notarypublicsanfranciscoca.com

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:46 639238628486902752
487 ms 108.160.157.36
36 2026-09-01 12:28 639238617906743100
367 ms 108.160.157.36
35 2026-09-01 12:11 639238607506044626
4 ms 108.160.157.36
34 2026-09-01 11:53 639238597040761406
5 ms 108.160.157.36
33 2026-09-01 11:36 639238586261546969
429 ms 108.160.157.36
32 2026-09-01 11:18 639238575587642333
5 ms 108.160.157.36
31 2026-09-01 10:23 639238543127398267
448 ms 108.160.157.36
30 2026-09-01 10:06 639238532668234016
649 ms 108.160.157.36
29 2026-09-01 09:48 639238522029321761
474 ms 108.160.157.36
28 2026-09-01 09:31 639238511519050351
5 ms 108.160.157.36
27 2026-09-01 09:13 639238500942239673
488 ms 108.160.157.36
26 2026-09-01 08:56 639238490412377398
492 ms 108.160.157.36
25 2026-09-01 08:38 639238479833203021
3 ms 108.160.157.36
24 2026-09-01 08:20 639238469140507479
3 ms 108.160.157.36
23 2026-09-01 08:03 639238458443560361
11 ms 108.160.157.36
22 2026-09-01 07:45 639238447694851502
472 ms 108.160.157.36
21 2026-09-01 07:26 639238436624109087
633 ms 108.160.157.36
20 2026-09-01 07:08 639238425565611335
462 ms 108.160.157.36
19 2026-09-01 06:12 639238392250222581
466 ms 108.160.157.36
18 2026-09-01 05:54 639238381322537831
4438 ms 108.160.157.36
17 2026-09-01 05:36 639238370248186084
2279 ms 108.160.157.36
16 2026-09-01 05:18 639238359264687845
433 ms 108.160.157.36
15 2026-09-01 04:59 639238348534621818
381 ms 108.160.157.36
14 2026-09-01 04:41 639238337725739433
426 ms 108.160.157.36
13 2026-09-01 04:23 639238326844749368
501 ms 108.160.157.36
12 2026-09-01 04:05 639238315792024737
474 ms 108.160.157.36
11 2026-09-01 03:47 639238304931064768
407 ms 108.160.157.36
10 2026-09-01 03:29 639238294131483803
406 ms 108.160.157.36
9 2026-09-01 03:11 639238283314985519
428 ms 108.160.157.36
8 2026-09-01 02:53 639238272374093187
388 ms 108.160.157.36
7 2026-09-01 01:58 639238240032549922
429 ms 108.160.157.36
6 2026-09-01 01:40 639238229204177368
418 ms 108.160.157.36
5 2026-09-01 01:22 639238218326150282
418 ms 108.160.157.36
4 2026-09-01 01:04 639238207574700853
410 ms 108.160.157.36
3 2026-09-01 00:46 639238196660283915
402 ms 108.160.157.36
2 2026-09-01 00:28 639238185782358546
442 ms 108.160.157.36
1 2026-09-01 00:10 639238175054391781
428 ms 108.160.157.36