AS202634 demabg Petar Petrov
🇧🇬Org handle: ORG-DA748-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
3total
1 IPv42 IPv6
IPv4 Addresses
Allocated (RIR)256
Announced (BGP)256
IPv6 Addresses
Allocated (RIR)1.2×10³⁰
Announced (BGP)1.2×10³⁰
Announced Prefixes
(BGP)3|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 212.5.51.0/24 | 🇧🇬 BG | RIPE | assigned |
| 2a0b:8dc0::/29 | 🇧🇬 BG | RIPENCC | allocated |
| 2a0f:6840::/29 | 🇧🇬 BG | RIPENCC | allocated |
All 3 announced prefixes of AS202634 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS202634 hands its own prefixes to: transit providers, or peers at an exchange.
- AS47872SOFIA CONNECT Sofia Connect EAD3
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 AS202634 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/202634Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/202634" | jq