Summary

  • The registry view records AS216429 as held by NETMAX-BRO-LTD inside the RIPE NCC-assigned block 215452–216475, and records the AS as announced (RIPEstat AS overview).
  • Three prefixes were announced as of 16 October 2026: 154.9.155.0/24 and 2a07:5680:4::/48 since 2 October, and 79.176.42.0/24 since 6 October (RIPEstat announced prefixes).
  • The routing view shows two IPv4 prefixes, 512 addresses, and one IPv6 /48 at full RIS peer visibility — but only one observed neighbour (RIPEstat routing status).
  • That neighbour is AS212616; a third-party page names it K.M.A ADVANCED TECHNOLOGIES LTD and renders a sponsoring-organisation handle (bgp.tools AS216429).

The briefing separates three questions that are routinely collapsed into one: what is recorded, who controls the announcement, and what is actually carried. On the evidence available on 16 October 2026, the first question is answered, the second is partly answered, and the third is not answered at all.

The record link

The AS-overview view for AS216429 returns a holder string of NETMAX-BRO-LTD NET MAX BRO LTD and places the number inside the block 215452–216475, described in the same payload as assigned by RIPE NCC. The same response records the AS as announced (RIPEstat AS overview).

That is a dated, checkable statement about a registration. It establishes that the registry association exists and when it was observed. It does not establish that the named party is a registered legal entity, a trading brand or a label attached to somebody else's infrastructure. Nothing in this evidence set resolves that, and the company card in the directory carries its own open questions — legal-entity country, current services, visible assets and responsible contacts all remain unfilled.

The use link, as far as announcement goes

Announcement is the closest thing this evidence set has to a demonstrated use. Three prefixes appear in the announced-prefix view for AS216429 on 16 October 2026: 154.9.155.0/24 and 2a07:5680:4::/48, both with a start time of 2 October 2026, and 79.176.42.0/24, with a start time of 6 October 2026 (RIPEstat announced prefixes).

Two observations follow. First, the IPv4 space totals 512 addresses across two /24s — small, and precisely the kind of footprint that is rented rather than built. Second, the announcements are recent relative to the registry entry: the holder name and the AS have a longer history than these particular prefixes. Prefix provenance — which allocation each announced prefix is drawn from — was not established from a registry object in this evidence set, so it should not be asserted.

Visibility is not topology

The routing-status view adds a measurement that reads, at first glance, like strength. Both IPv4 prefixes and the single IPv6 /48 are seen by every reporting peer in the RIS set: 327 of 327 IPv4 peers and 316 of 316 IPv6 peers (RIPEstat routing status).

Visibility of that kind means the announcements are propagated widely and are not being filtered out anywhere in the observed collector population. It says nothing about how the announcing network is built, who its customers are, or whether traffic in the other direction exists. It is worth being explicit about what full visibility does not measure: it is a count of collectors that can see a route, not a count of parties that exchange traffic over it.

The single-neighbour result

The most consequential number in this evidence set is one. The neighbour view for AS216429 reports a single distinct observed neighbour, AS212616, with the relationship recorded as left and a power value of 614; the same payload shows peer counts of 664 on IPv4 and 338 on IPv6 for that neighbour (RIPEstat neighbour view).

The same payload carries an earliest_time field of 2019-08-28, which is the earliest point in the measurement record for this relationship — not a founding date for the network, and not a date on which this AS began operating.

One neighbour means one path in and out of the announced address space, as far as public measurement goes. A network in that position has no local redundancy: whatever happens to that single interconnection is, on this evidence, the whole of AS216429's connectivity. Two readings are consistent with the observation. Either the topology genuinely is single-homed, or the collector set cannot see the other relationships — for example where an upstream does not advertise a path to the public RIS peer population. This evidence set cannot distinguish between them, and the difference matters a great deal to anyone assessing resilience.

The operating-layer lead and its limit

The one piece of evidence that reaches past the registry layer is a third-party rendering. The bgp.tools page for AS216429 displays a sponsoring-organisation handle, ORG-KTCL1-RIPE, and lists a single upstream, AS212616, named K.M.A ADVANCED TECHNOLOGIES LTD; the summary text on the same page states that the AS originates two IPv4 prefixes and one IPv6 prefix as of October 2026 (bgp.tools AS216429).

The same organisation handle appears both in the sponsor field and in the upstream listing. That convergence is a lead worth following, not a settled finding — it is a third-party rendering rather than a registry object, and this evidence set did not read the underlying organisation object. What the lead suggests is that reachability for this address space may be delivered by the sponsoring party rather than by the named holder itself. That is a statement about the measurement layer, not about ownership, contracts or intent.

What this does not establish

The gap between the three links is the finding. The registry association is established. The announcement set and its start dates are established. The visibility count is established. The single observed neighbour is established. Everything beyond that — whether the announced space carries service traffic, whether the holder exercises independent control over routing policy, whether the single neighbour reflects a real single-homed design, and whether the operating layer changed since the previous reading on 27 September 2026 — remains open.

The absence of traffic evidence is not evidence that no traffic exists. It means that the public measurements assembled here measure propagation, not carriage, and that the honest reading of AS216429 on 16 October 2026 is of a registry-linked identity whose announcements are visible everywhere and whose interconnection is visible in exactly one place.

Readers who want the registry-layer background — the registration timeline, the authorisation question and the earlier state of the same case — will find it in the previous case file on this subject in the directory: NETMAX-BRO-LTD in the BTW directory.