Lax Matthew
BGP inherited
Cluster stats
| Netblocks | 2 |
| All fragments | 14 blocks across 11 clusters |
| Cluster ID | 192810326 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 8 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (2)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 51.89.187.68/30 | Lax Matthew | RIPE | LEGACY | ● high |
| 43.255.116.0/24 | LAX-US | APNIC | ALLOCATED NON-PORTABLE | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(2 of 2)
Possible discrepancies (1)
These blocks are registered to Lax Matthew 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.
| 43.255.116.0/24 /24 | authorized for AS21859 — Zenlayer Inc |
NIC Handles
DUMY-RIPE
DUMY-RIPE
MAINT-LAX-US
ORG-LM261-RIPE
OVH-MNT
SUI1-AP
SUI1-AP
SUI1-AP