Autonomous system
AS14532 CBOSS
Unclassified ARIN
Summary
CBOSS
hosting business infrastructure
Five IPv6 announcements and a single upstream to carry all of them.
What it's used for
- A payments and hosting company's network. 1,024 IPv4 addresses across three prefixes, five IPv6 prefixes, and one observed BGP neighbour.
Notable
- The IPv6 blocks come from two unrelated ranges: three scattered end-site blocks including
2605:3380:4301::/48, plus2607:abc0::/47and2607:abc0:2::/48from a second range. - Those last two overlap in coverage, with the larger announcement spanning two blocks and the smaller sitting immediately beyond it.
- All three IPv4 blocks carry the netname
CBOSS-IPV4-1, which names the protocol and implies a companion record. - Nine addresses were queried for reverse DNS and none returned a name.
Interesting
- Announcing three consecutive end-site blocks as one larger prefix and a separate smaller one is a choice, not a necessity. Combining all three into a single announcement would need the run to start on the right boundary, and it does not, so the routing table carries two entries where the address space suggests one.
- Five IPv6 announcements against three IPv4 blocks is an unusual balance for a network this size, and the scattered end-site blocks in the first range suggest space collected one request at a time rather than allocated in a plan.
- One observed neighbour carrying eight announcements is the thinnest ratio of upstreams to prefixes in this range, and it means a single carrier relationship decides whether any of it is reachable.
- The netname naming a protocol is a small piece of foresight from an operator that expected to hold both kinds of space, which the IPv6 side confirms.
This description is AI-generated, best-effort context — not authoritative, and provided without any guarantee of accuracy. Source, and how to suggest an edit.
Interconnection
Peering at a glance
Internet exchanges
No exchange port on file. Many exchanges publish no participant list, so this is not proof of absence.
Transit providers
1 upstream, 0 downstream and 2 adjacent networks observed; most-used upstreams first.
| AS | Network | Paths seen |
|---|---|---|
| AS12025 | Iron Mountain Data Center | 430 |
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-21, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 3 prefixes · 1.02K addresses IPv6 5 prefixes
| Country | Name | Prefixes |
|---|---|---|
| US | United States of America | 8 |
Registry
Allocation record
- Registry
- ARIN
- Handle
AS14532- Registry name
- CBOSS
- Registrant
- CBOSS INC
- Abuse contact
- ipmgmt@cboss.com
- Registered
- 1999-12-30
- Last changed
- 2020-04-02
- Allocation
- assigned
Routing security
RPKI and IRR
- RPKI
- 70% valid · 7 valid, 3 with no ROA
- ROAs
- 2 authorising AS14532
- ASPA
- no ASPA record
- IRR
- 70% registered · 7 of 10 announcements
- Route objects
- 5 naming AS14532
Reputation
Classification and threat
Unclassified Not in the curated lists. Most of the ~80,000 allocated ASNs are not.
Spamhaus DROP
Not on ASN-DROP The network as a whole is not listed.
No DROP prefixes None of its announced space is on the DROP prefix list.
Spamhaus DROP ("Don't Route Or Peer") lists space and networks run by, or hijacked for, spam and cybercrime operations: 442 networks and 1,779 prefixes, as published 2026-10-22. A short, high-confidence list, so a match is worth taking seriously, and absence from it says little on its own.
FBI IC3
No IC3 indicators Nothing from the FBI IC3 feed.
IC3 threat data is alpha. Absence of an indicator is not evidence of good behaviour, only of absence from this one feed.
Elsewhere