AS196874 TELENET-RSM Telenet S.r.l.
🇸🇲Org handle: ORG-Ts87-RIPE
TeleneT San Marino
RIPE NCCallocatedASPA Published
Announced Prefixes (BGP)
2total
2 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)3,072
Announced (BGP)3,072
IPv6 Addresses
Allocated (RIR)7.9×10²⁸
Announced (BGP)0
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-23). How the score works · RPKI explained
Announced Prefixes
(BGP)2|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-25 | |
| Valid | RIPE | 2026-10-25 |
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 109.233.80.0/21 | 🇸🇲 SM | RIPENCC | allocated |
| 192.145.48.0/22 | 🇸🇲 SM | RIPENCC | allocated |
| 2a01:f600::/32 | 🇸🇲 SM | RIPENCC | allocated |
All 2 announced prefixes of AS196874 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS196874 hands its own prefixes to: transit providers, or peers at an exchange.
- AS12874FASTWEB SpA2
Downstreams (4)
Networks whose own prefixes AS196874 passes on: usually its customers.
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/196874Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/196874" | jq