DNS response history for ns02.m2mwireless.com

ns02.m2mwireless.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 32 DNS check records, 32 successful responses, 0 failed responses, and 356 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 ns02.m2mwireless.com.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

356 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:16

All timestamps shown in UTC

Latest Resolved IP on Selected Date

47.180.54.107

Most recently resolved hosting IP on selected date

Successful Responses

32

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 ns02.m2mwireless.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
32 2026-08-25 11:16 639232524938080723
344 ms 47.180.54.107
31 2026-08-25 10:22 639232492740373468
327 ms 47.180.54.107
30 2026-08-25 10:05 639232482235303141
330 ms 47.180.54.107
29 2026-08-25 09:47 639232471861770303
335 ms 47.180.54.107
28 2026-08-25 09:30 639232461630217327
346 ms 47.180.54.107
27 2026-08-25 09:13 639232451282965990
350 ms 47.180.54.107
26 2026-08-25 08:56 639232440814614938
330 ms 47.180.54.107
25 2026-08-25 08:38 639232430410720425
327 ms 47.180.54.107
24 2026-08-25 08:21 639232420003096185
332 ms 47.180.54.107
23 2026-08-25 08:03 639232409467287444
332 ms 47.180.54.107
22 2026-08-25 07:46 639232399077195997
336 ms 47.180.54.107
21 2026-08-25 07:29 639232388731528337
346 ms 47.180.54.107
20 2026-08-25 07:11 639232378288598612
352 ms 47.180.54.107
19 2026-08-25 06:17 639232346196373643
335 ms 47.180.54.107
18 2026-08-25 06:01 639232336112370741
336 ms 47.180.54.107
17 2026-08-25 05:44 639232326146508970
327 ms 47.180.54.107
16 2026-08-25 05:27 639232316189381720
5 ms 47.180.54.107
15 2026-08-25 05:11 639232306217998913
337 ms 47.180.54.107
14 2026-08-25 04:54 639232296255744174
332 ms 47.180.54.107
13 2026-08-25 04:37 639232286095760789
326 ms 47.180.54.107
12 2026-08-25 04:20 639232276086186273
341 ms 47.180.54.107
11 2026-08-25 04:04 639232265900986425
335 ms 47.180.54.107
10 2026-08-25 03:47 639232255723518075
328 ms 47.180.54.107
9 2026-08-25 03:30 639232245484452890
335 ms 47.180.54.107
8 2026-08-25 03:13 639232235157175331
329 ms 47.180.54.107
7 2026-08-25 02:19 639232203197189095
336 ms 47.180.54.107
6 2026-08-25 02:02 639232192844564298
332 ms 47.180.54.107
5 2026-08-25 01:45 639232182496008942
1334 ms 47.180.54.107
4 2026-08-25 01:28 639232172197053132
341 ms 47.180.54.107
3 2026-08-25 00:34 639232140250307418
333 ms 47.180.54.107
2 2026-08-25 00:17 639232129927860324
328 ms 47.180.54.107
1 2026-08-25 00:00 639232119551972438
334 ms 47.180.54.107