DNS response history for dns2.infobrand.id

dns2.infobrand.id 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 37 DNS check records, 37 successful responses, 0 failed responses, and 30 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 dns2.infobrand.id.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

30 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:21

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.93.58.185

Most recently resolved hosting IP on selected date

Successful Responses

37

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 dns2.infobrand.id

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
37 2026-08-26 12:21 639233434974187439
32 ms 103.93.58.185
36 2026-08-26 12:04 639233424567558554
21 ms 103.93.58.185
35 2026-08-26 11:46 639233414056832719
43 ms 103.93.58.185
34 2026-08-26 11:29 639233403515141099
14 ms 103.93.58.185
33 2026-08-26 10:34 639233370841350248
14 ms 103.93.58.185
32 2026-08-26 10:17 639233360361507238
41 ms 103.93.58.185
31 2026-08-26 10:00 639233350067824371
29 ms 103.93.58.185
30 2026-08-26 09:42 639233339545274518
46 ms 103.93.58.185
29 2026-08-26 09:25 639233329214918079
35 ms 103.93.58.185
28 2026-08-26 09:08 639233318749762337
50 ms 103.93.58.185
27 2026-08-26 08:50 639233308387917838
9 ms 103.93.58.185
26 2026-08-26 08:33 639233297961740122
43 ms 103.93.58.185
25 2026-08-26 08:16 639233287487159094
14 ms 103.93.58.185
24 2026-08-26 07:58 639233276995531707
56 ms 103.93.58.185
23 2026-08-26 07:41 639233266521568229
20 ms 103.93.58.185
22 2026-08-26 07:23 639233256081047431
18 ms 103.93.58.185
21 2026-08-26 06:29 639233223620132921
20 ms 103.93.58.185
20 2026-08-26 06:12 639233213287814244
16 ms 103.93.58.185
19 2026-08-26 05:55 639233202925983161
9 ms 103.93.58.185
18 2026-08-26 05:37 639233192644780696
5 ms 103.93.58.185
17 2026-08-26 05:20 639233182401183833
28 ms 103.93.58.185
16 2026-08-26 05:03 639233172074181051
38 ms 103.93.58.185
15 2026-08-26 04:46 639233161808421455
9 ms 103.93.58.185
14 2026-08-26 04:29 639233151357344052
12 ms 103.93.58.185
13 2026-08-26 04:11 639233141034116946
8 ms 103.93.58.185
12 2026-08-26 03:54 639233130828334142
25 ms 103.93.58.185
11 2026-08-26 03:37 639233120373450007
30 ms 103.93.58.185
10 2026-08-26 03:20 639233110066216193
49 ms 103.93.58.185
9 2026-08-26 02:26 639233078065410564
36 ms 103.93.58.185
8 2026-08-26 02:09 639233067787457832
23 ms 103.93.58.185
7 2026-08-26 01:52 639233057501801162
109 ms 103.93.58.185
6 2026-08-26 01:35 639233047089431703
42 ms 103.93.58.185
5 2026-08-26 01:18 639233036754790688
28 ms 103.93.58.185
4 2026-08-26 01:00 639233026412602472
15 ms 103.93.58.185
3 2026-08-26 00:43 639233016064066127
66 ms 103.93.58.185
2 2026-08-26 00:26 639233005922655772
31 ms 103.93.58.185
1 2026-08-26 00:09 639232995672256907
9 ms 103.93.58.185