DNS response history for ns2.dbdb-holdings.com

ns2.dbdb-holdings.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-25. For this date, NameServerHistory found 36 DNS check records, 36 successful responses, 0 failed responses, and 445 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.dbdb-holdings.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

445 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:41

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.16.128.80

Most recently resolved hosting IP on selected date

Successful Responses

36

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.dbdb-holdings.com

Showing DNS history for 2026-08-25 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
36 2026-08-25 12:41 639232576780683689
631 ms 103.16.128.80
35 2026-08-25 12:24 639232566381512620
310 ms 103.16.128.80
34 2026-08-25 12:07 639232556111768563
630 ms 103.16.128.80
33 2026-08-25 11:50 639232545839529039
630 ms 103.16.128.80
32 2026-08-25 11:32 639232535349285207
4 ms 103.16.128.80
31 2026-08-25 11:15 639232524938080723
639 ms 103.16.128.80
30 2026-08-25 10:21 639232492740373468
6 ms 103.16.128.80
29 2026-08-25 10:04 639232482235303141
638 ms 103.16.128.80
28 2026-08-25 09:46 639232471861770303
640 ms 103.16.128.80
27 2026-08-25 09:29 639232461630217327
626 ms 103.16.128.80
26 2026-08-25 09:12 639232451282965990
622 ms 103.16.128.80
25 2026-08-25 08:55 639232440814614938
634 ms 103.16.128.80
24 2026-08-25 08:37 639232430410720425
630 ms 103.16.128.80
23 2026-08-25 08:20 639232420003096185
633 ms 103.16.128.80
22 2026-08-25 08:03 639232409467287444
408 ms 103.16.128.80
21 2026-08-25 07:45 639232399077195997
639 ms 103.16.128.80
20 2026-08-25 07:28 639232388731528337
627 ms 103.16.128.80
19 2026-08-25 07:11 639232378288598612
707 ms 103.16.128.80
18 2026-08-25 06:17 639232346196373643
7 ms 103.16.128.80
17 2026-08-25 06:00 639232336112370741
4 ms 103.16.128.80
16 2026-08-25 05:43 639232326146508970
634 ms 103.16.128.80
15 2026-08-25 05:27 639232316189381720
625 ms 103.16.128.80
14 2026-08-25 05:10 639232306217998913
3 ms 103.16.128.80
13 2026-08-25 04:53 639232296255744174
17 ms 103.16.128.80
12 2026-08-25 04:37 639232286095760789
2 ms 103.16.128.80
11 2026-08-25 04:20 639232276086186273
628 ms 103.16.128.80
10 2026-08-25 04:03 639232265900986425
635 ms 103.16.128.80
9 2026-08-25 03:46 639232255723518075
637 ms 103.16.128.80
8 2026-08-25 03:29 639232245484452890
622 ms 103.16.128.80
7 2026-08-25 03:12 639232235157175331
635 ms 103.16.128.80
6 2026-08-25 02:19 639232203197189095
2 ms 103.16.128.80
5 2026-08-25 02:02 639232192844564298
643 ms 103.16.128.80
4 2026-08-25 01:44 639232182496008942
629 ms 103.16.128.80
3 2026-08-25 01:27 639232172197053132
637 ms 103.16.128.80
2 2026-08-25 00:33 639232140250307418
4 ms 103.16.128.80
1 2026-08-25 00:17 639232129927860324
2 ms 103.16.128.80