Skip to main content

AS205094

PERSONAL-PACKET

Personal Packet GmbH

Registry

Authoritative registration data

AS number
205094
Name
PERSONAL-PACKET
Organisation
Personal Packet GmbH
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

1

Total announced

3

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS205094
213.142.154.0/23 IPv4 /23 RPKI valid
195.128.143.0/24 IPv4 /24 not checked
2a12:f140::/29 IPv6 /29 not checked

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS205094
Address families
LOCIX FRANKFURT: Peering LAN 10,000 Mbps IPv4 · IPv6

No rows match “”.

Showing – of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS205094 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

7 networks seen before AS205094 in AS paths

Observed upstreams
Families
AS56382 VSERVERLTD 170 434
v4 v6
AS25394 MK-NETZDIENSTE-AS 117 290
v4 v6
AS6939 HURRICANE 172 270
v4 v6
AS25091 IP-Max 2 11
v4 v6
AS14840 ASN14840 2 10
v4
AS401753 BIXCE 1 3
v4 v6
AS48646 STEFAN6 1 1
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS205094 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

14 adjacencies that may be an artefact of collector peering

No rows match “”.

Showing – of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.