DNS response history for ns5.meobets.com

ns5.meobets.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-25. For this date, NameServerHistory found 30 DNS check records, 30 successful responses, 0 failed responses, and 307 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.meobets.com.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

307 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:20

All timestamps shown in UTC

Latest Resolved IP on Selected Date

34.209.120.123

Most recently resolved hosting IP on selected date

Successful Responses

30

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 ns5.meobets.com

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
30 2026-08-25 10:20 639232492740373468
180 ms 34.209.120.123
29 2026-08-25 10:03 639232482235303141
3 ms 34.209.120.123
28 2026-08-25 09:45 639232471861770303
349 ms 34.209.120.123
27 2026-08-25 09:28 639232461630217327
353 ms 34.209.120.123
26 2026-08-25 09:11 639232451282965990
352 ms 34.209.120.123
25 2026-08-25 08:53 639232440814614938
261 ms 34.209.120.123
24 2026-08-25 08:36 639232430410720425
922 ms 34.209.120.123
23 2026-08-25 08:19 639232420003096185
173 ms 34.209.120.123
22 2026-08-25 08:01 639232409467287444
355 ms 34.209.120.123
21 2026-08-25 07:44 639232399077195997
188 ms 34.209.120.123
20 2026-08-25 07:26 639232388731528337
362 ms 34.209.120.123
19 2026-08-25 07:09 639232378288598612
354 ms 34.209.120.123
18 2026-08-25 06:15 639232346196373643
3 ms 34.209.120.123
17 2026-08-25 05:59 639232336112370741
353 ms 34.209.120.123
16 2026-08-25 05:42 639232326146508970
4 ms 34.209.120.123
15 2026-08-25 05:25 639232316189381720
3 ms 34.209.120.123
14 2026-08-25 05:09 639232306217998913
184 ms 34.209.120.123
13 2026-08-25 04:52 639232296255744174
170 ms 34.209.120.123
12 2026-08-25 04:35 639232286095760789
188 ms 34.209.120.123
11 2026-08-25 04:18 639232276086186273
169 ms 34.209.120.123
10 2026-08-25 04:02 639232265900986425
366 ms 34.209.120.123
9 2026-08-25 03:45 639232255723518075
168 ms 34.209.120.123
8 2026-08-25 03:28 639232245484452890
361 ms 34.209.120.123
7 2026-08-25 03:11 639232235157175331
170 ms 34.209.120.123
6 2026-08-25 02:17 639232203197189095
169 ms 34.209.120.123
5 2026-08-25 02:00 639232192844564298
172 ms 34.209.120.123
4 2026-08-25 01:43 639232182496008942
167 ms 34.209.120.123
3 2026-08-25 01:26 639232172197053132
169 ms 34.209.120.123
2 2026-08-25 00:32 639232140250307418
2203 ms 34.209.120.123
1 2026-08-25 00:15 639232129927860324
334 ms 34.209.120.123