Summary

  • RIPE’s organisation record, captured on 1 September 2026, identifies Pishgaman Ofogh Barkhat LLC as an Iranian LIR and records a registration number, Isfahan address and abuse-contact role.
  • Two RIPEstat queries captured on 3 September 2026 for 109.70.73.0/24 returned HTTP 400 because those endpoints require an ASN rather than a prefix. They provide no announcement or RPKI evidence and support no operational conclusion.

The useful starting point is modest. In the 1 September 2026 source capture, RIPE’s ORG-POBL10-RIPE record names Pishgaman Ofogh Barkhat LLC, gives country IR, registration number 14012129894 // 73685, and lists an Isfahan address. It also records an abuse-contact role. Those are point-in-time public registry facts: they establish a registry and contact surface for the listed organisation, not legal or operational accountability.

In the same 1 September source capture, RIPE’s prefix record links 109.70.73.0/24 to that organisation and gives its route object origin as AS60781. The captured AS60781 object has a different organisation selector, ORG-OB3-RIPE, and the name LEASEWEB-NL-AMS-01. That is a documented registry boundary at the capture time, not evidence of a particular hosting, transit or contractual arrangement.

They do not establish a retail service catalogue, a customer base, an outage record, a transit arrangement, or a response-time promise. The distinction matters most when a buyer wants a locality assurance. “Registered locally” may describe the allocation holder while the parties controlling route origin, hosting operation, resolver selection, physical access and incident response remain unknown and may differ.

On 3 September 2026, RIPEstat announced-prefix and RPKI-validation requests for 109.70.73.0/24 each returned HTTP 400: those endpoints rejected a prefix because they require an ASN. These failed queries are not observations of routing or RPKI state and must not be translated into “unrouted”, “unsafe”, or “down”. A responsible assessment records the failed method and requests valid current routing, authorisation and operating-contact evidence from the parties involved.

Sources

RIPE organisation record; RIPE prefix and route record; RIPE autonomous-system record; RIPEstat announced-prefixes request; RIPEstat RPKI-validation request.