DNS response history for ns2.box.bloggerprise.company

ns2.box.bloggerprise.company 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 26 DNS check records, 26 successful responses, 0 failed responses, and 387 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.box.bloggerprise.company.
Records on Selected Date

26

Historical checks stored for this nameserver on selected date

Average Latency

387 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-28 10:58

All timestamps shown in UTC

Latest Resolved IP on Selected Date

159.89.176.29

Most recently resolved hosting IP on selected date

Successful Responses

26

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.box.bloggerprise.company

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
26 2026-08-28 10:58 639235111428014262
40 ms 159.89.176.29
25 2026-08-28 10:41 639235100921813626
38 ms 159.89.176.29
24 2026-08-28 09:47 639235068670703481
261 ms 159.89.176.29
23 2026-08-28 09:30 639235058337459445
2045 ms 159.89.176.29
22 2026-08-28 09:12 639235047825109146
61 ms 159.89.176.29
21 2026-08-28 08:55 639235037383229033
45 ms 159.89.176.29
20 2026-08-28 08:02 639235005619242711
63 ms 159.89.176.29
19 2026-08-28 07:45 639234995310346584
2047 ms 159.89.176.29
18 2026-08-28 07:27 639234984946548933
31 ms 159.89.176.29
17 2026-08-28 07:10 639234974608077290
280 ms 159.89.176.29
16 2026-08-28 06:17 639234942529845595
164 ms 159.89.176.29
15 2026-08-28 06:00 639234932259126627
20 ms 159.89.176.29
14 2026-08-28 05:42 639234921916735988
11 ms 159.89.176.29
13 2026-08-28 05:25 639234911470038027
54 ms 159.89.176.29
12 2026-08-28 04:32 639234879588411654
143 ms 159.89.176.29
11 2026-08-28 04:15 639234869341589104
148 ms 159.89.176.29
10 2026-08-28 03:58 639234859012216675
36 ms 159.89.176.29
9 2026-08-28 03:40 639234848695364934
2039 ms 159.89.176.29
8 2026-08-28 02:47 639234816952458162
19 ms 159.89.176.29
7 2026-08-28 02:31 639234806773081598
10 ms 159.89.176.29
6 2026-08-28 02:13 639234796382955255
51 ms 159.89.176.29
5 2026-08-28 01:56 639234786015782563
2030 ms 159.89.176.29
4 2026-08-28 01:02 639234753811917646
46 ms 159.89.176.29
3 2026-08-28 00:45 639234743739767811
47 ms 159.89.176.29
2 2026-08-28 00:28 639234733372362811
187 ms 159.89.176.29
1 2026-08-28 00:11 639234723048550337
158 ms 159.89.176.29