DNS response history for ns2.hospedame.cloud

ns2.hospedame.cloud 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 38 DNS check records, 38 successful responses, 0 failed responses, and 210 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.hospedame.cloud.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

210 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 13:13

All timestamps shown in UTC

Latest Resolved IP on Selected Date

98.142.99.220

Most recently resolved hosting IP on selected date

Successful Responses

38

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.hospedame.cloud

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
38 2026-08-25 13:13 639232597643611557
263 ms 98.142.99.220
37 2026-08-25 12:56 639232587225721862
257 ms 98.142.99.220
36 2026-08-25 12:39 639232576780683689
260 ms 98.142.99.220
35 2026-08-25 12:21 639232566381512620
427 ms 98.142.99.220
34 2026-08-25 12:04 639232556111768563
250 ms 98.142.99.220
33 2026-08-25 11:47 639232545839529039
8 ms 98.142.99.220
32 2026-08-25 11:30 639232535349285207
261 ms 98.142.99.220
31 2026-08-25 11:12 639232524938080723
260 ms 98.142.99.220
30 2026-08-25 10:18 639232492740373468
260 ms 98.142.99.220
29 2026-08-25 10:01 639232482235303141
258 ms 98.142.99.220
28 2026-08-25 09:44 639232471861770303
166 ms 98.142.99.220
27 2026-08-25 09:26 639232461630217327
260 ms 98.142.99.220
26 2026-08-25 09:09 639232451282965990
138 ms 98.142.99.220
25 2026-08-25 08:52 639232440814614938
265 ms 98.142.99.220
24 2026-08-25 08:34 639232430410720425
257 ms 98.142.99.220
23 2026-08-25 08:17 639232420003096185
257 ms 98.142.99.220
22 2026-08-25 08:00 639232409467287444
257 ms 98.142.99.220
21 2026-08-25 07:42 639232399077195997
126 ms 98.142.99.220
20 2026-08-25 07:25 639232388731528337
262 ms 98.142.99.220
19 2026-08-25 07:08 639232378288598612
258 ms 98.142.99.220
18 2026-08-25 06:14 639232346196373643
259 ms 98.142.99.220
17 2026-08-25 05:57 639232336112370741
265 ms 98.142.99.220
16 2026-08-25 05:41 639232326146508970
4 ms 98.142.99.220
15 2026-08-25 05:24 639232316189381720
129 ms 98.142.99.220
14 2026-08-25 05:07 639232306217998913
3 ms 98.142.99.220
13 2026-08-25 04:51 639232296255744174
257 ms 98.142.99.220
12 2026-08-25 04:34 639232286095760789
260 ms 98.142.99.220
11 2026-08-25 04:17 639232276086186273
257 ms 98.142.99.220
10 2026-08-25 04:00 639232265900986425
257 ms 98.142.99.220
9 2026-08-25 03:43 639232255723518075
258 ms 98.142.99.220
8 2026-08-25 03:26 639232245484452890
257 ms 98.142.99.220
7 2026-08-25 03:09 639232235157175331
126 ms 98.142.99.220
6 2026-08-25 02:16 639232203197189095
258 ms 98.142.99.220
5 2026-08-25 01:59 639232192844564298
7 ms 98.142.99.220
4 2026-08-25 01:41 639232182496008942
134 ms 98.142.99.220
3 2026-08-25 01:24 639232172197053132
125 ms 98.142.99.220
2 2026-08-25 00:31 639232140250307418
126 ms 98.142.99.220
1 2026-08-25 00:14 639232129927860324
258 ms 98.142.99.220