AS16331 TELE-ENTRE-FI-AS Tele-entre Oy
🇫🇮Org handle: ORG-TO1-RIPE
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 33/100 · Medium riskRPKI ROA coverage
50%
no RPKI invalid prefixes
IRR route objects
50%
no origin mismatches
Hijack signals
0
0 announced against others' ROAs, 0 own announced by others
Upstreams
1
diversity 0/100
- 50% of announced prefixes (1 of 2) have no valid ROA
- Only one upstream seen in the AS paths of its routes
- 50% of announced prefixes (1 of 2) have no IRR route object for this ASN
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 |
|---|---|---|---|
| No ROA | - | 2026-10-24 | |
| Valid | RIPE | 2026-10-24 |
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 217.116.160.0/21 | 🇫🇮 FI | RIPENCC | allocated |
| 217.116.160.0/22 | 🇫🇮 FI | RIPE | assigned |
| 2a00:5240::/32 | 🇫🇮 FI | RIPENCC | allocated |
All 2 announced prefixes of AS16331 →
Upstream Providers(1)
| ASN | Name |
|---|---|
| AS204779 | 🇫🇮LOCALNETFI Local Loop Oy |
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS16331 hands its own prefixes to: transit providers, or peers at an exchange.
- AS204779LOCALNETFI Local Loop Oy2
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/16331Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/16331" | jq