AS200276 BEENET-AS ASP Co d.o.o
🇲🇪Org handle: ORG-ACD2-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
2total
2 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)1,024
Announced (BGP)512
IPv6 Addresses
Allocated (RIR)3.1×10²⁹
Announced (BGP)0
Announced Prefixes
(BGP)2|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-10 | |
| Valid | RIPE | 2026-10-10 |
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 81.28.248.0/22 | 🇲🇪 ME | RIPENCC | allocated |
| 2a10:100::/30 | 🇲🇪 ME | RIPENCC | allocated |
All 2 announced prefixes of AS200276 →
BGP Neighbours
(seen in AS paths)Upstreams (2)
Networks AS200276 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (3)
Networks whose own prefixes AS200276 passes on: usually its customers.
Other adjacent networks (1)
Adjacent to AS200276 in the transit part of AS paths: peers, providers or customers.
- AS43940MTEL Drustvo Za Telekomunikacije "MTEL" DOO1
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 AS200276 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/200276Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/200276" | jq