DNS response history for banshee.mxlogin.com

banshee.mxlogin.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, 33 successful responses, 2 failed responses, and 66 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 banshee.mxlogin.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

66 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 11:05

All timestamps shown in UTC

Latest Resolved IP on Selected Date

94.130.163.225

Most recently resolved hosting IP on selected date

Successful Responses

33

Checks that returned a measurable response

Failed Responses

2

Checks with no response or no returned latency

Failure Rate

6%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for banshee.mxlogin.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:05 639234253963286387
19 ms 94.130.163.225
34 2026-08-27 10:48 639234243654907465
110 ms 94.130.163.225
33 2026-08-27 10:31 639234233269654413
227 ms 94.130.163.225
32 2026-08-27 10:13 639234222943951923
24 ms 94.130.163.225
31 2026-08-27 09:56 639234212558002823
44 ms 94.130.163.225
30 2026-08-27 09:39 639234202117531850
-
29 2026-08-27 09:21 639234191649612722
78 ms 94.130.163.225
28 2026-08-27 09:04 639234181105879568
41 ms 94.130.163.225
27 2026-08-27 08:46 639234170713214496
20 ms 94.130.163.225
26 2026-08-27 08:29 639234160341037652
49 ms 94.130.163.225
25 2026-08-27 08:12 639234149799404224
105 ms 94.130.163.225
24 2026-08-27 07:54 639234139553286469
36 ms 94.130.163.225
23 2026-08-27 07:00 639234107183588293
56 ms 94.130.163.225
22 2026-08-27 06:43 639234096905435724
18 ms 94.130.163.225
21 2026-08-27 06:26 639234086579410775
22 ms 94.130.163.225
20 2026-08-27 06:09 639234076291157956
88 ms 94.130.163.225
19 2026-08-27 05:52 639234065981939454
27 ms 94.130.163.225
18 2026-08-27 05:34 639234055548642997
110 ms 94.130.163.225
17 2026-08-27 05:17 639234045267979603
153 ms 94.130.163.225
16 2026-08-27 05:00 639234034999717463
121 ms 94.130.163.225
15 2026-08-27 04:43 639234024739225358
119 ms 94.130.163.225
14 2026-08-27 04:26 639234014311170162
121 ms 94.130.163.225
13 2026-08-27 04:08 639234003806017640
85 ms 94.130.163.225
12 2026-08-27 03:51 639233993356203030
57 ms 94.130.163.225
11 2026-08-27 02:57 639233961301716608
36 ms 94.130.163.225
10 2026-08-27 02:40 639233950834200647
29 ms 94.130.163.225
9 2026-08-27 02:23 639233940431849026
12 ms 94.130.163.225
8 2026-08-27 02:05 639233930110596398
134 ms 94.130.163.225
7 2026-08-27 01:48 639233919705434540
86 ms 94.130.163.225
6 2026-08-27 01:31 639233909452807845
77 ms 94.130.163.225
5 2026-08-27 01:14 639233899096420820
9 ms 94.130.163.225
4 2026-08-27 00:57 639233888707824939
-
3 2026-08-27 00:39 639233878461203802
26 ms 94.130.163.225
2 2026-08-27 00:22 639233868060868209
34 ms 94.130.163.225
1 2026-08-27 00:04 639233857450922991
12 ms 94.130.163.225