AS39156 FTELECOM-AS First Telecom Ltd
🇷🇺Org handle: ORG-FTL2-RIPE
Vorontsovskaya str., 35b, building 2
RIPE NCCallocated
Announced Prefixes (BGP)
3total
3 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)6,400
Announced (BGP)6,400
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
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 |
|---|---|---|---|
| 80.76.224.0/20 | 🇷🇺 RU | RIPENCC | allocated |
| 80.76.236.0/24 | 🇷🇺 RU | RIPE | assigned |
| 109.235.208.0/21 | 🇷🇺 RU | RIPENCC | allocated |
All 3 announced prefixes of AS39156 →
BGP Neighbours
(seen in AS paths)Upstreams (2)
Networks AS39156 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (4)
Networks whose own prefixes AS39156 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 AS39156 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/39156Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/39156" | jq