DNS response history for ns3.explainbettingodds.com

ns3.explainbettingodds.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 35 DNS check records, 35 successful responses, 0 failed responses, and 321 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.explainbettingodds.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

321 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 11:16

All timestamps shown in UTC

Latest Resolved IP on Selected Date

104.237.135.95

Most recently resolved hosting IP on selected date

Successful Responses

35

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.explainbettingodds.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
35 2026-08-27 11:16 639234253963286387
5 ms 104.237.135.95
34 2026-08-27 10:59 639234243654907465
253 ms 104.237.135.95
33 2026-08-27 10:42 639234233269654413
3 ms 104.237.135.95
32 2026-08-27 10:24 639234222943951923
247 ms 104.237.135.95
31 2026-08-27 10:07 639234212558002823
251 ms 104.237.135.95
30 2026-08-27 09:50 639234202117531850
259 ms 104.237.135.95
29 2026-08-27 09:32 639234191649612722
698 ms 104.237.135.95
28 2026-08-27 09:15 639234181105879568
253 ms 104.237.135.95
27 2026-08-27 08:57 639234170713214496
132 ms 104.237.135.95
26 2026-08-27 08:40 639234160341037652
253 ms 104.237.135.95
25 2026-08-27 08:23 639234149799404224
131 ms 104.237.135.95
24 2026-08-27 08:05 639234139553286469
125 ms 104.237.135.95
23 2026-08-27 07:11 639234107183588293
255 ms 104.237.135.95
22 2026-08-27 06:54 639234096905435724
253 ms 104.237.135.95
21 2026-08-27 06:37 639234086579410775
244 ms 104.237.135.95
20 2026-08-27 06:20 639234076291157956
257 ms 104.237.135.95
19 2026-08-27 06:03 639234065981939454
251 ms 104.237.135.95
18 2026-08-27 05:46 639234055548642997
235 ms 104.237.135.95
17 2026-08-27 05:28 639234045267979603
131 ms 104.237.135.95
16 2026-08-27 05:11 639234034999717463
1785 ms 104.237.135.95
15 2026-08-27 04:54 639234024739225358
241 ms 104.237.135.95
14 2026-08-27 04:37 639234014311170162
706 ms 104.237.135.95
13 2026-08-27 04:19 639234003806017640
131 ms 104.237.135.95
12 2026-08-27 04:02 639233993356203030
246 ms 104.237.135.95
11 2026-08-27 03:08 639233961301716608
242 ms 104.237.135.95
10 2026-08-27 02:51 639233950834200647
252 ms 104.237.135.95
9 2026-08-27 02:34 639233940431849026
1401 ms 104.237.135.95
8 2026-08-27 02:16 639233930110596398
123 ms 104.237.135.95
7 2026-08-27 01:59 639233919705434540
248 ms 104.237.135.95
6 2026-08-27 01:42 639233909452807845
705 ms 104.237.135.95
5 2026-08-27 01:25 639233899096420820
253 ms 104.237.135.95
4 2026-08-27 01:07 639233888707824939
150 ms 104.237.135.95
3 2026-08-27 00:50 639233878461203802
119 ms 104.237.135.95
2 2026-08-27 00:33 639233868060868209
126 ms 104.237.135.95
1 2026-08-27 00:15 639233857450922991
257 ms 104.237.135.95