DNS response history for ns3.bodintl.com

ns3.bodintl.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-25. For this date, NameServerHistory found 36 DNS check records, 36 successful responses, 0 failed responses, and 535 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.bodintl.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

535 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 06:16

All timestamps shown in UTC

Latest Resolved IP on Selected Date

121.12.152.101

Most recently resolved hosting IP on selected date

Successful Responses

36

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

Showing DNS history for 2026-08-25 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
36 2026-08-25 06:16 639232346196373643
3 ms 121.12.152.101
35 2026-08-25 06:16 639232346196373643
3 ms 218.16.64.133
34 2026-08-25 05:59 639232336112370741
4 ms 121.12.152.101
33 2026-08-25 05:59 639232336112370741
4 ms 218.16.64.133
32 2026-08-25 05:43 639232326146508970
580 ms 121.12.152.101
31 2026-08-25 05:43 639232326146508970
580 ms 218.16.64.133
30 2026-08-25 05:26 639232316189381720
504 ms 218.16.64.133
29 2026-08-25 05:26 639232316189381720
504 ms 121.12.152.101
28 2026-08-25 05:10 639232306217998913
390 ms 121.12.152.101
27 2026-08-25 05:10 639232306217998913
390 ms 218.16.64.133
26 2026-08-25 04:53 639232296255744174
390 ms 121.12.152.101
25 2026-08-25 04:53 639232296255744174
390 ms 218.16.64.133
24 2026-08-25 04:36 639232286095760789
536 ms 218.16.64.133
23 2026-08-25 04:36 639232286095760789
536 ms 121.12.152.101
22 2026-08-25 04:19 639232276086186273
502 ms 121.12.152.101
21 2026-08-25 04:19 639232276086186273
502 ms 218.16.64.133
20 2026-08-25 04:03 639232265900986425
515 ms 121.12.152.101
19 2026-08-25 04:03 639232265900986425
515 ms 218.16.64.133
18 2026-08-25 03:46 639232255723518075
533 ms 218.16.64.133
17 2026-08-25 03:46 639232255723518075
533 ms 121.12.152.101
16 2026-08-25 03:29 639232245484452890
222 ms 121.12.152.101
15 2026-08-25 03:29 639232245484452890
222 ms 218.16.64.133
14 2026-08-25 03:11 639232235157175331
750 ms 121.12.152.101
13 2026-08-25 03:11 639232235157175331
750 ms 218.16.64.133
12 2026-08-25 02:18 639232203197189095
430 ms 218.16.64.133
11 2026-08-25 02:18 639232203197189095
430 ms 121.12.152.101
10 2026-08-25 02:01 639232192844564298
435 ms 121.12.152.101
9 2026-08-25 02:01 639232192844564298
435 ms 218.16.64.133
8 2026-08-25 01:44 639232182496008942
2224 ms 218.16.64.133
7 2026-08-25 01:44 639232182496008942
2224 ms 121.12.152.101
6 2026-08-25 01:26 639232172197053132
759 ms 121.12.152.101
5 2026-08-25 01:26 639232172197053132
759 ms 218.16.64.133
4 2026-08-25 00:33 639232140250307418
435 ms 121.12.152.101
3 2026-08-25 00:33 639232140250307418
435 ms 218.16.64.133
2 2026-08-25 00:16 639232129927860324
425 ms 121.12.152.101
1 2026-08-25 00:16 639232129927860324
425 ms 218.16.64.133