AS34385 TRIPNET Tripnet AB
🇸🇪Org handle: ORG-TA46-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
5total
4 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)6,656
Announced (BGP)6,656
IPv6 Addresses
Allocated (RIR)7.9×10²⁸
Announced (BGP)7.9×10²⁸
Announced Prefixes
(BGP)5|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 | |
193.183.119.0/24MOAS | Invalid | - | 2026-10-11 |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)5Prefix | Country | RIR | Status |
|---|---|---|---|
| 31.47.200.0/21 | 🇸🇪 SE | RIPENCC | allocated |
| 193.183.119.0/24 | 🇸🇪 SE | RIPE | assigned |
| 194.14.11.0/24 | 🇸🇪 SE | RIPE | assigned |
| 217.28.192.0/20 | 🇸🇪 SE | RIPENCC | allocated |
| 2a02:24f8::/32 | 🇸🇪 SE | RIPENCC | allocated |
All 5 announced prefixes of AS34385 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS34385 hands its own prefixes to: transit providers, or peers at an exchange.
- AS1257TELE25
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 AS34385 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/34385Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/34385" | jq