DNS response history for ns2.briyam.com.mx

ns2.briyam.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 27 DNS check records, 27 successful responses, 0 failed responses, and 398 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.briyam.com.mx.
Records on Selected Date

27

Historical checks stored for this nameserver on selected date

Average Latency

398 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:27

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.138.188.6

Most recently resolved hosting IP on selected date

Successful Responses

27

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.briyam.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
27 2026-08-25 09:27 639232461630217327
324 ms 103.138.188.6
26 2026-08-25 09:10 639232451282965990
764 ms 103.138.188.6
25 2026-08-25 08:53 639232440814614938
327 ms 103.138.188.6
24 2026-08-25 08:36 639232430410720425
161 ms 103.138.188.6
23 2026-08-25 08:18 639232420003096185
322 ms 103.138.188.6
22 2026-08-25 08:01 639232409467287444
9 ms 103.138.188.6
21 2026-08-25 07:43 639232399077195997
157 ms 103.138.188.6
20 2026-08-25 07:26 639232388731528337
321 ms 103.138.188.6
19 2026-08-25 07:09 639232378288598612
463 ms 103.138.188.6
18 2026-08-25 06:15 639232346196373643
3 ms 103.138.188.6
17 2026-08-25 05:58 639232336112370741
34 ms 103.138.188.6
16 2026-08-25 05:41 639232326146508970
4 ms 103.138.188.6
15 2026-08-25 05:25 639232316189381720
3 ms 103.138.188.6
14 2026-08-25 05:08 639232306217998913
39 ms 103.138.188.6
13 2026-08-25 04:52 639232296255744174
319 ms 103.138.188.6
12 2026-08-25 04:35 639232286095760789
164 ms 103.138.188.6
11 2026-08-25 04:18 639232276086186273
169 ms 103.138.188.6
10 2026-08-25 04:01 639232265900986425
333 ms 103.138.188.6
9 2026-08-25 03:44 639232255723518075
328 ms 103.138.188.6
8 2026-08-25 03:27 639232245484452890
321 ms 103.138.188.6
7 2026-08-25 03:10 639232235157175331
324 ms 103.138.188.6
6 2026-08-25 02:17 639232203197189095
2311 ms 103.138.188.6
5 2026-08-25 02:00 639232192844564298
576 ms 103.138.188.6
4 2026-08-25 01:42 639232182496008942
322 ms 103.138.188.6
3 2026-08-25 01:25 639232172197053132
2007 ms 103.138.188.6
2 2026-08-25 00:32 639232140250307418
323 ms 103.138.188.6
1 2026-08-25 00:15 639232129927860324
318 ms 103.138.188.6