Summary

  • RIPE associates PS Processing LLC with an IPv4 range equivalent to three consecutive /24s, an IPv6 /32 and two autonomous systems.
  • In bounded RIPEstat views on 5 September 2026, one /24 was observed from AS201916 and one from AS212213; the status of the third registered /24 is not established by those observations.

The RIPE NCC member entry places PS Processing LLC in Moscow and lists the Russian Federation as its service area. The organisation object identifies ORG-CL264-RIPE as an LIR and records AVSND-MNT among its maintainers. An inverse organisation search links it to 185.59.216.0 through 185.59.218.255, 2a02:6e60::/32, AS201916 and AS212213.

The two aut-num objects carry suggestive labels. AS201916 is AVOSEND-SD; AS212213 is AVOSEND-DL. Both declare policy involving AS20764 and AS57304, while AS212213 also names the AS8631 route server. These are registry declarations, not proof of realised traffic, contracts or separate operating systems. The company’s public offer establishes that PS Processing LLC provides the AVOSEND information-technology service, but does not define what SD and DL mean.

The dated collector view is narrower. RIPEstat recorded one IPv4 /24 and 256 addresses for AS201916, and the same totals for AS212213. Both were visible to all 327 IPv4 RIS peers listed in their responses, and neither view showed IPv6 announcements. The two-week records identify 185.59.216.0/24 from AS201916 and 185.59.217.0/24 from AS212213.

That leaves a reconciliation question around 185.59.218.0/24. The cited view does not show it originating from either named ASN, but silence is not evidence that a block is unused, assignable or commercially available. It may have an unobserved use, a different origin, a reserved purpose or no current route. Public sources do not decide among those possibilities. A capacity claim requires evidence for assignment, authority, routing intention and operational ownership—not subtraction from a registry total.