DNS response history for ns2.dbsentry.com

ns2.dbsentry.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 37 DNS check records, 37 successful responses, 0 failed responses, and 598 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.dbsentry.com.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

598 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:55

All timestamps shown in UTC

Latest Resolved IP on Selected Date

54.152.19.119

Most recently resolved hosting IP on selected date

Successful Responses

37

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.dbsentry.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
37 2026-08-25 12:55 639232587225721862
351 ms 54.152.19.119
36 2026-08-25 12:38 639232576780683689
362 ms 54.152.19.119
35 2026-08-25 12:20 639232566381512620
402 ms 54.152.19.119
34 2026-08-25 12:03 639232556111768563
92 ms 54.152.19.119
33 2026-08-25 11:46 639232545839529039
357 ms 54.152.19.119
32 2026-08-25 11:29 639232535349285207
357 ms 54.152.19.119
31 2026-08-25 11:11 639232524938080723
9 ms 54.152.19.119
30 2026-08-25 10:17 639232492740373468
89 ms 54.152.19.119
29 2026-08-25 10:00 639232482235303141
350 ms 54.152.19.119
28 2026-08-25 09:43 639232471861770303
484 ms 54.152.19.119
27 2026-08-25 09:25 639232461630217327
357 ms 54.152.19.119
26 2026-08-25 09:08 639232451282965990
2378 ms 54.152.19.119
25 2026-08-25 08:51 639232440814614938
356 ms 54.152.19.119
24 2026-08-25 08:33 639232430410720425
98 ms 54.152.19.119
23 2026-08-25 08:16 639232420003096185
358 ms 54.152.19.119
22 2026-08-25 07:59 639232409467287444
395 ms 54.152.19.119
21 2026-08-25 07:41 639232399077195997
351 ms 54.152.19.119
20 2026-08-25 07:24 639232388731528337
2402 ms 54.152.19.119
19 2026-08-25 07:07 639232378288598612
366 ms 54.152.19.119
18 2026-08-25 06:13 639232346196373643
111 ms 54.152.19.119
17 2026-08-25 05:56 639232336112370741
90 ms 54.152.19.119
16 2026-08-25 05:40 639232326146508970
349 ms 54.152.19.119
15 2026-08-25 05:23 639232316189381720
2 ms 54.152.19.119
14 2026-08-25 05:06 639232306217998913
354 ms 54.152.19.119
13 2026-08-25 04:50 639232296255744174
91 ms 54.152.19.119
12 2026-08-25 04:33 639232286095760789
2489 ms 54.152.19.119
11 2026-08-25 04:16 639232276086186273
361 ms 54.152.19.119
10 2026-08-25 03:59 639232265900986425
352 ms 54.152.19.119
9 2026-08-25 03:42 639232255723518075
7 ms 54.152.19.119
8 2026-08-25 03:25 639232245484452890
4361 ms 54.152.19.119
7 2026-08-25 03:08 639232235157175331
352 ms 54.152.19.119
6 2026-08-25 02:15 639232203197189095
89 ms 54.152.19.119
5 2026-08-25 01:58 639232192844564298
356 ms 54.152.19.119
4 2026-08-25 01:40 639232182496008942
89 ms 54.152.19.119
3 2026-08-25 01:23 639232172197053132
352 ms 54.152.19.119
2 2026-08-25 00:30 639232140250307418
2038 ms 54.152.19.119
1 2026-08-25 00:13 639232129927860324
351 ms 54.152.19.119