DNS response history for ns1.drivecms.com

ns1.drivecms.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-28. For this date, NameServerHistory found 29 DNS check records, 29 successful responses, 0 failed responses, and 304 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.drivecms.com.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

304 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-28 12:28

All timestamps shown in UTC

Latest Resolved IP on Selected Date

65.111.161.60

Most recently resolved hosting IP on selected date

Successful Responses

29

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.drivecms.com

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
29 2026-08-28 12:28 639235163898672622
262 ms 65.111.161.60
28 2026-08-28 11:35 639235132147470568
259 ms 65.111.161.60
27 2026-08-28 11:18 639235121907744088
260 ms 65.111.161.60
26 2026-08-28 11:01 639235111428014262
255 ms 65.111.161.60
25 2026-08-28 10:43 639235100921813626
256 ms 65.111.161.60
24 2026-08-28 09:49 639235068670703481
267 ms 65.111.161.60
23 2026-08-28 09:32 639235058337459445
154 ms 65.111.161.60
22 2026-08-28 09:15 639235047825109146
262 ms 65.111.161.60
21 2026-08-28 08:57 639235037383229033
258 ms 65.111.161.60
20 2026-08-28 08:04 639235005619242711
261 ms 65.111.161.60
19 2026-08-28 07:47 639234995310346584
256 ms 65.111.161.60
18 2026-08-28 07:30 639234984946548933
258 ms 65.111.161.60
17 2026-08-28 07:12 639234974608077290
262 ms 65.111.161.60
16 2026-08-28 06:19 639234942529845595
257 ms 65.111.161.60
15 2026-08-28 06:02 639234932259126627
2177 ms 65.111.161.60
14 2026-08-28 05:45 639234921916735988
272 ms 65.111.161.60
13 2026-08-28 05:27 639234911470038027
257 ms 65.111.161.60
12 2026-08-28 04:34 639234879588411654
258 ms 65.111.161.60
11 2026-08-28 04:17 639234869341589104
254 ms 65.111.161.60
10 2026-08-28 04:00 639234859012216675
125 ms 65.111.161.60
9 2026-08-28 03:42 639234848695364934
259 ms 65.111.161.60
8 2026-08-28 02:50 639234816952458162
254 ms 65.111.161.60
7 2026-08-28 02:33 639234806773081598
126 ms 65.111.161.60
6 2026-08-28 02:16 639234796382955255
257 ms 65.111.161.60
5 2026-08-28 01:58 639234786015782563
125 ms 65.111.161.60
4 2026-08-28 01:05 639234753811917646
143 ms 65.111.161.60
3 2026-08-28 00:48 639234743739767811
257 ms 65.111.161.60
2 2026-08-28 00:31 639234733372362811
254 ms 65.111.161.60
1 2026-08-28 00:13 639234723048550337
260 ms 65.111.161.60