DNS response history for ns2.megabet303.link

ns2.megabet303.link 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 36 DNS check records, 36 successful responses, 0 failed responses, and 306 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 ns2.megabet303.link.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

306 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 11:18

All timestamps shown in UTC

Latest Resolved IP on Selected Date

66.29.152.112

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 ns2.megabet303.link

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
36 2026-08-27 11:18 639234253963286387
324 ms 66.29.152.112
35 2026-08-27 11:01 639234243654907465
309 ms 66.29.152.112
34 2026-08-27 10:43 639234233269654413
302 ms 66.29.152.112
33 2026-08-27 10:26 639234222943951923
317 ms 66.29.152.112
32 2026-08-27 10:09 639234212558002823
325 ms 66.29.152.112
31 2026-08-27 09:52 639234202117531850
330 ms 66.29.152.112
30 2026-08-27 09:34 639234191649612722
317 ms 66.29.152.112
29 2026-08-27 09:17 639234181105879568
316 ms 66.29.152.112
28 2026-08-27 08:59 639234170713214496
319 ms 66.29.152.112
27 2026-08-27 08:42 639234160341037652
303 ms 66.29.152.112
26 2026-08-27 08:24 639234149799404224
310 ms 66.29.152.112
25 2026-08-27 08:07 639234139553286469
319 ms 66.29.152.112
24 2026-08-27 07:13 639234107183588293
153 ms 66.29.152.112
23 2026-08-27 06:56 639234096905435724
326 ms 66.29.152.112
22 2026-08-27 06:39 639234086579410775
319 ms 66.29.152.112
21 2026-08-27 06:22 639234076291157956
309 ms 66.29.152.112
20 2026-08-27 06:05 639234065981939454
316 ms 66.29.152.112
19 2026-08-27 05:47 639234055548642997
325 ms 66.29.152.112
18 2026-08-27 05:30 639234045267979603
162 ms 66.29.152.112
17 2026-08-27 05:13 639234034999717463
310 ms 66.29.152.112
16 2026-08-27 04:56 639234024739225358
309 ms 66.29.152.112
15 2026-08-27 04:39 639234014311170162
309 ms 66.29.152.112
14 2026-08-27 04:21 639234003806017640
315 ms 66.29.152.112
13 2026-08-27 04:04 639233993356203030
318 ms 66.29.152.112
12 2026-08-27 03:10 639233961301716608
308 ms 66.29.152.112
11 2026-08-27 02:53 639233950834200647
311 ms 66.29.152.112
10 2026-08-27 02:35 639233940431849026
315 ms 66.29.152.112
9 2026-08-27 02:18 639233930110596398
325 ms 66.29.152.112
8 2026-08-27 02:01 639233919705434540
294 ms 66.29.152.112
7 2026-08-27 01:44 639233909452807845
335 ms 66.29.152.112
6 2026-08-27 01:26 639233899096420820
309 ms 66.29.152.112
5 2026-08-27 01:09 639233888707824939
319 ms 66.29.152.112
4 2026-08-27 00:52 639233878461203802
303 ms 66.29.152.112
3 2026-08-27 00:35 639233868060868209
301 ms 66.29.152.112
2 2026-08-27 00:17 639233857450922991
312 ms 66.29.152.112
1 2026-08-27 00:00 639233846871926285
304 ms 66.29.152.112