DNS response history for ns3.dibc.in

ns3.dibc.in 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-26. For this date, NameServerHistory found 34 DNS check records, 34 successful responses, 0 failed responses, and 210 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 ns3.dibc.in.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

210 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:34

All timestamps shown in UTC

Latest Resolved IP on Selected Date

216.10.250.105

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 ns3.dibc.in

Showing DNS history for 2026-08-26 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-26 11:34 639233403515141099
274 ms 216.10.250.105
33 2026-08-26 10:39 639233370841350248
276 ms 216.10.250.105
32 2026-08-26 10:22 639233360361507238
148 ms 216.10.250.105
31 2026-08-26 10:05 639233350067824371
132 ms 216.10.250.105
30 2026-08-26 09:48 639233339545274518
161 ms 216.10.250.105
29 2026-08-26 09:30 639233329214918079
285 ms 216.10.250.105
28 2026-08-26 09:13 639233318749762337
402 ms 216.10.250.105
27 2026-08-26 08:56 639233308387917838
297 ms 216.10.250.105
26 2026-08-26 08:38 639233297961740122
136 ms 216.10.250.105
25 2026-08-26 08:21 639233287487159094
387 ms 216.10.250.105
24 2026-08-26 08:03 639233276995531707
294 ms 216.10.250.105
23 2026-08-26 07:46 639233266521568229
161 ms 216.10.250.105
22 2026-08-26 07:28 639233256081047431
27 ms 216.10.250.105
21 2026-08-26 06:34 639233223620132921
215 ms 216.10.250.105
20 2026-08-26 06:17 639233213287814244
273 ms 216.10.250.105
19 2026-08-26 06:00 639233202925983161
282 ms 216.10.250.105
18 2026-08-26 05:42 639233192644780696
262 ms 216.10.250.105
17 2026-08-26 05:25 639233182401183833
147 ms 216.10.250.105
16 2026-08-26 05:08 639233172074181051
138 ms 216.10.250.105
15 2026-08-26 04:51 639233161808421455
263 ms 216.10.250.105
14 2026-08-26 04:34 639233151357344052
146 ms 216.10.250.105
13 2026-08-26 04:16 639233141034116946
369 ms 216.10.250.105
12 2026-08-26 03:59 639233130828334142
10 ms 216.10.250.105
11 2026-08-26 03:42 639233120373450007
281 ms 216.10.250.105
10 2026-08-26 03:25 639233110066216193
286 ms 216.10.250.105
9 2026-08-26 02:32 639233078065410564
135 ms 216.10.250.105
8 2026-08-26 02:14 639233067787457832
35 ms 216.10.250.105
7 2026-08-26 01:57 639233057501801162
313 ms 216.10.250.105
6 2026-08-26 01:40 639233047089431703
8 ms 216.10.250.105
5 2026-08-26 01:23 639233036754790688
268 ms 216.10.250.105
4 2026-08-26 01:06 639233026412602472
293 ms 216.10.250.105
3 2026-08-26 00:48 639233016064066127
153 ms 216.10.250.105
2 2026-08-26 00:31 639233005922655772
143 ms 216.10.250.105
1 2026-08-26 00:14 639232995672256907
156 ms 216.10.250.105