DNS response history for ns5.m2o.bet

ns5.m2o.bet 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-25. For this date, NameServerHistory found 28 DNS check records, 27 successful responses, 1 failed responses, and 441 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 ns5.m2o.bet.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

441 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:40

All timestamps shown in UTC

Latest Resolved IP on Selected Date

192.142.0.100

Most recently resolved hosting IP on selected date

Successful Responses

27

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

4%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns5.m2o.bet

Showing DNS history for 2026-08-25 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
28 2026-08-25 09:40 639232471861770303
42 ms 192.142.0.100
27 2026-08-25 09:23 639232461630217327
2029 ms 84.201.6.137
26 2026-08-25 09:05 639232451282965990
65 ms 192.142.0.100
25 2026-08-25 08:48 639232440814614938
26 ms 195.54.174.165
24 2026-08-25 08:31 639232430410720425
2231 ms 192.142.0.100
23 2026-08-25 08:13 639232420003096185
67 ms 195.54.174.165
22 2026-08-25 07:56 639232409467287444
65 ms 192.142.0.100
21 2026-08-25 07:38 639232399077195997
34 ms 195.54.174.165
20 2026-08-25 07:21 639232388731528337
57 ms 192.142.0.100
19 2026-08-25 07:04 639232378288598612
35 ms 192.142.0.100
18 2026-08-25 06:10 639232346196373643
31 ms 84.201.6.137
17 2026-08-25 05:53 639232336112370741
41 ms 192.142.0.100
16 2026-08-25 05:37 639232326146508970
190 ms 84.201.6.137
15 2026-08-25 05:20 639232316189381720
-
14 2026-08-25 05:04 639232306217998913
119 ms 195.54.174.165
13 2026-08-25 04:47 639232296255744174
34 ms 84.201.6.137
12 2026-08-25 04:30 639232286095760789
2022 ms 84.201.6.137
11 2026-08-25 04:13 639232276086186273
36 ms 195.54.174.165
10 2026-08-25 03:56 639232265900986425
141 ms 192.142.0.100
9 2026-08-25 03:39 639232255723518075
2117 ms 192.142.0.100
8 2026-08-25 03:22 639232245484452890
53 ms 192.142.0.100
7 2026-08-25 03:05 639232235157175331
40 ms 192.142.0.100
6 2026-08-25 02:12 639232203197189095
167 ms 195.54.174.165
5 2026-08-25 01:55 639232192844564298
34 ms 195.54.174.165
4 2026-08-25 01:37 639232182496008942
30 ms 192.142.0.100
3 2026-08-25 01:20 639232172197053132
30 ms 192.142.0.100
2 2026-08-25 00:27 639232140250307418
28 ms 84.201.6.137
1 2026-08-25 00:10 639232129927860324
2148 ms 195.54.174.165