DNS response history for fwn2.bodrex.com

fwn2.bodrex.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-27. For this date, NameServerHistory found 40 DNS check records, 40 successful responses, 0 failed responses, and 676 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 fwn2.bodrex.com.
Records on Selected Date

40

Historical checks stored for this nameserver on selected date

Average Latency

676 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 13:21

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.86.154.2

Most recently resolved hosting IP on selected date

Successful Responses

40

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 fwn2.bodrex.com

Showing DNS history for 2026-08-27 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
40 2026-08-27 13:21 639234327818741376
687 ms 103.86.154.2
39 2026-08-27 13:03 639234317475724313
675 ms 103.86.154.2
38 2026-08-27 12:46 639234307007468133
690 ms 103.86.154.2
37 2026-08-27 12:29 639234296664302575
683 ms 103.86.154.2
36 2026-08-27 12:11 639234286253196126
674 ms 103.86.154.2
35 2026-08-27 11:18 639234253963286387
671 ms 103.86.154.2
34 2026-08-27 11:00 639234243654907465
664 ms 103.86.154.2
33 2026-08-27 10:43 639234233269654413
857 ms 103.86.154.2
32 2026-08-27 10:26 639234222943951923
641 ms 103.86.154.2
31 2026-08-27 10:09 639234212558002823
696 ms 103.86.154.2
30 2026-08-27 09:51 639234202117531850
655 ms 103.86.154.2
29 2026-08-27 09:34 639234191649612722
690 ms 103.86.154.2
28 2026-08-27 09:16 639234181105879568
743 ms 103.86.154.2
27 2026-08-27 08:59 639234170713214496
683 ms 103.86.154.2
26 2026-08-27 08:42 639234160341037652
695 ms 103.86.154.2
25 2026-08-27 08:24 639234149799404224
517 ms 103.86.154.2
24 2026-08-27 08:07 639234139553286469
680 ms 103.86.154.2
23 2026-08-27 07:13 639234107183588293
686 ms 103.86.154.2
22 2026-08-27 06:56 639234096905435724
695 ms 103.86.154.2
21 2026-08-27 06:39 639234086579410775
673 ms 103.86.154.2
20 2026-08-27 06:21 639234076291157956
656 ms 103.86.154.2
19 2026-08-27 06:04 639234065981939454
684 ms 103.86.154.2
18 2026-08-27 05:47 639234055548642997
542 ms 103.86.154.2
17 2026-08-27 05:30 639234045267979603
698 ms 103.86.154.2
16 2026-08-27 05:13 639234034999717463
704 ms 103.86.154.2
15 2026-08-27 04:55 639234024739225358
704 ms 103.86.154.2
14 2026-08-27 04:38 639234014311170162
768 ms 103.86.154.2
13 2026-08-27 04:21 639234003806017640
663 ms 103.86.154.2
12 2026-08-27 04:03 639233993356203030
381 ms 103.86.154.2
11 2026-08-27 03:10 639233961301716608
765 ms 103.86.154.2
10 2026-08-27 02:53 639233950834200647
572 ms 103.86.154.2
9 2026-08-27 02:35 639233940431849026
750 ms 103.86.154.2
8 2026-08-27 02:18 639233930110596398
704 ms 103.86.154.2
7 2026-08-27 02:01 639233919705434540
733 ms 103.86.154.2
6 2026-08-27 01:43 639233909452807845
672 ms 103.86.154.2
5 2026-08-27 01:26 639233899096420820
672 ms 103.86.154.2
4 2026-08-27 01:09 639233888707824939
671 ms 103.86.154.2
3 2026-08-27 00:52 639233878461203802
646 ms 103.86.154.2
2 2026-08-27 00:34 639233868060868209
680 ms 103.86.154.2
1 2026-08-27 00:17 639233857450922991
731 ms 103.86.154.2