DNS response history for dns30.remly.com

dns30.remly.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 36 DNS check records, 36 successful responses, 0 failed responses, and 299 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 dns30.remly.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

299 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

198.235.132.98

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 dns30.remly.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
36 2026-08-25 12:31 639232576780683689
19 ms 198.235.132.98
35 2026-08-25 12:14 639232566381512620
58 ms 198.235.132.98
34 2026-08-25 11:57 639232556111768563
18 ms 198.235.132.98
33 2026-08-25 11:40 639232545839529039
15 ms 198.235.132.98
32 2026-08-25 11:22 639232535349285207
22 ms 198.235.132.98
31 2026-08-25 11:05 639232524938080723
2048 ms 198.235.132.98
30 2026-08-25 10:11 639232492740373468
13 ms 198.235.132.98
29 2026-08-25 09:54 639232482235303141
37 ms 198.235.132.98
28 2026-08-25 09:36 639232471861770303
14 ms 198.235.132.98
27 2026-08-25 09:19 639232461630217327
7 ms 198.235.132.98
26 2026-08-25 09:02 639232451282965990
27 ms 198.235.132.98
25 2026-08-25 08:44 639232440814614938
57 ms 198.235.132.98
24 2026-08-25 08:27 639232430410720425
2027 ms 198.235.132.98
23 2026-08-25 08:10 639232420003096185
41 ms 198.235.132.98
22 2026-08-25 07:52 639232409467287444
8 ms 198.235.132.98
21 2026-08-25 07:35 639232399077195997
6 ms 198.235.132.98
20 2026-08-25 07:18 639232388731528337
7 ms 198.235.132.98
19 2026-08-25 07:00 639232378288598612
25 ms 198.235.132.98
18 2026-08-25 06:07 639232346196373643
4 ms 198.235.132.98
17 2026-08-25 05:50 639232336112370741
4 ms 198.235.132.98
16 2026-08-25 05:33 639232326146508970
2017 ms 198.235.132.98
15 2026-08-25 05:17 639232316189381720
4 ms 198.235.132.98
14 2026-08-25 05:00 639232306217998913
90 ms 198.235.132.98
13 2026-08-25 04:44 639232296255744174
10 ms 198.235.132.98
12 2026-08-25 04:27 639232286095760789
17 ms 198.235.132.98
11 2026-08-25 04:10 639232276086186273
33 ms 198.235.132.98
10 2026-08-25 03:53 639232265900986425
20 ms 198.235.132.98
9 2026-08-25 03:36 639232255723518075
2043 ms 198.235.132.98
8 2026-08-25 03:19 639232245484452890
2020 ms 198.235.132.98
7 2026-08-25 03:02 639232235157175331
4 ms 198.235.132.98
6 2026-08-25 02:08 639232203197189095
4 ms 198.235.132.98
5 2026-08-25 01:51 639232192844564298
9 ms 198.235.132.98
4 2026-08-25 01:34 639232182496008942
5 ms 198.235.132.98
3 2026-08-25 01:17 639232172197053132
5 ms 198.235.132.98
2 2026-08-25 00:24 639232140250307418
5 ms 198.235.132.98
1 2026-08-25 00:06 639232129927860324
7 ms 198.235.132.98