DNS response history for ns2.jrsepulcre.com

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

35

Historical checks stored for this nameserver on selected date

Average Latency

307 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 11:05

All timestamps shown in UTC

Latest Resolved IP on Selected Date

194.164.160.176

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 ns2.jrsepulcre.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
35 2026-08-27 11:05 639234253963286387
130 ms 194.164.160.176
34 2026-08-27 10:48 639234243654907465
101 ms 194.164.160.176
33 2026-08-27 10:31 639234233269654413
92 ms 194.164.160.176
32 2026-08-27 10:14 639234222943951923
47 ms 194.164.160.176
31 2026-08-27 09:56 639234212558002823
58 ms 194.164.160.176
30 2026-08-27 09:39 639234202117531850
93 ms 194.164.160.176
29 2026-08-27 09:21 639234191649612722
95 ms 194.164.160.176
28 2026-08-27 09:04 639234181105879568
18 ms 194.164.160.176
27 2026-08-27 08:47 639234170713214496
77 ms 194.164.160.176
26 2026-08-27 08:29 639234160341037652
115 ms 194.164.160.176
25 2026-08-27 08:12 639234149799404224
95 ms 194.164.160.176
24 2026-08-27 07:55 639234139553286469
52 ms 194.164.160.176
23 2026-08-27 07:01 639234107183588293
76 ms 194.164.160.176
22 2026-08-27 06:44 639234096905435724
114 ms 194.164.160.176
21 2026-08-27 06:27 639234086579410775
96 ms 194.164.160.176
20 2026-08-27 06:09 639234076291157956
108 ms 194.164.160.176
19 2026-08-27 05:52 639234065981939454
11 ms 194.164.160.176
18 2026-08-27 05:35 639234055548642997
21 ms 194.164.160.176
17 2026-08-27 05:18 639234045267979603
57 ms 194.164.160.176
16 2026-08-27 05:01 639234034999717463
90 ms 194.164.160.176
15 2026-08-27 04:43 639234024739225358
176 ms 194.164.160.176
14 2026-08-27 04:26 639234014311170162
95 ms 194.164.160.176
13 2026-08-27 04:09 639234003806017640
4048 ms 194.164.160.176
12 2026-08-27 03:51 639233993356203030
48 ms 194.164.160.176
11 2026-08-27 02:58 639233961301716608
75 ms 194.164.160.176
10 2026-08-27 02:40 639233950834200647
58 ms 194.164.160.176
9 2026-08-27 02:23 639233940431849026
2012 ms 194.164.160.176
8 2026-08-27 02:06 639233930110596398
108 ms 194.164.160.176
7 2026-08-27 01:48 639233919705434540
91 ms 194.164.160.176
6 2026-08-27 01:31 639233909452807845
70 ms 194.164.160.176
5 2026-08-27 01:14 639233899096420820
93 ms 194.164.160.176
4 2026-08-27 00:57 639233888707824939
92 ms 194.164.160.176
3 2026-08-27 00:40 639233878461203802
2045 ms 194.164.160.176
2 2026-08-27 00:22 639233868060868209
99 ms 194.164.160.176
1 2026-08-27 00:05 639233857450922991
77 ms 194.164.160.176