Home ASN LookupAS212148

AS212148 ITECON synaforce GmbH

🇩🇪

Org handle: ORG-HGG4-RIPE

RIPE NCCallocated

Announced Prefixes (BGP)

6total

3 IPv43 IPv6

IPv4 Addresses

Allocated (RIR)256

Announced (BGP)768

IPv6 Addresses

Allocated (RIR)6.3×10²⁹

Announced (BGP)6.3×10²⁹

Prefix Limit (IPv4)

Prefix Limit (IPv6)

Country

🇩🇪 DE

RIR

RIPE NCC

Status

allocated

Allocated

2020-12-16

Announced Prefixes

(BGP)6

Prefix	RPKI	IRR	Last Seen
91.212.156.0/24	Valid	RIPE	2026-10-08
154.47.0.0/24	No ROA	Other IRR	2026-10-08
154.47.1.0/24	No ROA	Other IRR	2026-10-08
2a07:b280::/29	Valid	RIPE	2026-10-08
2a07:b280:100::/40	Valid	RIPE	2026-10-08
2a07:b280:200::/40	Valid	RIPE	2026-10-08

Allocated Prefixes

(RIR)2

Prefix	Country	RIR	Status
91.212.156.0/24	🇩🇪 DE	RIPENCC	allocated
2a07:b280::/29	🇩🇪 DE	RIPENCC	allocated

All 6 announced prefixes of AS212148 →

BGP Neighbours

(seen in AS paths)

Upstreams (2)

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

AS205769Mainzer Breitband Mainzer Breitband4
AS174Cogent Communications2

Transfer History

Registry transfers of AS212148 between organisations.

AS212148M&A · 2023-09-26
ITecon GmbH
RIPE NCC
→
synaforce GmbH
RIPE NCC

Date	Resource	From	To	Type
2023-09-26	AS212148	ITecon GmbH RIPE NCC	synaforce GmbH RIPE NCC	M&A

ASPA

No ASPA

Abuse Contact

External Links

RIPE Whois RIPEstat

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

GEThttps://api.ipctl.io/v1/asn/212148

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

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