AS34970 DIATEM Diatem SAS

🇫🇷

Org handle: ORG-DA98-RIPE

67300 SCHILTIGHEIM

RIPE NCCallocated

Announced Prefixes (BGP)

8total

8 IPv40 IPv6

IPv4 Addresses

Allocated (RIR)4,096

Announced (BGP)5,120

IPv6 Addresses

Allocated (RIR)0

Announced (BGP)0

Prefix Limit (IPv4)

Prefix Limit (IPv6)

Country

RIR

Status

allocated

Allocated

2005-05-10

Announced Prefixes

(BGP)8

Prefix	RPKI	IRR	Last Seen
91.195.206.0/23	Valid	RIPE	2026-10-10
95.130.152.0/21	Valid	RIPE	2026-10-10
130.117.58.0/23	No ROA	Other IRR	2026-10-10
185.55.144.0/22	Valid	RIPE	2026-10-10
194.50.78.0/24	Valid	RIPE	2026-10-10
212.103.24.0/24	Valid	RIPE	2026-10-10
212.103.25.0/24	Valid	RIPE	2026-10-10
212.103.28.0/24	Valid	RIPE	2026-10-10

(RIR)5

Prefix	Country	RIR	Status
91.195.206.0/23	🇫🇷 FR	RIPENCC	assigned
95.130.152.0/21	🇫🇷 FR	RIPENCC	allocated
185.55.144.0/22	🇫🇷 FR	RIPENCC	allocated
194.50.78.0/24	🇫🇷 FR	RIPENCC	assigned
212.103.25.0/24	🇫🇷 FR	RIPE	assigned

(seen in AS paths)

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

ASPA

No ASPA

Abuse Contact

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 AS34970 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/34970" | jq