DNS response history for ns2.re-fresh.ws

ns2.re-fresh.ws 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-27. For this date, NameServerHistory found 35 DNS check records, 35 successful responses, 0 failed responses, and 425 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.re-fresh.ws.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

425 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 11:16

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.127.42.3

Most recently resolved hosting IP on selected date

Successful Responses

35

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.re-fresh.ws

Showing DNS history for 2026-08-27 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
35 2026-08-27 11:16 639234253963286387
271 ms 103.127.42.3
34 2026-08-27 10:59 639234243654907465
271 ms 103.127.42.3
33 2026-08-27 10:42 639234233269654413
547 ms 103.127.42.3
32 2026-08-27 10:25 639234222943951923
278 ms 103.127.42.3
31 2026-08-27 10:07 639234212558002823
271 ms 103.127.42.3
30 2026-08-27 09:50 639234202117531850
277 ms 103.127.42.3
29 2026-08-27 09:33 639234191649612722
559 ms 103.127.42.3
28 2026-08-27 09:15 639234181105879568
547 ms 103.127.42.3
27 2026-08-27 08:58 639234170713214496
278 ms 103.127.42.3
26 2026-08-27 08:40 639234160341037652
278 ms 103.127.42.3
25 2026-08-27 08:23 639234149799404224
559 ms 103.127.42.3
24 2026-08-27 08:05 639234139553286469
555 ms 103.127.42.3
23 2026-08-27 07:12 639234107183588293
2338 ms 103.127.42.3
22 2026-08-27 06:54 639234096905435724
2298 ms 103.127.42.3
21 2026-08-27 06:37 639234086579410775
279 ms 103.127.42.3
20 2026-08-27 06:20 639234076291157956
284 ms 103.127.42.3
19 2026-08-27 06:03 639234065981939454
4 ms 103.127.42.3
18 2026-08-27 05:46 639234055548642997
4 ms 103.127.42.3
17 2026-08-27 05:28 639234045267979603
546 ms 103.127.42.3
16 2026-08-27 05:11 639234034999717463
552 ms 103.127.42.3
15 2026-08-27 04:54 639234024739225358
275 ms 103.127.42.3
14 2026-08-27 04:37 639234014311170162
276 ms 103.127.42.3
13 2026-08-27 04:19 639234003806017640
567 ms 103.127.42.3
12 2026-08-27 04:02 639233993356203030
554 ms 103.127.42.3
11 2026-08-27 03:09 639233961301716608
280 ms 103.127.42.3
10 2026-08-27 02:51 639233950834200647
269 ms 103.127.42.3
9 2026-08-27 02:34 639233940431849026
549 ms 103.127.42.3
8 2026-08-27 02:17 639233930110596398
7 ms 103.127.42.3
7 2026-08-27 01:59 639233919705434540
285 ms 103.127.42.3
6 2026-08-27 01:42 639233909452807845
3 ms 103.127.42.3
5 2026-08-27 01:25 639233899096420820
2 ms 103.127.42.3
4 2026-08-27 01:08 639233888707824939
3 ms 103.127.42.3
3 2026-08-27 00:50 639233878461203802
272 ms 103.127.42.3
2 2026-08-27 00:33 639233868060868209
271 ms 103.127.42.3
1 2026-08-27 00:16 639233857450922991
274 ms 103.127.42.3