DNS response history for ns2.mojobuzz.com

ns2.mojobuzz.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 226 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.mojobuzz.com.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

226 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:19

All timestamps shown in UTC

Latest Resolved IP on Selected Date

3.141.241.213

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 ns2.mojobuzz.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:19 639232492740373468
213 ms 3.141.241.213
29 2026-08-25 10:02 639232482235303141
209 ms 3.141.241.213
28 2026-08-25 09:44 639232471861770303
211 ms 3.141.241.213
27 2026-08-25 09:27 639232461630217327
212 ms 3.141.241.213
26 2026-08-25 09:10 639232451282965990
214 ms 3.141.241.213
25 2026-08-25 08:52 639232440814614938
33 ms 3.141.241.213
24 2026-08-25 08:35 639232430410720425
32 ms 3.141.241.213
23 2026-08-25 08:18 639232420003096185
208 ms 3.141.241.213
22 2026-08-25 08:00 639232409467287444
166 ms 3.141.241.213
21 2026-08-25 07:43 639232399077195997
235 ms 3.141.241.213
20 2026-08-25 07:26 639232388731528337
144 ms 3.141.241.213
19 2026-08-25 07:08 639232378288598612
217 ms 3.141.241.213
18 2026-08-25 06:15 639232346196373643
202 ms 3.141.241.213
17 2026-08-25 05:58 639232336112370741
205 ms 3.141.241.213
16 2026-08-25 05:41 639232326146508970
231 ms 3.141.241.213
15 2026-08-25 05:24 639232316189381720
203 ms 3.141.241.213
14 2026-08-25 05:08 639232306217998913
207 ms 3.141.241.213
13 2026-08-25 04:51 639232296255744174
212 ms 3.141.241.213
12 2026-08-25 04:34 639232286095760789
8 ms 3.141.241.213
11 2026-08-25 04:17 639232276086186273
111 ms 3.141.241.213
10 2026-08-25 04:01 639232265900986425
217 ms 3.141.241.213
9 2026-08-25 03:44 639232255723518075
202 ms 3.141.241.213
8 2026-08-25 03:27 639232245484452890
1629 ms 3.141.241.213
7 2026-08-25 03:10 639232235157175331
211 ms 3.141.241.213
6 2026-08-25 02:16 639232203197189095
219 ms 3.141.241.213
5 2026-08-25 01:59 639232192844564298
200 ms 3.141.241.213
4 2026-08-25 01:42 639232182496008942
107 ms 3.141.241.213
3 2026-08-25 01:25 639232172197053132
122 ms 3.141.241.213
2 2026-08-25 00:31 639232140250307418
205 ms 3.141.241.213
1 2026-08-25 00:14 639232129927860324
204 ms 3.141.241.213