Summary

  • AS43022 gives Seech-Infocom a measurable public routing footprint: RIPEstat saw nine IPv4 prefixes and one IPv6 prefix on 26 August 2026, while the principal IPv4 and IPv6 aggregates checked as RPKI-valid.
  • A signed 2025 protocol found one fixed Zaporizhzhia-to-Dnipro test path compliant on four regulated indicators across 2,000 sessions. It was not a network-wide uptime study and cannot be presented as an SLA.
  • The decisive resilience evidence remains absent: node-level backup power, physically independent paths, incident and restoration records, and demonstrated performance against the provider's repair and recalculation terms.

A route collector can see a prefix while a customer cannot reach the access node that originates the connection. That mismatch is the right place to begin with Seech-Infocom. The company has enough public evidence to show that it operates a network; the same evidence is not enough to show what happens at a home or business when electricity, backhaul or field equipment fails.

The identity chain is unusually clear for a small regional operator. RIPE NCC lists Seech-Infocom Ltd. as the Ukrainian LIR ORG-SL134-RIPE. The RIPE Database assigns AS43022, with the name UA-SEECH, to that organisation. A Ukrainian State Centre of Radio Frequencies protocol and the company's public offer identify the legal entity as ТОВ «СІЧ-ІНФОКОМ», EDRPOU 30001108, operating under the INFOCOM trade name. Shared phone numbers, infocom.ua mailboxes and the company's official website connect the operational and legal records without requiring a same-name guess.

The public routing surface is also concrete. At RIPEstat's 26 August 2026 observation, AS43022 was announced through nine visible IPv4 prefixes covering 8,192 addresses and one visible IPv6 prefix. The IPv4 route 77.93.32.0/19 was RPKI-valid for AS43022 with a maximum length of /24; 2a04:7dc0::/29 was valid with a maximum length of /29. RIPEstat reported visibility from all 327 IPv4 RIS peers in its set and from 184 of 320 IPv6 peers, as well as 21 observed neighbours. Those are control-plane observations, not customer counts or commercial contracts.

The history matters, but only within its boundary. RIPEstat returned successive visibility segments for 77.93.32.0/19 from 5 March 2022 to the 26 August 2026 query end, using a floor of ten full-feed peers. That is evidence of persistent aggregate-route visibility during the observed interval. It does not reveal whether a street cabinet lost power, whether a PON segment remained lit, whether a radio site had fuel, or whether an individual subscriber could pass traffic.

There are signs of deliberate interconnection diversity. The RIPE policy object declares six IPv4 imports accepting any route from AS3255, AS3326, AS35297, AS15895, AS199995 and AS6846, alongside exchange and peer policies. The operator-maintained PeeringDB profile lists four 20,000 Mbps exchange-LAN entries across DTEL-IX and Giganet and a facility association in Kyiv. But a declared policy is not a live BGP session, a listed port is not proof of utilisation, and two names on a diagram are not proof that fibre paths avoid the same duct, building or power source.

Seech-Infocom's own commercial surface fills in the customer proposition. Its site lists residential access at 100, 200, 300 and 500 Mbps, describes FTTB, PON and radio access, and advertises data transmission, Internet, redundancy and round-the-clock technical support for business customers. Its service rules require one day's notice for planned work that may interrupt service. They set a 24-hour target for repairing registered network damage unless the work needs longer, and provide for recalculation when a provider-caused absence lasts more than three working days.

The public offer accepts responsibility for the operability of the provider's own network while excluding the quality of the wider public Internet.

These terms reveal the control surface: the customer must register a fault; the provider distinguishes its network from external segments; cause and duration determine whether a remedy applies. They do not reveal actual mean time to restore, the share of faults closed within 24 hours, how often the longer-work exception is used, or how much recalculation has been paid. A contractual target is an accountability mechanism, not a performance result.

The strongest performance document is also the easiest to overstate. Protocol 23-008, dated 14 April 2025, records 2,000 sessions between client IP 77.93.44.2 in Zaporizhzhia and a test server in Dnipro from 11 April 09:37:54 to 12 April 15:39:11. It recorded 100% successful registrations, no refusal time, all registrations within the 30-second norm, no unsatisfactory upload or download sessions against the regulatory floor of 56 kbit/s, one-way delay from 16.00 to 17.08 milliseconds with a 16.88 millisecond average, 0.02% packet loss and 1.02 milliseconds of jitter. The protocol concluded that the four regulated availability and completeness indicators it assessed met the applicable levels.

That is useful evidence of a specific path over roughly 30 hours. It is not an annual availability measure, not a survey of every access technology, not an outage restoration trial and not proof of node-level power autonomy. The honest conclusion is narrower and more valuable: Seech-Infocom can point to a live public routing surface, valid origin controls, declared interconnection options, published customer remedies and one independently administered test. A resilience claim still needs evidence of the physical and operational system behind them.

The missing evidence is identifiable. The public record does not show shared-risk groups, active upstream status, backup-battery or generator coverage, refill practice, the number and location of access nodes, an incident ledger, customer-impact minutes, restoration distributions, IPv6 availability to end users or the representativeness of the 2025 test line. Nor does it establish customer count, audited capacity or utilisation. These are unknowns, not negative findings.

Selected primary evidence: RIPE NCC member record, RIPE Database AS43022 object, RIPEstat routing status, RIPEstat routing history, published service rules, and 2025 measurement protocol.