Skip to main content

AS34641

Servperso_Systems_CORP

This ASN is used for our internal IT infrastructure, peer our transit asn via AS34872

Registry

Authoritative registration data

AS number
34641
Name
Servperso_Systems_CORP
Organisation
This ASN is used for our internal IT infrastructure, peer our transit asn via AS34872
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

0

IPv6 prefixes

3

Total announced

3

Announced prefixes

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

Prefixes announced by AS34641
2a0f:8400::/32 IPv6 /32 RPKI valid
2a0f:8400:7e0::/44 IPv6 /44 not checked
2a0f:8400:7f0::/44 IPv6 /44 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 AS34641
Address families
DE-CIX Dusseldorf: DE-CIX Dusseldorf Peering LAN 1,000 Mbps IPv4 · IPv6
DE-CIX Frankfurt: DE-CIX Frankfurt Peering LAN 200,000 Mbps IPv4 · IPv6
LOCIX DUSSELDORF: Peering LAN 10,000 Mbps IPv4 · IPv6
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 AS34641 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS34641 in AS paths

Observed upstreams
Families
AS34872 Servperso_Systems 156 223
v6
AS6939 HURRICANE 67 172
v6
AS24961 MYLOC-AS 37 73
v6
AS48362 TKSWF-AS 2 6
v6
AS205794 RTTW-AS 1 2
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS34641 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

22 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.