DNS response history for ns2.maxeffect.bg

ns2.maxeffect.bg 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 38 DNS check records, 38 successful responses, 0 failed responses, and 103 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.maxeffect.bg.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

103 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 12:39

All timestamps shown in UTC

Latest Resolved IP on Selected Date

91.196.126.61

Most recently resolved hosting IP on selected date

Successful Responses

38

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.maxeffect.bg

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
38 2026-08-27 12:39 639234307007468133
140 ms 91.196.126.61
37 2026-08-27 12:21 639234296664302575
51 ms 91.196.126.61
36 2026-08-27 12:04 639234286253196126
184 ms 91.196.126.61
35 2026-08-27 11:10 639234253963286387
32 ms 91.196.126.61
34 2026-08-27 10:53 639234243654907465
201 ms 91.196.126.61
33 2026-08-27 10:36 639234233269654413
127 ms 91.196.126.61
32 2026-08-27 10:19 639234222943951923
35 ms 91.196.126.61
31 2026-08-27 10:01 639234212558002823
106 ms 91.196.126.61
30 2026-08-27 09:44 639234202117531850
48 ms 91.196.126.61
29 2026-08-27 09:27 639234191649612722
57 ms 91.196.126.61
28 2026-08-27 09:09 639234181105879568
155 ms 91.196.126.61
27 2026-08-27 08:52 639234170713214496
156 ms 91.196.126.61
26 2026-08-27 08:34 639234160341037652
47 ms 91.196.126.61
25 2026-08-27 08:17 639234149799404224
30 ms 91.196.126.61
24 2026-08-27 08:00 639234139553286469
78 ms 91.196.126.61
23 2026-08-27 07:06 639234107183588293
159 ms 91.196.126.61
22 2026-08-27 06:49 639234096905435724
14 ms 91.196.126.61
21 2026-08-27 06:32 639234086579410775
65 ms 91.196.126.61
20 2026-08-27 06:14 639234076291157956
59 ms 91.196.126.61
19 2026-08-27 05:57 639234065981939454
183 ms 91.196.126.61
18 2026-08-27 05:40 639234055548642997
82 ms 91.196.126.61
17 2026-08-27 05:23 639234045267979603
318 ms 91.196.126.61
16 2026-08-27 05:06 639234034999717463
29 ms 91.196.126.61
15 2026-08-27 04:48 639234024739225358
23 ms 91.196.126.61
14 2026-08-27 04:31 639234014311170162
159 ms 91.196.126.61
13 2026-08-27 04:14 639234003806017640
55 ms 91.196.126.61
12 2026-08-27 03:56 639233993356203030
53 ms 91.196.126.61
11 2026-08-27 03:03 639233961301716608
26 ms 91.196.126.61
10 2026-08-27 02:46 639233950834200647
23 ms 91.196.126.61
9 2026-08-27 02:28 639233940431849026
48 ms 91.196.126.61
8 2026-08-27 02:11 639233930110596398
155 ms 91.196.126.61
7 2026-08-27 01:54 639233919705434540
326 ms 91.196.126.61
6 2026-08-27 01:36 639233909452807845
51 ms 91.196.126.61
5 2026-08-27 01:19 639233899096420820
239 ms 91.196.126.61
4 2026-08-27 01:02 639233888707824939
7 ms 91.196.126.61
3 2026-08-27 00:45 639233878461203802
209 ms 91.196.126.61
2 2026-08-27 00:27 639233868060868209
59 ms 91.196.126.61
1 2026-08-27 00:10 639233857450922991
129 ms 91.196.126.61