DNS response history for ns2.mojowebservices.com

ns2.mojowebservices.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 28 DNS check records, 28 successful responses, 0 failed responses, and 230 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.mojowebservices.com.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

230 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:41

All timestamps shown in UTC

Latest Resolved IP on Selected Date

74.81.90.99

Most recently resolved hosting IP on selected date

Successful Responses

28

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.mojowebservices.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
28 2026-08-25 09:41 639232471861770303
279 ms 74.81.90.99
27 2026-08-25 09:23 639232461630217327
3 ms 74.81.90.99
26 2026-08-25 09:06 639232451282965990
326 ms 74.81.90.99
25 2026-08-25 08:49 639232440814614938
17 ms 74.81.90.99
24 2026-08-25 08:32 639232430410720425
285 ms 74.81.90.99
23 2026-08-25 08:14 639232420003096185
160 ms 74.81.90.99
22 2026-08-25 07:57 639232409467287444
4 ms 74.81.90.99
21 2026-08-25 07:39 639232399077195997
3 ms 74.81.90.99
20 2026-08-25 07:22 639232388731528337
270 ms 74.81.90.99
19 2026-08-25 07:05 639232378288598612
270 ms 74.81.90.99
18 2026-08-25 06:11 639232346196373643
11 ms 74.81.90.99
17 2026-08-25 05:54 639232336112370741
7 ms 74.81.90.99
16 2026-08-25 05:38 639232326146508970
25 ms 74.81.90.99
15 2026-08-25 05:21 639232316189381720
4 ms 74.81.90.99
14 2026-08-25 05:05 639232306217998913
9 ms 74.81.90.99
13 2026-08-25 04:48 639232296255744174
275 ms 74.81.90.99
12 2026-08-25 04:31 639232286095760789
271 ms 74.81.90.99
11 2026-08-25 04:14 639232276086186273
283 ms 74.81.90.99
10 2026-08-25 03:57 639232265900986425
2261 ms 74.81.90.99
9 2026-08-25 03:40 639232255723518075
3 ms 74.81.90.99
8 2026-08-25 03:23 639232245484452890
271 ms 74.81.90.99
7 2026-08-25 03:06 639232235157175331
272 ms 74.81.90.99
6 2026-08-25 02:13 639232203197189095
287 ms 74.81.90.99
5 2026-08-25 01:56 639232192844564298
284 ms 74.81.90.99
4 2026-08-25 01:38 639232182496008942
3 ms 74.81.90.99
3 2026-08-25 01:21 639232172197053132
4 ms 74.81.90.99
2 2026-08-25 00:28 639232140250307418
271 ms 74.81.90.99
1 2026-08-25 00:11 639232129927860324
270 ms 74.81.90.99