DNS response history for ns2.rwebcorp.com

ns2.rwebcorp.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-28. For this date, NameServerHistory found 36 DNS check records, 36 successful responses, 0 failed responses, and 414 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.rwebcorp.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

414 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-28 15:08

All timestamps shown in UTC

Latest Resolved IP on Selected Date

168.144.34.111

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.rwebcorp.com

Showing DNS history for 2026-08-28 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-28 15:08 639235258803654519
324 ms 168.144.34.111
35 2026-08-28 14:50 639235248596087996
320 ms 168.144.34.111
34 2026-08-28 14:33 639235238225955920
323 ms 168.144.34.111
33 2026-08-28 14:16 639235227727862105
326 ms 168.144.34.111
32 2026-08-28 13:22 639235195230848570
327 ms 168.144.34.111
31 2026-08-28 13:05 639235184840503274
325 ms 168.144.34.111
30 2026-08-28 12:47 639235174453894956
312 ms 168.144.34.111
29 2026-08-28 12:29 639235163898672622
337 ms 168.144.34.111
28 2026-08-28 11:37 639235132147470568
324 ms 168.144.34.111
27 2026-08-28 11:19 639235121907744088
319 ms 168.144.34.111
26 2026-08-28 11:02 639235111428014262
322 ms 168.144.34.111
25 2026-08-28 10:44 639235100921813626
319 ms 168.144.34.111
24 2026-08-28 09:51 639235068670703481
336 ms 168.144.34.111
23 2026-08-28 09:34 639235058337459445
320 ms 168.144.34.111
22 2026-08-28 09:16 639235047825109146
320 ms 168.144.34.111
21 2026-08-28 08:59 639235037383229033
2316 ms 168.144.34.111
20 2026-08-28 08:06 639235005619242711
2187 ms 168.144.34.111
19 2026-08-28 07:49 639234995310346584
318 ms 168.144.34.111
18 2026-08-28 07:31 639234984946548933
323 ms 168.144.34.111
17 2026-08-28 07:14 639234974608077290
330 ms 168.144.34.111
16 2026-08-28 06:21 639234942529845595
321 ms 168.144.34.111
15 2026-08-28 06:04 639234932259126627
342 ms 168.144.34.111
14 2026-08-28 05:46 639234921916735988
330 ms 168.144.34.111
13 2026-08-28 05:29 639234911470038027
325 ms 168.144.34.111
12 2026-08-28 04:36 639234879588411654
315 ms 168.144.34.111
11 2026-08-28 04:19 639234869341589104
319 ms 168.144.34.111
10 2026-08-28 04:01 639234859012216675
324 ms 168.144.34.111
9 2026-08-28 03:44 639234848695364934
320 ms 168.144.34.111
8 2026-08-28 02:51 639234816952458162
388 ms 168.144.34.111
7 2026-08-28 02:34 639234806773081598
6 ms 168.144.34.111
6 2026-08-28 02:17 639234796382955255
317 ms 168.144.34.111
5 2026-08-28 02:00 639234786015782563
3 ms 168.144.34.111
4 2026-08-28 01:06 639234753811917646
316 ms 168.144.34.111
3 2026-08-28 00:49 639234743739767811
315 ms 168.144.34.111
2 2026-08-28 00:32 639234733372362811
316 ms 168.144.34.111
1 2026-08-28 00:15 639234723048550337
318 ms 168.144.34.111