Summary

  • RIPEstat lists AS12843 inside block 12288-13311 of the IANA 16-bit AS Numbers Registry and AS215996 inside block 215452-216475 of the IANA 32-bit registry, both under the holder TELEMAXX TelemaxX Telekommunikation GmbH and both announced at the 2026-11-17T08:00:00 query time.
  • 215,996 is larger than 65,535, the largest value a 16-bit field can hold, so the second number cannot have been issued from the pool that holds the first. Prefix counts, registration dates, contacts and the operator's own service list were not in the material read, so what the second number is for remains open.

The whole record, one line per number

The response for the lower number is short enough to quote in full. It returns resource 12843, a containing block of 12288-13311 described as Assigned by RIPE NCC and named the IANA 16-bit Autonomous System (AS) Numbers Registry, the holder string TELEMAXX TelemaxX Telekommunikation GmbH, and announced true, all pinned to a query time of 2026-11-17T08:00:00 (https://stat.ripe.net/data/as-overview/data.json?resource=AS12843).

The response for the higher number repeats that shape and changes three values: resource 215996, containing block 215452-216475, and a registry named the IANA 32-bit Autonomous System (AS) Numbers Registry. The holder string is identical. The announced flag is identical. The query time is identical (https://stat.ripe.net/data/as-overview/data.json?resource=AS215996).

That is the entire evidential base of this briefing, and it is worth being blunt about how little it is. No prefix list. No allocation date. No administrative or technical contact. No statement of what the operator sells, owns or connects. What the two documents do carry is a structural fact that cannot be argued away, and structural facts of that kind are precisely what a reader tracking a regional carrier is usually missing.

The arithmetic does the arguing

Both containing blocks are 1,024 numbers wide: 12,288 through 13,311, and 215,452 through 216,475. Each sits in a registry assigned by RIPE NCC. The difference that matters is the name of the registry, because the name is the constraint. A 16-bit field tops out at 65,535. The second number is 215,996, which is 150,461 above that ceiling.

No policy history, no allocation practice and no second source are needed to draw the conclusion. A number larger than the largest representable 16-bit value cannot be a member of a 16-bit block. The second autonomous system was therefore not carved from the same finite space as the first. It came from the newer one, the one that exists because the older count ran out.

This is where a careless reading goes wrong. Two AS numbers under one holder look like a bookkeeping artifact, two labels on the same machine, and most coverage of small carriers stops there. The registry says otherwise: these are two distinct identities drawn from two distinct pools, and the second one could only have been obtained by asking for it.

What announced actually means

Both records report announced true, which is a statement about visibility in the routing system at 08:00 on 17 November 2026, not a statement about size, traffic, address family or ownership of the address space being originated. It says the number was in use. It does not say how much of anything.

The discipline follows directly. Announced true confirms that neither number is a dormant reservation, which is genuinely useful, because a dormant second number would have made the pool split a filing rather than an operating fact. It does not license a single sentence about prefix counts, customer volumes or network scale. Anyone who wants those numbers has to read a different record.

Two identities are a decision

An autonomous system number is how a network tells the rest of the internet that a set of routes belongs to it. A carrier that holds one has one such statement to make. A carrier that holds two has two, and running the second is not free: it has to be carried in filters, in routing policy, in contact records and in whatever documentation the operator publishes for peers and customers.

So why would a regional operator add a newer number when an older one already works? The candidate explanations are mundane and mutually exclusive in their consequences. The older identity's address space could be tight enough that a new block needs its own origin. A customer or service class could need to be kept separable, so that it can be moved, sold or shut without disturbing the rest. A network absorbed from somewhere else could still be originating under an identity that was never folded into the first. Or the second number could simply be a provisioning convention, with no commercial meaning at all.

The documents read on 17 November 2026 do not choose between those stories. Each one implies a different thing to watch and a different failure mode, which is exactly why the choice should not be made by assertion in a briefing.

What would settle it

Four records would close the question, and none of them was obtained in the material reviewed on 17 November 2026. The announced-prefix list for each number would show whether AS215996 originates routes of its own or merely repeats the older identity. The RIPE NCC registration record would give the date each number was assigned, which orders the decision in time. The administrative and technical contacts would show whether one team runs both or whether the second identity belongs to a different part of the business.

And the operator's own published service description would say what it sells, which is the fact every commercial reading of a registry entry ultimately leans on.

Stating that plainly is a statement about the documents, not about the company. A record that was not queried does not become empty, and a service page that was not read does not become a page without services. The two facts that were read stand on their own; the rest is a work list.

BTW's directory entry for the operator records the entity and the number resources attributed to it (https://btw.media/en/directory/telemaxx-telemaxx-telekommunikation-gmbh). The registry records are the primary documents behind that attribution, and they are the only two things this briefing is willing to assert.

Why the cheapest number matters

An analyst waiting for a revenue line to reveal a carrier's structure will wait through several reporting cycles and then receive a number that has been aggregated, allocated and smoothed beyond recognition. The registry is the opposite instrument. It is cheap, it is dated, and it changes when an operator makes a decision rather than when an accountant describes one. A second origination identity is the earliest durable public trace of a commercial move that will show up in an income statement only long after the fact, if it shows up at all.

The counter-discipline is just as important. Two identities are not two businesses. They can be one network with a second label, and the pool split proves only that the second number was deliberately taken. Identity count is a signal to investigate, not a valuation. The correct posture is neither the breathless one that reads two AS numbers as a hidden second company, nor the dismissive one that reads them as paperwork. It is the boring one: a deliberate decision was made, the registry kept the receipt, and the receipt does not say why.

What remains is a small, hard fact about a German carrier, established from primary registry data and nothing else: TELEMAXX TelemaxX Telekommunikation GmbH holds two live autonomous system numbers, one of which could not have come from the pool that holds the other. The market rarely bothers to look that up. The next record that shows what the newer number carries will turn this from a structural observation into a commercial one, and it will be available before the financial statements catch up.