AS209255 TELFAXCOMMUNICATIONS TELFAX COMMUNICATIONS SARL
π«π·Org handle: ORG-TCS38-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
2total
1 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)1,024
Announced (BGP)1,024
IPv6 Addresses
Allocated (RIR)6.3Γ10Β²βΉ
Announced (BGP)6.3Γ10Β²βΉ
Prefix Limit (IPv4)
10
Prefix Limit (IPv6)
5
Country
π«π· FRRIR
RIPE NCCStatus
allocated
Allocated
2019-03-11
Routing hygiene
Score 10/100 Β· Low riskRPKI ROA coverage
100%
no RPKI invalid prefixes
IRR route objects
100%
no origin mismatches
Hijack signals
0
0 announced against others' ROAs, 0 own announced by others
Upstreams
1
diversity 0/100
- Only one upstream seen in the AS paths of its routes
Based on 2 announced prefixes, updated daily (2026-10-24). How the score works Β· RPKI explained
Announced Prefixes
(BGP)2|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-24 | |
| Valid | RIPE | 2026-10-24 |
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 92.119.52.0/22 | π«π· FR | RIPENCC | allocated |
| 2a09:b640::/29 | π«π· FR | RIPENCC | allocated |
All 2 announced prefixes of AS209255 β
Downstream Customers(1)
| ASN | Name |
|---|---|
| AS60983 | π«π·LIOPEN-AS LIOPEN SARL |
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
- How to run an ASPA checkVerify the upstream providers listed above
- 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/209255Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/209255" | jq