AS50877 AIRBEAM-AS Airbeam S.r.l.
🇮🇹Org handle: ORG-AS558-RIPE
AIRBEAM
RIPE NCCallocated
Announced Prefixes (BGP)
5total
4 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)6,400
Announced (BGP)6,144
IPv6 Addresses
Allocated (RIR)6.3×10²⁹
Announced (BGP)6.3×10²⁹
Announced Prefixes
(BGP)5|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-10 | |
| Valid | RIPE | 2026-10-10 | |
| Valid | RIPE | 2026-10-10 | |
| Valid | RIPE | 2026-10-10 | |
| Valid | RIPE | 2026-10-10 |
Allocated Prefixes
(RIR)6Prefix | Country | RIR | Status |
|---|---|---|---|
| 159.255.128.0/21 | 🇮🇹 IT | RIPENCC | allocated |
| 176.32.56.0/21 | 🇮🇹 IT | RIPENCC | allocated |
| 185.112.196.0/22 | 🇮🇹 IT | RIPENCC | allocated |
| 185.182.208.0/22 | 🇮🇹 IT | RIPENCC | allocated |
| 185.182.209.0/24 | 🇮🇹 IT | RIPE | assigned |
| 2a0a:f980::/29 | 🇮🇹 IT | RIPENCC | allocated |
All 5 announced prefixes of AS50877 →
BGP Neighbours
(seen in AS paths)Upstreams (2)
Networks AS50877 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (5)
Networks whose own prefixes AS50877 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 AS50877 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/50877Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/50877" | jq