DNS response history for ns2.mojodeepcloud.tech

ns2.mojodeepcloud.tech 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 36 DNS check records, 36 successful responses, 0 failed responses, and 360 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.mojodeepcloud.tech.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

360 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:26

All timestamps shown in UTC

Latest Resolved IP on Selected Date

45.238.156.18

Most recently resolved hosting IP on selected date

Successful Responses

36

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.mojodeepcloud.tech

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
36 2026-08-25 12:26 639232566381512620
426 ms 45.238.156.18
35 2026-08-25 12:09 639232556111768563
430 ms 45.238.156.18
34 2026-08-25 11:51 639232545839529039
377 ms 103.130.238.112
33 2026-08-25 11:34 639232535349285207
371 ms 103.130.238.112
32 2026-08-25 11:17 639232524938080723
240 ms 103.130.238.112
31 2026-08-25 10:23 639232492740373468
4 ms 103.130.238.112
30 2026-08-25 10:06 639232482235303141
238 ms 103.130.238.112
29 2026-08-25 09:48 639232471861770303
369 ms 103.130.238.112
28 2026-08-25 09:31 639232461630217327
371 ms 103.130.238.112
27 2026-08-25 09:14 639232451282965990
824 ms 103.130.238.112
26 2026-08-25 08:57 639232440814614938
358 ms 103.130.238.112
25 2026-08-25 08:39 639232430410720425
366 ms 103.130.238.112
24 2026-08-25 08:22 639232420003096185
374 ms 103.130.238.112
23 2026-08-25 08:04 639232409467287444
361 ms 103.130.238.112
22 2026-08-25 07:47 639232399077195997
233 ms 103.130.238.112
21 2026-08-25 07:30 639232388731528337
369 ms 103.130.238.112
20 2026-08-25 07:12 639232378288598612
368 ms 103.130.238.112
19 2026-08-25 06:18 639232346196373643
380 ms 103.130.238.112
18 2026-08-25 06:02 639232336112370741
949 ms 103.130.238.112
17 2026-08-25 05:45 639232326146508970
369 ms 103.130.238.112
16 2026-08-25 05:28 639232316189381720
3 ms 103.130.238.112
15 2026-08-25 05:12 639232306217998913
371 ms 103.130.238.112
14 2026-08-25 04:55 639232296255744174
373 ms 103.130.238.112
13 2026-08-25 04:38 639232286095760789
367 ms 103.130.238.112
12 2026-08-25 04:21 639232276086186273
369 ms 103.130.238.112
11 2026-08-25 04:05 639232265900986425
373 ms 103.130.238.112
10 2026-08-25 03:48 639232255723518075
245 ms 103.130.238.112
9 2026-08-25 03:31 639232245484452890
366 ms 103.130.238.112
8 2026-08-25 03:14 639232235157175331
371 ms 103.130.238.112
7 2026-08-25 02:20 639232203197189095
369 ms 103.130.238.112
6 2026-08-25 02:03 639232192844564298
363 ms 103.130.238.112
5 2026-08-25 01:46 639232182496008942
241 ms 103.130.238.112
4 2026-08-25 01:29 639232172197053132
367 ms 103.130.238.112
3 2026-08-25 00:35 639232140250307418
243 ms 103.130.238.112
2 2026-08-25 00:18 639232129927860324
367 ms 103.130.238.112
1 2026-08-25 00:01 639232119551972438
412 ms 103.130.238.112