DNS response history for n2.ripedb.net

n2.ripedb.net 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, 35 successful responses, 1 failed responses, and 178 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 n2.ripedb.net.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

178 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:31

All timestamps shown in UTC

Latest Resolved IP on Selected Date

89.149.5.219

Most recently resolved hosting IP on selected date

Successful Responses

35

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for n2.ripedb.net

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:31 639232576780683689
68 ms 89.149.5.219
35 2026-08-25 12:13 639232566381512620
66 ms 89.149.5.219
34 2026-08-25 11:56 639232556111768563
99 ms 89.149.5.219
33 2026-08-25 11:39 639232545839529039
2059 ms 89.149.5.219
32 2026-08-25 11:22 639232535349285207
112 ms 89.149.5.219
31 2026-08-25 11:04 639232524938080723
69 ms 89.149.5.219
30 2026-08-25 10:11 639232492740373468
71 ms 89.149.5.219
29 2026-08-25 09:53 639232482235303141
76 ms 89.149.5.219
28 2026-08-25 09:36 639232471861770303
59 ms 89.149.5.219
27 2026-08-25 09:19 639232461630217327
53 ms 89.149.5.219
26 2026-08-25 09:02 639232451282965990
68 ms 89.149.5.219
25 2026-08-25 08:44 639232440814614938
89 ms 89.149.5.219
24 2026-08-25 08:27 639232430410720425
40 ms 89.149.5.219
23 2026-08-25 08:10 639232420003096185
119 ms 89.149.5.219
22 2026-08-25 07:52 639232409467287444
38 ms 89.149.5.219
21 2026-08-25 07:35 639232399077195997
45 ms 89.149.5.219
20 2026-08-25 07:17 639232388731528337
48 ms 89.149.5.219
19 2026-08-25 07:00 639232378288598612
77 ms 89.149.5.219
18 2026-08-25 06:06 639232346196373643
73 ms 89.149.5.219
17 2026-08-25 05:50 639232336112370741
78 ms 89.149.5.219
16 2026-08-25 05:33 639232326146508970
74 ms 89.149.5.219
15 2026-08-25 05:16 639232316189381720
41 ms 89.149.5.219
14 2026-08-25 05:00 639232306217998913
-
13 2026-08-25 04:43 639232296255744174
53 ms 89.149.5.219
12 2026-08-25 04:26 639232286095760789
31 ms 89.149.5.219
11 2026-08-25 04:10 639232276086186273
64 ms 89.149.5.219
10 2026-08-25 03:53 639232265900986425
30 ms 89.149.5.219
9 2026-08-25 03:36 639232255723518075
2055 ms 89.149.5.219
8 2026-08-25 03:19 639232245484452890
61 ms 89.149.5.219
7 2026-08-25 03:01 639232235157175331
72 ms 89.149.5.219
6 2026-08-25 02:08 639232203197189095
44 ms 89.149.5.219
5 2026-08-25 01:51 639232192844564298
61 ms 89.149.5.219
4 2026-08-25 01:34 639232182496008942
87 ms 89.149.5.219
3 2026-08-25 01:16 639232172197053132
43 ms 89.149.5.219
2 2026-08-25 00:23 639232140250307418
44 ms 89.149.5.219
1 2026-08-25 00:06 639232129927860324
62 ms 89.149.5.219