DNS response history for ns2.drivergent.com

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

33

Historical checks stored for this nameserver on selected date

Average Latency

470 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-28 14:16

All timestamps shown in UTC

Latest Resolved IP on Selected Date

162.214.55.209

Most recently resolved hosting IP on selected date

Successful Responses

33

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.drivergent.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
33 2026-08-28 14:16 639235227727862105
341 ms 162.214.55.209
32 2026-08-28 13:22 639235195230848570
350 ms 162.214.55.209
31 2026-08-28 13:05 639235184840503274
360 ms 162.214.55.209
30 2026-08-28 12:47 639235174453894956
332 ms 162.214.55.209
29 2026-08-28 12:30 639235163898672622
166 ms 162.214.55.209
28 2026-08-28 11:37 639235132147470568
346 ms 162.214.55.209
27 2026-08-28 11:20 639235121907744088
339 ms 162.214.55.209
26 2026-08-28 11:02 639235111428014262
2020 ms 162.214.55.209
25 2026-08-28 10:45 639235100921813626
160 ms 162.214.55.209
24 2026-08-28 09:51 639235068670703481
331 ms 162.214.55.209
23 2026-08-28 09:34 639235058337459445
339 ms 162.214.55.209
22 2026-08-28 09:16 639235047825109146
334 ms 162.214.55.209
21 2026-08-28 08:59 639235037383229033
336 ms 162.214.55.209
20 2026-08-28 08:06 639235005619242711
346 ms 162.214.55.209
19 2026-08-28 07:49 639234995310346584
2172 ms 162.214.55.209
18 2026-08-28 07:32 639234984946548933
345 ms 162.214.55.209
17 2026-08-28 07:14 639234974608077290
334 ms 162.214.55.209
16 2026-08-28 06:21 639234942529845595
346 ms 162.214.55.209
15 2026-08-28 06:04 639234932259126627
350 ms 162.214.55.209
14 2026-08-28 05:46 639234921916735988
336 ms 162.214.55.209
13 2026-08-28 05:29 639234911470038027
156 ms 162.214.55.209
12 2026-08-28 04:36 639234879588411654
333 ms 162.214.55.209
11 2026-08-28 04:19 639234869341589104
336 ms 162.214.55.209
10 2026-08-28 04:02 639234859012216675
163 ms 162.214.55.209
9 2026-08-28 03:44 639234848695364934
330 ms 162.214.55.209
8 2026-08-28 02:51 639234816952458162
339 ms 162.214.55.209
7 2026-08-28 02:35 639234806773081598
357 ms 162.214.55.209
6 2026-08-28 02:17 639234796382955255
8 ms 162.214.55.209
5 2026-08-28 02:00 639234786015782563
324 ms 162.214.55.209
4 2026-08-28 01:06 639234753811917646
332 ms 162.214.55.209
3 2026-08-28 00:49 639234743739767811
2172 ms 162.214.55.209
2 2026-08-28 00:32 639234733372362811
355 ms 162.214.55.209
1 2026-08-28 00:15 639234723048550337
332 ms 162.214.55.209