DNS response history for ns2.optimaweb.host

ns2.optimaweb.host 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 28 DNS check records, 28 successful responses, 0 failed responses, and 195 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.optimaweb.host.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

195 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-28 11:36

All timestamps shown in UTC

Latest Resolved IP on Selected Date

50.28.10.78

Most recently resolved hosting IP on selected date

Successful Responses

28

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.optimaweb.host

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
28 2026-08-28 11:36 639235132147470568
122 ms 50.28.10.78
27 2026-08-28 11:18 639235121907744088
253 ms 50.28.10.78
26 2026-08-28 11:01 639235111428014262
248 ms 50.28.10.78
25 2026-08-28 10:43 639235100921813626
248 ms 50.28.10.78
24 2026-08-28 09:50 639235068670703481
239 ms 50.28.10.78
23 2026-08-28 09:32 639235058337459445
129 ms 50.28.10.78
22 2026-08-28 09:15 639235047825109146
247 ms 50.28.10.78
21 2026-08-28 08:57 639235037383229033
177 ms 50.28.10.78
20 2026-08-28 08:04 639235005619242711
248 ms 50.28.10.78
19 2026-08-28 07:48 639234995310346584
120 ms 50.28.10.78
18 2026-08-28 07:30 639234984946548933
231 ms 50.28.10.78
17 2026-08-28 07:13 639234974608077290
274 ms 50.28.10.78
16 2026-08-28 06:19 639234942529845595
128 ms 50.28.10.78
15 2026-08-28 06:02 639234932259126627
215 ms 50.28.10.78
14 2026-08-28 05:45 639234921916735988
242 ms 50.28.10.78
13 2026-08-28 05:28 639234911470038027
238 ms 50.28.10.78
12 2026-08-28 04:35 639234879588411654
109 ms 50.28.10.78
11 2026-08-28 04:17 639234869341589104
231 ms 50.28.10.78
10 2026-08-28 04:00 639234859012216675
237 ms 50.28.10.78
9 2026-08-28 03:43 639234848695364934
244 ms 50.28.10.78
8 2026-08-28 02:50 639234816952458162
238 ms 50.28.10.78
7 2026-08-28 02:33 639234806773081598
133 ms 50.28.10.78
6 2026-08-28 02:16 639234796382955255
285 ms 50.28.10.78
5 2026-08-28 01:59 639234786015782563
132 ms 50.28.10.78
4 2026-08-28 01:05 639234753811917646
113 ms 50.28.10.78
3 2026-08-28 00:48 639234743739767811
8 ms 50.28.10.78
2 2026-08-28 00:31 639234733372362811
128 ms 50.28.10.78
1 2026-08-28 00:14 639234723048550337
235 ms 50.28.10.78