DNS response history for ns2.pressly.news

ns2.pressly.news 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 366 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.pressly.news.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

366 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:58

All timestamps shown in UTC

Latest Resolved IP on Selected Date

216.198.79.1

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 ns2.pressly.news

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:58 639232587225721862
445 ms 216.198.79.1
36 2026-08-25 12:41 639232576780683689
323 ms 216.198.79.1
35 2026-08-25 12:23 639232566381512620
450 ms 216.198.79.1
34 2026-08-25 12:06 639232556111768563
196 ms 216.198.79.1
33 2026-08-25 11:49 639232545839529039
567 ms 216.198.79.1
32 2026-08-25 11:32 639232535349285207
595 ms 216.198.79.1
31 2026-08-25 11:14 639232524938080723
4 ms 216.198.79.1
30 2026-08-25 10:21 639232492740373468
434 ms 216.198.79.1
29 2026-08-25 10:03 639232482235303141
33 ms 216.198.79.1
28 2026-08-25 09:46 639232471861770303
437 ms 216.198.79.1
27 2026-08-25 09:29 639232461630217327
459 ms 216.198.79.1
26 2026-08-25 09:12 639232451282965990
553 ms 216.198.79.1
25 2026-08-25 08:54 639232440814614938
457 ms 216.198.79.1
24 2026-08-25 08:37 639232430410720425
436 ms 216.198.79.1
23 2026-08-25 08:20 639232420003096185
448 ms 216.198.79.1
22 2026-08-25 08:02 639232409467287444
455 ms 216.198.79.1
21 2026-08-25 07:45 639232399077195997
391 ms 216.198.79.1
20 2026-08-25 07:27 639232388731528337
452 ms 216.198.79.1
19 2026-08-25 07:10 639232378288598612
447 ms 216.198.79.1
18 2026-08-25 06:16 639232346196373643
7 ms 216.198.79.1
17 2026-08-25 05:59 639232336112370741
4 ms 216.198.79.1
16 2026-08-25 05:43 639232326146508970
4 ms 216.198.79.1
15 2026-08-25 05:26 639232316189381720
9 ms 216.198.79.1
14 2026-08-25 05:10 639232306217998913
433 ms 216.198.79.1
13 2026-08-25 04:53 639232296255744174
445 ms 216.198.79.1
12 2026-08-25 04:36 639232286095760789
12 ms 216.198.79.1
11 2026-08-25 04:19 639232276086186273
292 ms 216.198.79.1
10 2026-08-25 04:03 639232265900986425
439 ms 216.198.79.1
9 2026-08-25 03:46 639232255723518075
314 ms 216.198.79.1
8 2026-08-25 03:28 639232245484452890
448 ms 216.198.79.1
7 2026-08-25 03:11 639232235157175331
276 ms 216.198.79.1
6 2026-08-25 02:18 639232203197189095
439 ms 216.198.79.1
5 2026-08-25 02:01 639232192844564298
1813 ms 216.198.79.1
4 2026-08-25 01:44 639232182496008942
2 ms 216.198.79.1
3 2026-08-25 01:26 639232172197053132
144 ms 216.198.79.1
2 2026-08-25 00:33 639232140250307418
434 ms 216.198.79.1
1 2026-08-25 00:16 639232129927860324
441 ms 216.198.79.1