DNS response history for ns2.pelingbl.com

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

30

Historical checks stored for this nameserver on selected date

Average Latency

229 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-28 12:43

All timestamps shown in UTC

Latest Resolved IP on Selected Date

106.48.28.249

Most recently resolved hosting IP on selected date

Successful Responses

30

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

Showing DNS history for 2026-08-28 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
30 2026-08-28 12:43 639235174453894956
53 ms 106.48.28.249
29 2026-08-28 12:25 639235163898672622
128 ms 106.48.28.249
28 2026-08-28 11:32 639235132147470568
153 ms 106.48.28.249
27 2026-08-28 11:15 639235121907744088
86 ms 106.48.28.249
26 2026-08-28 10:58 639235111428014262
92 ms 106.48.28.249
25 2026-08-28 10:40 639235100921813626
2058 ms 106.48.28.249
24 2026-08-28 09:47 639235068670703481
117 ms 106.48.28.249
23 2026-08-28 09:29 639235058337459445
97 ms 106.48.28.249
22 2026-08-28 09:12 639235047825109146
101 ms 106.48.28.249
21 2026-08-28 08:54 639235037383229033
64 ms 106.48.28.249
20 2026-08-28 08:02 639235005619242711
56 ms 106.48.28.249
19 2026-08-28 07:45 639234995310346584
126 ms 106.48.28.249
18 2026-08-28 07:27 639234984946548933
94 ms 106.48.28.249
17 2026-08-28 07:10 639234974608077290
86 ms 106.48.28.249
16 2026-08-28 06:16 639234942529845595
100 ms 106.48.28.249
15 2026-08-28 05:59 639234932259126627
128 ms 106.48.28.249
14 2026-08-28 05:42 639234921916735988
109 ms 106.48.28.249
13 2026-08-28 05:25 639234911470038027
83 ms 106.48.28.249
12 2026-08-28 04:32 639234879588411654
154 ms 106.48.28.249
11 2026-08-28 04:15 639234869341589104
2056 ms 106.48.28.249
10 2026-08-28 03:57 639234859012216675
88 ms 106.48.28.249
9 2026-08-28 03:40 639234848695364934
38 ms 106.48.28.249
8 2026-08-28 02:47 639234816952458162
179 ms 106.48.28.249
7 2026-08-28 02:30 639234806773081598
123 ms 106.48.28.249
6 2026-08-28 02:13 639234796382955255
78 ms 106.48.28.249
5 2026-08-28 01:56 639234786015782563
56 ms 106.48.28.249
4 2026-08-28 01:02 639234753811917646
98 ms 106.48.28.249
3 2026-08-28 00:45 639234743739767811
75 ms 106.48.28.249
2 2026-08-28 00:28 639234733372362811
91 ms 106.48.28.249
1 2026-08-28 00:11 639234723048550337
115 ms 106.48.28.249