DNS response history for ns2.sequel.one

ns2.sequel.one 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-28. For this date, NameServerHistory found 32 DNS check records, 32 successful responses, 0 failed responses, and 118 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.sequel.one.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

118 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-28 13:17

All timestamps shown in UTC

Latest Resolved IP on Selected Date

87.106.111.187

Most recently resolved hosting IP on selected date

Successful Responses

32

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.sequel.one

Showing DNS history for 2026-08-28 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
32 2026-08-28 13:17 639235195230848570
51 ms 87.106.111.187
31 2026-08-28 13:00 639235184840503274
54 ms 87.106.111.187
30 2026-08-28 12:42 639235174453894956
49 ms 87.106.111.187
29 2026-08-28 12:25 639235163898672622
46 ms 87.106.111.187
28 2026-08-28 11:32 639235132147470568
28 ms 87.106.111.187
27 2026-08-28 11:15 639235121907744088
46 ms 87.106.111.187
26 2026-08-28 10:58 639235111428014262
104 ms 87.106.111.187
25 2026-08-28 10:40 639235100921813626
57 ms 87.106.111.187
24 2026-08-28 09:46 639235068670703481
200 ms 87.106.111.187
23 2026-08-28 09:29 639235058337459445
40 ms 87.106.111.187
22 2026-08-28 09:11 639235047825109146
27 ms 87.106.111.187
21 2026-08-28 08:54 639235037383229033
60 ms 87.106.111.187
20 2026-08-28 08:01 639235005619242711
47 ms 87.106.111.187
19 2026-08-28 07:44 639234995310346584
53 ms 87.106.111.187
18 2026-08-28 07:27 639234984946548933
47 ms 87.106.111.187
17 2026-08-28 07:09 639234974608077290
64 ms 87.106.111.187
16 2026-08-28 06:16 639234942529845595
42 ms 87.106.111.187
15 2026-08-28 05:59 639234932259126627
56 ms 87.106.111.187
14 2026-08-28 05:41 639234921916735988
66 ms 87.106.111.187
13 2026-08-28 05:24 639234911470038027
56 ms 87.106.111.187
12 2026-08-28 04:31 639234879588411654
3 ms 87.106.111.187
11 2026-08-28 04:14 639234869341589104
2021 ms 87.106.111.187
10 2026-08-28 03:57 639234859012216675
74 ms 87.106.111.187
9 2026-08-28 03:39 639234848695364934
45 ms 87.106.111.187
8 2026-08-28 02:47 639234816952458162
43 ms 87.106.111.187
7 2026-08-28 02:30 639234806773081598
6 ms 87.106.111.187
6 2026-08-28 02:12 639234796382955255
61 ms 87.106.111.187
5 2026-08-28 01:55 639234786015782563
45 ms 87.106.111.187
4 2026-08-28 01:01 639234753811917646
66 ms 87.106.111.187
3 2026-08-28 00:45 639234743739767811
3 ms 87.106.111.187
2 2026-08-28 00:27 639234733372362811
173 ms 87.106.111.187
1 2026-08-28 00:10 639234723048550337
55 ms 87.106.111.187