DNS response history for ns2.poms.work

ns2.poms.work 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, 36 successful responses, 0 failed responses, and 275 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.poms.work.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

275 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:38

All timestamps shown in UTC

Latest Resolved IP on Selected Date

209.182.232.142

Most recently resolved hosting IP on selected date

Successful Responses

36

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.poms.work

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:38 639232576780683689
136 ms 209.182.232.142
35 2026-08-25 12:20 639232566381512620
264 ms 209.182.232.142
34 2026-08-25 12:03 639232556111768563
282 ms 209.182.232.142
33 2026-08-25 11:46 639232545839529039
9 ms 209.182.232.142
32 2026-08-25 11:29 639232535349285207
270 ms 209.182.232.142
31 2026-08-25 11:11 639232524938080723
277 ms 209.182.232.142
30 2026-08-25 10:17 639232492740373468
205 ms 209.182.232.142
29 2026-08-25 10:00 639232482235303141
140 ms 209.182.232.142
28 2026-08-25 09:43 639232471861770303
282 ms 209.182.232.142
27 2026-08-25 09:26 639232461630217327
307 ms 209.182.232.142
26 2026-08-25 09:08 639232451282965990
279 ms 209.182.232.142
25 2026-08-25 08:51 639232440814614938
132 ms 209.182.232.142
24 2026-08-25 08:34 639232430410720425
258 ms 209.182.232.142
23 2026-08-25 08:16 639232420003096185
165 ms 209.182.232.142
22 2026-08-25 07:59 639232409467287444
616 ms 209.182.232.142
21 2026-08-25 07:41 639232399077195997
131 ms 209.182.232.142
20 2026-08-25 07:24 639232388731528337
267 ms 209.182.232.142
19 2026-08-25 07:07 639232378288598612
128 ms 209.182.232.142
18 2026-08-25 06:13 639232346196373643
40 ms 209.182.232.142
17 2026-08-25 05:56 639232336112370741
277 ms 209.182.232.142
16 2026-08-25 05:40 639232326146508970
2279 ms 209.182.232.142
15 2026-08-25 05:23 639232316189381720
258 ms 209.182.232.142
14 2026-08-25 05:07 639232306217998913
146 ms 209.182.232.142
13 2026-08-25 04:50 639232296255744174
273 ms 209.182.232.142
12 2026-08-25 04:33 639232286095760789
278 ms 209.182.232.142
11 2026-08-25 04:16 639232276086186273
250 ms 209.182.232.142
10 2026-08-25 03:59 639232265900986425
278 ms 209.182.232.142
9 2026-08-25 03:42 639232255723518075
260 ms 209.182.232.142
8 2026-08-25 03:25 639232245484452890
140 ms 209.182.232.142
7 2026-08-25 03:08 639232235157175331
248 ms 209.182.232.142
6 2026-08-25 02:15 639232203197189095
204 ms 209.182.232.142
5 2026-08-25 01:58 639232192844564298
125 ms 209.182.232.142
4 2026-08-25 01:40 639232182496008942
127 ms 209.182.232.142
3 2026-08-25 01:23 639232172197053132
255 ms 209.182.232.142
2 2026-08-25 00:30 639232140250307418
7 ms 209.182.232.142
1 2026-08-25 00:13 639232129927860324
308 ms 209.182.232.142