DNS response history for ns2.corpgmg.com.mx

ns2.corpgmg.com.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 525 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.corpgmg.com.mx.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

525 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:17

All timestamps shown in UTC

Latest Resolved IP on Selected Date

198.50.127.141

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.corpgmg.com.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:17 639232492740373468
228 ms 198.50.127.141
29 2026-08-25 10:00 639232482235303141
208 ms 198.50.127.141
28 2026-08-25 09:43 639232471861770303
145 ms 198.50.127.141
27 2026-08-25 09:25 639232461630217327
210 ms 198.50.127.141
26 2026-08-25 09:08 639232451282965990
4212 ms 198.50.127.141
25 2026-08-25 08:51 639232440814614938
202 ms 198.50.127.141
24 2026-08-25 08:33 639232430410720425
201 ms 198.50.127.141
23 2026-08-25 08:16 639232420003096185
206 ms 198.50.127.141
22 2026-08-25 07:59 639232409467287444
199 ms 198.50.127.141
21 2026-08-25 07:41 639232399077195997
100 ms 198.50.127.141
20 2026-08-25 07:24 639232388731528337
199 ms 198.50.127.141
19 2026-08-25 07:07 639232378288598612
206 ms 198.50.127.141
18 2026-08-25 06:13 639232346196373643
200 ms 198.50.127.141
17 2026-08-25 05:56 639232336112370741
2112 ms 198.50.127.141
16 2026-08-25 05:40 639232326146508970
105 ms 198.50.127.141
15 2026-08-25 05:23 639232316189381720
111 ms 198.50.127.141
14 2026-08-25 05:06 639232306217998913
106 ms 198.50.127.141
13 2026-08-25 04:50 639232296255744174
225 ms 198.50.127.141
12 2026-08-25 04:33 639232286095760789
2401 ms 198.50.127.141
11 2026-08-25 04:16 639232276086186273
217 ms 198.50.127.141
10 2026-08-25 03:59 639232265900986425
261 ms 198.50.127.141
9 2026-08-25 03:42 639232255723518075
94 ms 198.50.127.141
8 2026-08-25 03:25 639232245484452890
222 ms 198.50.127.141
7 2026-08-25 03:08 639232235157175331
208 ms 198.50.127.141
6 2026-08-25 02:15 639232203197189095
222 ms 198.50.127.141
5 2026-08-25 01:58 639232192844564298
113 ms 198.50.127.141
4 2026-08-25 01:40 639232182496008942
222 ms 198.50.127.141
3 2026-08-25 01:23 639232172197053132
223 ms 198.50.127.141
2 2026-08-25 00:30 639232140250307418
2148 ms 198.50.127.141
1 2026-08-25 00:13 639232129927860324
235 ms 198.50.127.141