DNS response history for mx2.nyquest.no

mx2.nyquest.no 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 37 DNS check records, 37 successful responses, 0 failed responses, and 489 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 mx2.nyquest.no.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

489 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:56

All timestamps shown in UTC

Latest Resolved IP on Selected Date

167.179.70.83

Most recently resolved hosting IP on selected date

Successful Responses

37

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 mx2.nyquest.no

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
37 2026-08-25 12:56 639232587225721862
523 ms 167.179.70.83
36 2026-08-25 12:39 639232576780683689
474 ms 167.179.70.83
35 2026-08-25 12:22 639232566381512620
520 ms 167.179.70.83
34 2026-08-25 12:04 639232556111768563
500 ms 167.179.70.83
33 2026-08-25 11:47 639232545839529039
262 ms 167.179.70.83
32 2026-08-25 11:30 639232535349285207
505 ms 167.179.70.83
31 2026-08-25 11:13 639232524938080723
2007 ms 167.179.70.83
30 2026-08-25 10:19 639232492740373468
242 ms 167.179.70.83
29 2026-08-25 10:02 639232482235303141
247 ms 167.179.70.83
28 2026-08-25 09:44 639232471861770303
544 ms 167.179.70.83
27 2026-08-25 09:27 639232461630217327
542 ms 167.179.70.83
26 2026-08-25 09:10 639232451282965990
487 ms 167.179.70.83
25 2026-08-25 08:52 639232440814614938
418 ms 167.179.70.83
24 2026-08-25 08:35 639232430410720425
539 ms 167.179.70.83
23 2026-08-25 08:18 639232420003096185
508 ms 167.179.70.83
22 2026-08-25 08:00 639232409467287444
7 ms 167.179.70.83
21 2026-08-25 07:43 639232399077195997
4 ms 167.179.70.83
20 2026-08-25 07:26 639232388731528337
467 ms 167.179.70.83
19 2026-08-25 07:08 639232378288598612
4 ms 167.179.70.83
18 2026-08-25 06:14 639232346196373643
473 ms 167.179.70.83
17 2026-08-25 05:58 639232336112370741
10 ms 167.179.70.83
16 2026-08-25 05:41 639232326146508970
251 ms 167.179.70.83
15 2026-08-25 05:24 639232316189381720
658 ms 167.179.70.83
14 2026-08-25 05:08 639232306217998913
230 ms 167.179.70.83
13 2026-08-25 04:51 639232296255744174
2018 ms 167.179.70.83
12 2026-08-25 04:34 639232286095760789
242 ms 167.179.70.83
11 2026-08-25 04:17 639232276086186273
7 ms 167.179.70.83
10 2026-08-25 04:01 639232265900986425
3 ms 167.179.70.83
9 2026-08-25 03:44 639232255723518075
3 ms 167.179.70.83
8 2026-08-25 03:27 639232245484452890
482 ms 167.179.70.83
7 2026-08-25 03:10 639232235157175331
285 ms 167.179.70.83
6 2026-08-25 02:16 639232203197189095
493 ms 167.179.70.83
5 2026-08-25 01:59 639232192844564298
2313 ms 167.179.70.83
4 2026-08-25 01:42 639232182496008942
261 ms 167.179.70.83
3 2026-08-25 01:25 639232172197053132
530 ms 167.179.70.83
2 2026-08-25 00:31 639232140250307418
522 ms 167.179.70.83
1 2026-08-25 00:14 639232129927860324
528 ms 167.179.70.83