DNS response history for ns2.tbcfi.com

ns2.tbcfi.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-24. For this date, NameServerHistory found 38 DNS check records, 38 successful responses, 0 failed responses, and 290 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.tbcfi.com.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

290 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 15:52

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.186.185.128

Most recently resolved hosting IP on selected date

Successful Responses

38

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

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
38 2026-08-24 15:52 639231828211839931
312 ms 103.186.185.128
37 2026-08-24 15:35 639231818080917481
292 ms 103.186.185.128
36 2026-08-24 15:18 639231807961539652
265 ms 103.186.185.128
35 2026-08-24 15:01 639231797631669865
5 ms 103.186.185.128
34 2026-08-24 14:08 639231765923559455
4 ms 103.186.185.128
33 2026-08-24 13:51 639231755868832964
283 ms 103.186.185.128
32 2026-08-24 13:35 639231745628278877
261 ms 103.186.185.128
31 2026-08-24 13:17 639231735407682062
6 ms 103.186.185.128
30 2026-08-24 12:25 639231703815441688
288 ms 103.186.185.128
29 2026-08-24 12:08 639231693747052549
311 ms 103.186.185.128
28 2026-08-24 11:51 639231683712487276
536 ms 103.186.185.128
27 2026-08-24 11:34 639231673513573868
790 ms 103.186.185.128
26 2026-08-24 10:41 639231641791249939
4 ms 103.186.185.128
25 2026-08-24 10:25 639231631866211033
4 ms 103.186.185.128
24 2026-08-24 10:08 639231621644955316
281 ms 103.186.185.128
23 2026-08-24 09:51 639231611478799259
618 ms 103.186.185.128
22 2026-08-24 08:58 639231579923718211
2545 ms 103.186.185.128
21 2026-08-24 08:42 639231569810702936
288 ms 103.186.185.128
20 2026-08-24 08:24 639231559762411619
300 ms 103.186.185.128
19 2026-08-24 08:08 639231549663595407
267 ms 103.186.185.128
18 2026-08-24 07:15 639231518076817246
287 ms 103.186.185.128
17 2026-08-24 06:59 639231508078650885
311 ms 103.186.185.128
16 2026-08-24 06:42 639231498210697093
4 ms 103.186.185.128
15 2026-08-24 06:25 639231488109699360
282 ms 103.186.185.128
14 2026-08-24 05:33 639231456772510692
4 ms 103.186.185.128
13 2026-08-24 05:17 639231447084631185
634 ms 103.186.185.128
12 2026-08-24 05:00 639231437208519473
317 ms 103.186.185.128
11 2026-08-24 04:44 639231427209627490
4 ms 103.186.185.128
10 2026-08-24 03:51 639231395791246644
2 ms 103.186.185.128
9 2026-08-24 03:35 639231386075551458
3 ms 103.186.185.128
8 2026-08-24 03:19 639231376208713791
273 ms 103.186.185.128
7 2026-08-24 03:02 639231366170589276
3 ms 103.186.185.128
6 2026-08-24 02:10 639231334732159368
3 ms 103.186.185.128
5 2026-08-24 01:53 639231325035670078
293 ms 103.186.185.128
4 2026-08-24 01:37 639231315132253837
4 ms 103.186.185.128
3 2026-08-24 01:20 639231305014280808
624 ms 103.186.185.128
2 2026-08-24 00:28 639231273779380675
4 ms 103.186.185.128
1 2026-08-24 00:12 639231264180839154
303 ms 103.186.185.128