AS62416 PTServidor SAMPLING LINE-SERVICOS E INTERNET, LDA
🇵🇹Org handle: ORG-SLEI4-RIPE
RIPE NCCallocatedASPA Published
Announced Prefixes (BGP)
4total
3 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)2,304
Announced (BGP)2,304
IPv6 Addresses
Allocated (RIR)6.3×10²⁹
Announced (BGP)6.3×10²⁹
Routing hygiene
Score 6/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
2
diversity 38/100
- All announced prefixes have a valid ROA and a matching IRR route object
Based on 4 announced prefixes, updated daily (2026-10-24). How the score works · RPKI explained
Announced Prefixes
(BGP)4|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 |
Allocated Prefixes
(RIR)4Prefix | Country | RIR | Status |
|---|---|---|---|
| 185.32.188.0/22 | 🇵🇹 PT | RIPENCC | allocated |
| 185.32.190.0/24 | 🇵🇹 PT | RIPE | assigned |
| 185.222.8.0/22 | 🇵🇹 PT | RIPENCC | allocated |
| 2a00:c560::/29 | 🇵🇹 PT | RIPENCC | allocated |
All 4 announced prefixes of AS62416 →
BGP Neighbours
(seen in AS paths)Upstreams (2)
Networks AS62416 hands its own prefixes to: transit providers, or peers at an exchange.
Transfer History
Registry transfers of AS62416 between organisations.
- AS62416Transfer ·
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/62416Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/62416" | jq