DNS response history for blue2.disbit.com

blue2.disbit.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 34 DNS check records, 34 successful responses, 0 failed responses, and 87 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 blue2.disbit.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

87 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:00

All timestamps shown in UTC

Latest Resolved IP on Selected Date

91.146.97.132

Most recently resolved hosting IP on selected date

Successful Responses

34

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 blue2.disbit.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
34 2026-08-25 12:00 639232556111768563
89 ms 91.146.97.132
33 2026-08-25 11:43 639232545839529039
101 ms 91.146.97.132
32 2026-08-25 11:26 639232535349285207
123 ms 91.146.97.132
31 2026-08-25 11:08 639232524938080723
101 ms 91.146.97.132
30 2026-08-25 10:14 639232492740373468
14 ms 91.146.97.132
29 2026-08-25 09:57 639232482235303141
82 ms 91.146.97.132
28 2026-08-25 09:40 639232471861770303
67 ms 91.146.97.132
27 2026-08-25 09:23 639232461630217327
46 ms 91.146.97.132
26 2026-08-25 09:06 639232451282965990
124 ms 91.146.97.132
25 2026-08-25 08:48 639232440814614938
104 ms 91.146.97.132
24 2026-08-25 08:31 639232430410720425
41 ms 91.146.97.132
23 2026-08-25 08:13 639232420003096185
117 ms 91.146.97.132
22 2026-08-25 07:56 639232409467287444
97 ms 91.146.97.132
21 2026-08-25 07:39 639232399077195997
98 ms 91.146.97.132
20 2026-08-25 07:21 639232388731528337
90 ms 91.146.97.132
19 2026-08-25 07:04 639232378288598612
192 ms 91.146.97.132
18 2026-08-25 06:10 639232346196373643
90 ms 91.146.97.132
17 2026-08-25 05:54 639232336112370741
102 ms 91.146.97.132
16 2026-08-25 05:37 639232326146508970
67 ms 91.146.97.132
15 2026-08-25 05:20 639232316189381720
207 ms 91.146.97.132
14 2026-08-25 05:04 639232306217998913
79 ms 91.146.97.132
13 2026-08-25 04:47 639232296255744174
85 ms 91.146.97.132
12 2026-08-25 04:30 639232286095760789
77 ms 91.146.97.132
11 2026-08-25 04:13 639232276086186273
103 ms 91.146.97.132
10 2026-08-25 03:57 639232265900986425
51 ms 91.146.97.132
9 2026-08-25 03:40 639232255723518075
52 ms 91.146.97.132
8 2026-08-25 03:23 639232245484452890
95 ms 91.146.97.132
7 2026-08-25 03:05 639232235157175331
58 ms 91.146.97.132
6 2026-08-25 02:12 639232203197189095
61 ms 91.146.97.132
5 2026-08-25 01:55 639232192844564298
42 ms 91.146.97.132
4 2026-08-25 01:38 639232182496008942
36 ms 91.146.97.132
3 2026-08-25 01:20 639232172197053132
64 ms 91.146.97.132
2 2026-08-25 00:27 639232140250307418
112 ms 91.146.97.132
1 2026-08-25 00:10 639232129927860324
84 ms 91.146.97.132