DNS response history for ns2.cosmos.mx

ns2.cosmos.mx 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 321 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.cosmos.mx.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

321 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:21

All timestamps shown in UTC

Latest Resolved IP on Selected Date

205.251.156.35

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.cosmos.mx

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:21 639232492740373468
5 ms 205.251.156.35
29 2026-08-25 10:04 639232482235303141
134 ms 205.251.156.35
28 2026-08-25 09:46 639232471861770303
287 ms 205.251.156.35
27 2026-08-25 09:29 639232461630217327
1890 ms 205.251.156.35
26 2026-08-25 09:12 639232451282965990
5 ms 205.251.156.35
25 2026-08-25 08:55 639232440814614938
272 ms 205.251.156.35
24 2026-08-25 08:37 639232430410720425
3 ms 205.251.156.35
23 2026-08-25 08:20 639232420003096185
764 ms 205.251.156.35
22 2026-08-25 08:02 639232409467287444
130 ms 205.251.156.35
21 2026-08-25 07:45 639232399077195997
285 ms 205.251.156.35
20 2026-08-25 07:27 639232388731528337
262 ms 205.251.156.35
19 2026-08-25 07:10 639232378288598612
139 ms 205.251.156.35
18 2026-08-25 06:16 639232346196373643
626 ms 205.251.156.35
17 2026-08-25 06:00 639232336112370741
4 ms 205.251.156.35
16 2026-08-25 05:43 639232326146508970
276 ms 205.251.156.35
15 2026-08-25 05:26 639232316189381720
3 ms 205.251.156.35
14 2026-08-25 05:10 639232306217998913
133 ms 205.251.156.35
13 2026-08-25 04:53 639232296255744174
272 ms 205.251.156.35
12 2026-08-25 04:36 639232286095760789
280 ms 205.251.156.35
11 2026-08-25 04:19 639232276086186273
630 ms 205.251.156.35
10 2026-08-25 04:03 639232265900986425
782 ms 205.251.156.35
9 2026-08-25 03:46 639232255723518075
655 ms 205.251.156.35
8 2026-08-25 03:29 639232245484452890
203 ms 205.251.156.35
7 2026-08-25 03:12 639232235157175331
261 ms 205.251.156.35
6 2026-08-25 02:18 639232203197189095
273 ms 205.251.156.35
5 2026-08-25 02:01 639232192844564298
9 ms 205.251.156.35
4 2026-08-25 01:44 639232182496008942
478 ms 205.251.156.35
3 2026-08-25 01:27 639232172197053132
274 ms 205.251.156.35
2 2026-08-25 00:33 639232140250307418
142 ms 205.251.156.35
1 2026-08-25 00:16 639232129927860324
148 ms 205.251.156.35