AS30798 TNNET-AS TNNet Oy

🇫🇮

Org handle: ORG-TO2-RIPE

TNNet Oy Main network

RIPE NCCallocated

Announced Prefixes (BGP)

6total

5 IPv41 IPv6

IPv4 Addresses

Allocated (RIR)37,888

Announced (BGP)37,888

IPv6 Addresses

Allocated (RIR)7.9×10²⁸

Announced (BGP)7.9×10²⁸

Prefix Limit (IPv4)

Prefix Limit (IPv6)

Country

RIR

Status

allocated

Allocated

2003-12-08

Announced Prefixes

(BGP)6

Prefix	RPKI	IRR	Last Seen
45.154.68.0/22	Valid	RIPE	2026-10-11
62.204.0.0/19	Valid	RIPE	2026-10-11
89.236.64.0/18	Valid	RIPE	2026-10-11
213.185.32.0/19	Valid	RIPE	2026-10-11
217.112.240.0/20	Valid	RIPE	2026-10-11
2001:40e8::/32	Valid	RIPE	2026-10-11

(RIR)6

Prefix	Country	RIR	Status
45.154.68.0/22	🇫🇮 FI	RIPENCC	allocated
62.204.0.0/19	🇫🇮 FI	RIPENCC	allocated
89.236.64.0/18	🇫🇮 FI	RIPENCC	allocated
213.185.32.0/19	🇫🇮 FI	RIPENCC	allocated
217.112.240.0/20	🇫🇮 FI	RIPENCC	allocated
2001:40e8::/32	🇫🇮 FI	RIPENCC	allocated

(seen in AS paths)

Networks AS30798 hands its own prefixes to: transit providers, or peers at an exchange.

ASPA

No ASPA

Abuse Contact

+31205354444

External Links

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 AS30798 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

Returns ASN details, announced prefixes, and BGP routing data.

curl -s "https://api.ipctl.io/v1/asn/30798" | jq