DNS response history for mx.nanogherkin.com

mx.nanogherkin.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 36 DNS check records, 35 successful responses, 1 failed responses, and 125 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 mx.nanogherkin.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

125 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:32

All timestamps shown in UTC

Latest Resolved IP on Selected Date

212.69.35.75

Most recently resolved hosting IP on selected date

Successful Responses

35

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for mx.nanogherkin.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
36 2026-08-25 12:32 639232576780683689
51 ms 212.69.35.75
35 2026-08-25 12:14 639232566381512620
53 ms 212.69.35.75
34 2026-08-25 11:57 639232556111768563
60 ms 212.69.35.75
33 2026-08-25 11:40 639232545839529039
51 ms 212.69.35.75
32 2026-08-25 11:22 639232535349285207
64 ms 212.69.35.75
31 2026-08-25 11:05 639232524938080723
53 ms 212.69.35.75
30 2026-08-25 10:11 639232492740373468
51 ms 212.69.35.75
29 2026-08-25 09:54 639232482235303141
46 ms 212.69.35.75
28 2026-08-25 09:37 639232471861770303
52 ms 212.69.35.75
27 2026-08-25 09:20 639232461630217327
43 ms 212.69.35.75
26 2026-08-25 09:02 639232451282965990
78 ms 212.69.35.75
25 2026-08-25 08:45 639232440814614938
68 ms 212.69.35.75
24 2026-08-25 08:27 639232430410720425
61 ms 212.69.35.75
23 2026-08-25 08:10 639232420003096185
42 ms 212.69.35.75
22 2026-08-25 07:53 639232409467287444
60 ms 212.69.35.75
21 2026-08-25 07:35 639232399077195997
48 ms 212.69.35.75
20 2026-08-25 07:18 639232388731528337
53 ms 212.69.35.75
19 2026-08-25 07:01 639232378288598612
44 ms 212.69.35.75
18 2026-08-25 06:07 639232346196373643
77 ms 212.69.35.75
17 2026-08-25 05:50 639232336112370741
57 ms 212.69.35.75
16 2026-08-25 05:34 639232326146508970
62 ms 212.69.35.75
15 2026-08-25 05:17 639232316189381720
230 ms 212.69.35.75
14 2026-08-25 05:01 639232306217998913
50 ms 212.69.35.75
13 2026-08-25 04:44 639232296255744174
15 ms 212.69.35.75
12 2026-08-25 04:27 639232286095760789
46 ms 212.69.35.75
11 2026-08-25 04:10 639232276086186273
91 ms 212.69.35.75
10 2026-08-25 03:53 639232265900986425
2213 ms 212.69.35.75
9 2026-08-25 03:36 639232255723518075
48 ms 212.69.35.75
8 2026-08-25 03:19 639232245484452890
36 ms 212.69.35.75
7 2026-08-25 03:02 639232235157175331
61 ms 212.69.35.75
6 2026-08-25 02:09 639232203197189095
-
5 2026-08-25 01:52 639232192844564298
73 ms 212.69.35.75
4 2026-08-25 01:34 639232182496008942
43 ms 212.69.35.75
3 2026-08-25 01:17 639232172197053132
205 ms 212.69.35.75
2 2026-08-25 00:24 639232140250307418
47 ms 212.69.35.75
1 2026-08-25 00:07 639232129927860324
51 ms 212.69.35.75