AS49327 TELZA-AS TOV "Telza"
🇺🇦Org handle: ORG-TA411-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
6total
6 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)1,024
Announced (BGP)2,304
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Announced Prefixes
(BGP)6|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)1Prefix | Country | RIR | Status |
|---|---|---|---|
| 91.214.28.0/22 | 🇺🇦 UA | RIPENCC | assigned |
All 6 announced prefixes of AS49327 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS49327 hands its own prefixes to: transit providers, or peers at an exchange.
- AS35297DATALINE6
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 AS49327 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/49327Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/49327" | jq