DNS response history for ns2.multibaks.com

ns2.multibaks.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-26. For this date, NameServerHistory found 26 DNS check records, 26 successful responses, 0 failed responses, and 333 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.multibaks.com.
Records on Selected Date

26

Historical checks stored for this nameserver on selected date

Average Latency

333 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 08:40

All timestamps shown in UTC

Latest Resolved IP on Selected Date

192.110.164.212

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

Showing DNS history for 2026-08-26 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-26 08:40 639233297961740122
314 ms 192.110.164.212
25 2026-08-26 08:23 639233287487159094
2281 ms 192.110.164.212
24 2026-08-26 08:05 639233276995531707
156 ms 192.110.164.212
23 2026-08-26 07:48 639233266521568229
311 ms 192.110.164.212
22 2026-08-26 07:30 639233256081047431
298 ms 192.110.164.212
21 2026-08-26 06:36 639233223620132921
292 ms 192.110.164.212
20 2026-08-26 06:19 639233213287814244
298 ms 192.110.164.212
19 2026-08-26 06:02 639233202925983161
295 ms 192.110.164.212
18 2026-08-26 05:44 639233192644780696
325 ms 192.110.164.212
17 2026-08-26 05:27 639233182401183833
297 ms 192.110.164.212
16 2026-08-26 05:10 639233172074181051
301 ms 192.110.164.212
15 2026-08-26 04:53 639233161808421455
299 ms 192.110.164.212
14 2026-08-26 04:36 639233151357344052
9 ms 192.110.164.212
13 2026-08-26 04:18 639233141034116946
176 ms 192.110.164.212
12 2026-08-26 04:01 639233130828334142
296 ms 192.110.164.212
11 2026-08-26 03:44 639233120373450007
296 ms 192.110.164.212
10 2026-08-26 03:27 639233110066216193
303 ms 192.110.164.212
9 2026-08-26 02:34 639233078065410564
3 ms 192.110.164.212
8 2026-08-26 02:16 639233067787457832
308 ms 192.110.164.212
7 2026-08-26 01:59 639233057501801162
305 ms 192.110.164.212
6 2026-08-26 01:42 639233047089431703
297 ms 192.110.164.212
5 2026-08-26 01:25 639233036754790688
3 ms 192.110.164.212
4 2026-08-26 01:08 639233026412602472
295 ms 192.110.164.212
3 2026-08-26 00:50 639233016064066127
296 ms 192.110.164.212
2 2026-08-26 00:33 639233005922655772
301 ms 192.110.164.212
1 2026-08-26 00:16 639232995672256907
295 ms 192.110.164.212