DNS response history for ns2.bazcode.co

ns2.bazcode.co 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-24. For this date, NameServerHistory found 34 DNS check records, 34 successful responses, 0 failed responses, and 145 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.bazcode.co.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

145 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 14:10

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.75.198.54

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 ns2.bazcode.co

Showing DNS history for 2026-08-24 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-24 14:10 639231765923559455
190 ms 103.75.198.54
33 2026-08-24 13:53 639231755868832964
181 ms 103.75.198.54
32 2026-08-24 13:36 639231745628278877
188 ms 103.75.198.54
31 2026-08-24 13:19 639231735407682062
179 ms 103.75.198.54
30 2026-08-24 12:26 639231703815441688
170 ms 103.75.198.54
29 2026-08-24 12:10 639231693747052549
192 ms 103.75.198.54
28 2026-08-24 11:53 639231683712487276
193 ms 103.75.198.54
27 2026-08-24 11:36 639231673513573868
6 ms 103.75.198.54
26 2026-08-24 10:43 639231641791249939
206 ms 103.75.198.54
25 2026-08-24 10:26 639231631866211033
4 ms 103.75.198.54
24 2026-08-24 10:09 639231621644955316
192 ms 103.75.198.54
23 2026-08-24 09:52 639231611478799259
165 ms 103.75.198.54
22 2026-08-24 09:00 639231579923718211
175 ms 103.75.198.54
21 2026-08-24 08:43 639231569810702936
189 ms 103.75.198.54
20 2026-08-24 08:26 639231559762411619
134 ms 103.75.198.54
19 2026-08-24 08:09 639231549663595407
121 ms 103.75.198.54
18 2026-08-24 07:16 639231518076817246
214 ms 103.75.198.54
17 2026-08-24 07:00 639231508078650885
204 ms 103.75.198.54
16 2026-08-24 06:43 639231498210697093
181 ms 103.75.198.54
15 2026-08-24 06:27 639231488109699360
172 ms 103.75.198.54
14 2026-08-24 05:34 639231456772510692
177 ms 103.75.198.54
13 2026-08-24 05:18 639231447084631185
143 ms 103.75.198.54
12 2026-08-24 05:02 639231437208519473
3 ms 103.75.198.54
11 2026-08-24 04:45 639231427209627490
163 ms 103.75.198.54
10 2026-08-24 03:52 639231395791246644
3 ms 103.75.198.54
9 2026-08-24 03:37 639231386075551458
8 ms 103.75.198.54
8 2026-08-24 03:20 639231376208713791
6 ms 103.75.198.54
7 2026-08-24 03:04 639231366170589276
226 ms 103.75.198.54
6 2026-08-24 02:11 639231334732159368
144 ms 103.75.198.54
5 2026-08-24 01:55 639231325035670078
191 ms 103.75.198.54
4 2026-08-24 01:38 639231315132253837
101 ms 103.75.198.54
3 2026-08-24 01:22 639231305014280808
194 ms 103.75.198.54
2 2026-08-24 00:29 639231273779380675
323 ms 103.75.198.54
1 2026-08-24 00:13 639231264180839154
2 ms 103.75.198.54