DNS response history for ns2.800hosting.com

ns2.800hosting.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 32 DNS check records, 32 successful responses, 0 failed responses, and 344 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.800hosting.com.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

344 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-28 13:23

All timestamps shown in UTC

Latest Resolved IP on Selected Date

69.41.160.29

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.800hosting.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
32 2026-08-28 13:23 639235195230848570
350 ms 69.41.160.29
31 2026-08-28 13:06 639235184840503274
386 ms 69.41.160.29
30 2026-08-28 12:49 639235174453894956
356 ms 69.41.160.29
29 2026-08-28 12:31 639235163898672622
393 ms 69.41.160.29
28 2026-08-28 11:38 639235132147470568
333 ms 69.41.160.29
27 2026-08-28 11:21 639235121907744088
329 ms 69.41.160.29
26 2026-08-28 11:04 639235111428014262
355 ms 69.41.160.29
25 2026-08-28 10:46 639235100921813626
364 ms 69.41.160.29
24 2026-08-28 09:52 639235068670703481
360 ms 69.41.160.29
23 2026-08-28 09:35 639235058337459445
339 ms 69.41.160.29
22 2026-08-28 09:18 639235047825109146
337 ms 69.41.160.29
21 2026-08-28 09:00 639235037383229033
177 ms 69.41.160.29
20 2026-08-28 08:07 639235005619242711
326 ms 69.41.160.29
19 2026-08-28 07:50 639234995310346584
334 ms 69.41.160.29
18 2026-08-28 07:33 639234984946548933
376 ms 69.41.160.29
17 2026-08-28 07:15 639234974608077290
339 ms 69.41.160.29
16 2026-08-28 06:22 639234942529845595
340 ms 69.41.160.29
15 2026-08-28 06:05 639234932259126627
350 ms 69.41.160.29
14 2026-08-28 05:48 639234921916735988
335 ms 69.41.160.29
13 2026-08-28 05:30 639234911470038027
334 ms 69.41.160.29
12 2026-08-28 04:37 639234879588411654
338 ms 69.41.160.29
11 2026-08-28 04:20 639234869341589104
338 ms 69.41.160.29
10 2026-08-28 04:03 639234859012216675
380 ms 69.41.160.29
9 2026-08-28 03:46 639234848695364934
372 ms 69.41.160.29
8 2026-08-28 02:53 639234816952458162
355 ms 69.41.160.29
7 2026-08-28 02:36 639234806773081598
332 ms 69.41.160.29
6 2026-08-28 02:19 639234796382955255
333 ms 69.41.160.29
5 2026-08-28 02:01 639234786015782563
368 ms 69.41.160.29
4 2026-08-28 01:08 639234753811917646
344 ms 69.41.160.29
3 2026-08-28 00:51 639234743739767811
332 ms 69.41.160.29
2 2026-08-28 00:34 639234733372362811
367 ms 69.41.160.29
1 2026-08-28 00:16 639234723048550337
349 ms 69.41.160.29