DNS response history for ns2.meetings-by-mail.com

ns2.meetings-by-mail.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 29 DNS check records, 29 successful responses, 0 failed responses, and 394 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.meetings-by-mail.com.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

394 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 09:27

All timestamps shown in UTC

Latest Resolved IP on Selected Date

107.172.56.155

Most recently resolved hosting IP on selected date

Successful Responses

29

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.meetings-by-mail.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
29 2026-08-27 09:27 639234191649612722
217 ms 107.172.56.155
28 2026-08-27 09:10 639234181105879568
237 ms 107.172.56.155
27 2026-08-27 08:52 639234170713214496
2154 ms 107.172.56.155
26 2026-08-27 08:35 639234160341037652
224 ms 107.172.56.155
25 2026-08-27 08:18 639234149799404224
222 ms 107.172.56.155
24 2026-08-27 08:00 639234139553286469
227 ms 107.172.56.155
23 2026-08-27 07:07 639234107183588293
207 ms 107.172.56.155
22 2026-08-27 06:49 639234096905435724
208 ms 107.172.56.155
21 2026-08-27 06:32 639234086579410775
105 ms 107.172.56.155
20 2026-08-27 06:15 639234076291157956
209 ms 107.172.56.155
19 2026-08-27 05:58 639234065981939454
42 ms 107.172.56.155
18 2026-08-27 05:41 639234055548642997
227 ms 107.172.56.155
17 2026-08-27 05:23 639234045267979603
227 ms 107.172.56.155
16 2026-08-27 05:06 639234034999717463
223 ms 107.172.56.155
15 2026-08-27 04:49 639234024739225358
111 ms 107.172.56.155
14 2026-08-27 04:32 639234014311170162
219 ms 107.172.56.155
13 2026-08-27 04:14 639234003806017640
216 ms 107.172.56.155
12 2026-08-27 03:57 639233993356203030
212 ms 107.172.56.155
11 2026-08-27 03:04 639233961301716608
2106 ms 107.172.56.155
10 2026-08-27 02:46 639233950834200647
106 ms 107.172.56.155
9 2026-08-27 02:29 639233940431849026
210 ms 107.172.56.155
8 2026-08-27 02:12 639233930110596398
212 ms 107.172.56.155
7 2026-08-27 01:54 639233919705434540
209 ms 107.172.56.155
6 2026-08-27 01:37 639233909452807845
210 ms 107.172.56.155
5 2026-08-27 01:20 639233899096420820
122 ms 107.172.56.155
4 2026-08-27 01:03 639233888707824939
211 ms 107.172.56.155
3 2026-08-27 00:45 639233878461203802
2110 ms 107.172.56.155
2 2026-08-27 00:28 639233868060868209
211 ms 107.172.56.155
1 2026-08-27 00:11 639233857450922991
218 ms 107.172.56.155