MADISON
Madison Communications, Inc.
LEI
984500CEC3E53M14HT75
Registered name
MADISON
Jurisdiction
Ultimate parent
No parent on file in GLEIF
Cluster stats
| Netblocks | 4 |
| All fragments | 43 blocks across 15 clusters |
| Cluster ID | 193382893 |
| Registry | PEERINGDB |
| Owner jurisdiction | US-WI |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Legal identity | LEI 984500CEC3E53M14HT75 |
| Shared handles | clustered on 4 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 208.115.136.78/32 | Madison Communications, Inc. | PEERINGDB | ASSIGNED | ● high |
| 2001:504:0:4:0:1:8596:1/128 | Madison Communications, Inc. | PEERINGDB | ASSIGNED | ● high |
| 2a00:2381:90f::/48 | MADISON | RIPE | AGGREGATED-BY-LIR | ● low |
| 2a00:2381:90f::/56 | MADISON | RIPE | ASSIGNED | ● low |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
50.0%
of checked blocks have valid RPKI ROA coverage
(2 of 4)
Possible discrepancies (2)
These blocks are registered to Madison Communications, Inc. but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.
| 2a00:2381:90f::/48 /48 | authorized for AS2856 — British Telecommunications PLC |
| 2a00:2381:90f::/56 /56 | authorized for AS2856 — British Telecommunications PLC |
NIC Handles
AS18596
BTNET-MNT
DUMY-RIPE
DUMY-RIPE