DNS response history for ns2.mohasagordns.com

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

29

Historical checks stored for this nameserver on selected date

Average Latency

98 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:50

All timestamps shown in UTC

Latest Resolved IP on Selected Date

15.235.152.136

Most recently resolved hosting IP on selected date

Successful Responses

29

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.mohasagordns.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
29 2026-08-25 09:50 639232482235303141
9 ms 15.235.152.136
28 2026-08-25 09:33 639232471861770303
33 ms 15.235.152.136
27 2026-08-25 09:16 639232461630217327
28 ms 15.235.152.136
26 2026-08-25 08:59 639232451282965990
31 ms 15.235.152.136
25 2026-08-25 08:41 639232440814614938
12 ms 15.235.152.136
24 2026-08-25 08:24 639232430410720425
17 ms 15.235.152.136
23 2026-08-25 08:07 639232420003096185
16 ms 15.235.152.136
22 2026-08-25 07:49 639232409467287444
10 ms 15.235.152.136
21 2026-08-25 07:32 639232399077195997
18 ms 15.235.152.136
20 2026-08-25 07:14 639232388731528337
17 ms 15.235.152.136
19 2026-08-25 06:57 639232378288598612
71 ms 15.235.152.136
18 2026-08-25 06:04 639232346196373643
9 ms 15.235.152.136
17 2026-08-25 05:47 639232336112370741
2042 ms 15.235.152.136
16 2026-08-25 05:30 639232326146508970
25 ms 15.235.152.136
15 2026-08-25 05:14 639232316189381720
55 ms 15.235.152.136
14 2026-08-25 04:57 639232306217998913
114 ms 15.235.152.136
13 2026-08-25 04:40 639232296255744174
25 ms 15.235.152.136
12 2026-08-25 04:23 639232286095760789
8 ms 15.235.152.136
11 2026-08-25 04:07 639232276086186273
9 ms 15.235.152.136
10 2026-08-25 03:50 639232265900986425
8 ms 15.235.152.136
9 2026-08-25 03:33 639232255723518075
31 ms 15.235.152.136
8 2026-08-25 03:16 639232245484452890
16 ms 15.235.152.136
7 2026-08-25 02:59 639232235157175331
9 ms 15.235.152.136
6 2026-08-25 02:05 639232203197189095
133 ms 15.235.152.136
5 2026-08-25 01:48 639232192844564298
47 ms 15.235.152.136
4 2026-08-25 01:31 639232182496008942
10 ms 15.235.152.136
3 2026-08-25 01:14 639232172197053132
10 ms 15.235.152.136
2 2026-08-25 00:20 639232140250307418
9 ms 15.235.152.136
1 2026-08-25 00:03 639232129927860324
19 ms 15.235.152.136