AS14868 Ligga Telecomunicacoes S.A.

The reverse names cite an RFC number to say an address is shared, and the netnames are nothing but ticket numbers.

What it's used for

• A Brazilian broadband operator. 86,016 addresses across 20 IPv4 prefixes plus three IPv6 prefixes, with 91 observed BGP neighbours.

Notable

• Every netname is a bare number: 227969, 3691, 136211, 168917, 24260, 506382, 506383, 506387, 506388, 245934.
• All of them register to LIGGA SERVICOS EM TELECOM, some with S.A. appended and some without.
• Ten of eighteen sampled addresses returned a name, under two domains: liggatelecom.com.br and copelfibra.com.br.
• The names mark the line type as static or dynamic, and some insert rfc6598 before it.
• The three IPv6 prefixes are 2001:1284::/32, 2804:182c::/32 and 2804:39e8::/32.
• The registry lookup for 177.220.128.0/18 failed.

Interesting

• rfc6598 names the document that reserved a range for carrier-grade address sharing. Putting it in a hostname tells anyone who looks that the customer behind the address does not have it to themselves: the most precise way to say so, and the least likely to be understood.
• Netnames made only of digits are registry ticket numbers, kept because they are unique rather than because they mean anything. The registry identifies these blocks perfectly and describes them not at all.
• Two domains answer across the same address space, one naming a different brand. The reverse zones were migrated block by block and the migration is unfinished.
• Ninety-one neighbours against 86,016 addresses is far more adjacency than the address count suggests, which is what happens when peering locally beats buying transit.