DNS response history for ns2.bleedingtree.com

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

35

Historical checks stored for this nameserver on selected date

Average Latency

184 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 11:10

All timestamps shown in UTC

Latest Resolved IP on Selected Date

158.106.134.136

Most recently resolved hosting IP on selected date

Successful Responses

35

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

Showing DNS history for 2026-08-27 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
35 2026-08-27 11:10 639234253963286387
120 ms 158.106.134.136
34 2026-08-27 10:53 639234243654907465
222 ms 158.106.134.136
33 2026-08-27 10:36 639234233269654413
223 ms 158.106.134.136
32 2026-08-27 10:19 639234222943951923
223 ms 158.106.134.136
31 2026-08-27 10:01 639234212558002823
221 ms 158.106.134.136
30 2026-08-27 09:44 639234202117531850
217 ms 158.106.134.136
29 2026-08-27 09:27 639234191649612722
227 ms 158.106.134.136
28 2026-08-27 09:09 639234181105879568
111 ms 158.106.134.136
27 2026-08-27 08:52 639234170713214496
244 ms 158.106.134.136
26 2026-08-27 08:34 639234160341037652
226 ms 158.106.134.136
25 2026-08-27 08:17 639234149799404224
117 ms 158.106.134.136
24 2026-08-27 08:00 639234139553286469
224 ms 158.106.134.136
23 2026-08-27 07:06 639234107183588293
118 ms 158.106.134.136
22 2026-08-27 06:49 639234096905435724
18 ms 158.106.134.136
21 2026-08-27 06:32 639234086579410775
250 ms 158.106.134.136
20 2026-08-27 06:14 639234076291157956
219 ms 158.106.134.136
19 2026-08-27 05:57 639234065981939454
116 ms 158.106.134.136
18 2026-08-27 05:40 639234055548642997
123 ms 158.106.134.136
17 2026-08-27 05:23 639234045267979603
230 ms 158.106.134.136
16 2026-08-27 05:06 639234034999717463
228 ms 158.106.134.136
15 2026-08-27 04:48 639234024739225358
111 ms 158.106.134.136
14 2026-08-27 04:31 639234014311170162
220 ms 158.106.134.136
13 2026-08-27 04:14 639234003806017640
124 ms 158.106.134.136
12 2026-08-27 03:56 639233993356203030
242 ms 158.106.134.136
11 2026-08-27 03:03 639233961301716608
163 ms 158.106.134.136
10 2026-08-27 02:46 639233950834200647
4 ms 158.106.134.136
9 2026-08-27 02:28 639233940431849026
220 ms 158.106.134.136
8 2026-08-27 02:11 639233930110596398
224 ms 158.106.134.136
7 2026-08-27 01:54 639233919705434540
220 ms 158.106.134.136
6 2026-08-27 01:36 639233909452807845
239 ms 158.106.134.136
5 2026-08-27 01:19 639233899096420820
205 ms 158.106.134.136
4 2026-08-27 01:02 639233888707824939
132 ms 158.106.134.136
3 2026-08-27 00:45 639233878461203802
220 ms 158.106.134.136
2 2026-08-27 00:27 639233868060868209
239 ms 158.106.134.136
1 2026-08-27 00:10 639233857450922991
217 ms 158.106.134.136