DNS response history for ns.partieglence.com

ns.partieglence.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 29 DNS check records, 29 successful responses, 0 failed responses, and 229 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 ns.partieglence.com.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

229 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:55

All timestamps shown in UTC

Latest Resolved IP on Selected Date

92.42.33.78

Most recently resolved hosting IP on selected date

Successful Responses

29

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 ns.partieglence.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
29 2026-08-25 09:55 639232482235303141
83 ms 92.42.33.78
28 2026-08-25 09:38 639232471861770303
56 ms 92.42.33.78
27 2026-08-25 09:21 639232461630217327
106 ms 92.42.33.78
26 2026-08-25 09:04 639232451282965990
104 ms 92.42.33.78
25 2026-08-25 08:46 639232440814614938
105 ms 92.42.33.78
24 2026-08-25 08:29 639232430410720425
132 ms 92.42.33.78
23 2026-08-25 08:12 639232420003096185
107 ms 92.42.33.78
22 2026-08-25 07:54 639232409467287444
106 ms 92.42.33.78
21 2026-08-25 07:37 639232399077195997
14 ms 92.42.33.78
20 2026-08-25 07:19 639232388731528337
35 ms 92.42.33.78
19 2026-08-25 07:02 639232378288598612
108 ms 92.42.33.78
18 2026-08-25 06:08 639232346196373643
68 ms 92.42.33.78
17 2026-08-25 05:52 639232336112370741
102 ms 92.42.33.78
16 2026-08-25 05:35 639232326146508970
115 ms 92.42.33.78
15 2026-08-25 05:18 639232316189381720
124 ms 92.42.33.78
14 2026-08-25 05:02 639232306217998913
120 ms 92.42.33.78
13 2026-08-25 04:45 639232296255744174
57 ms 92.42.33.78
12 2026-08-25 04:28 639232286095760789
101 ms 92.42.33.78
11 2026-08-25 04:12 639232276086186273
2022 ms 92.42.33.78
10 2026-08-25 03:55 639232265900986425
83 ms 92.42.33.78
9 2026-08-25 03:38 639232255723518075
115 ms 92.42.33.78
8 2026-08-25 03:21 639232245484452890
126 ms 92.42.33.78
7 2026-08-25 03:04 639232235157175331
2068 ms 92.42.33.78
6 2026-08-25 02:10 639232203197189095
105 ms 92.42.33.78
5 2026-08-25 01:53 639232192844564298
98 ms 92.42.33.78
4 2026-08-25 01:36 639232182496008942
99 ms 92.42.33.78
3 2026-08-25 01:18 639232172197053132
112 ms 92.42.33.78
2 2026-08-25 00:25 639232140250307418
101 ms 92.42.33.78
1 2026-08-25 00:08 639232129927860324
70 ms 92.42.33.78