AS41477 LMAX LMAX Limited
🇬🇧Org handle: ORG-LL142-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
7total
7 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)2,048
Announced (BGP)4,608
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Announced Prefixes
(BGP)7|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | APNIC | 2026-10-11 | |
| Valid | APNIC | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 91.215.164.0/22 | 🇬🇧 GB | RIPENCC | assigned |
| 103.219.172.0/22 | 🇭🇰 HK | APNIC | assigned |
All 7 announced prefixes of AS41477 →
BGP Neighbours
(seen in AS paths)Upstreams (3)
Networks AS41477 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (3)
Networks whose own prefixes AS41477 passes on: usually its customers.
ASPA
No ASPA
Abuse Contact
External Links
Learn more
- What is an ASN?Autonomous systems, ASN ranges and how they are assigned
- RPKI and route origin validationWhat the RPKI badges on the prefix list mean
- ASPA explainedWhy AS41477 should publish an ASPA object
- IPv4 transfers in the RIPE NCC regionMonthly volume and the latest registry transfers
- ASN data in AI agents and SIEMMCP server and API integrations
API
Open https://api.ipctl.io/v1/asn/41477Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/41477" | jq