Skip to main content

AS34154

CONFIGO-AS

. Upstreams

Registry

Authoritative registration data

AS number
34154
Name
CONFIGO-AS
Organisation
. Upstreams
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

6

IPv6 prefixes

1

Total announced

7

Announced prefixes

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

Prefixes announced by AS34154
217.71.216.0/21 IPv4 /21 not checked
185.121.196.0/22 IPv4 /22 not checked
185.222.204.0/22 IPv4 /22 not checked
195.160.196.0/22 IPv4 /22 not checked
185.237.34.0/24 IPv4 /24 not checked
193.17.230.0/24 IPv4 /24 not checked
2a00:1fe8::/32 IPv6 /32 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 AS34154
Address families
ERA-IX Frankfurt 10,000 Mbps IPv4 · IPv6
NL-ix: Main 10,000 Mbps IPv4 · IPv6
OpenCarrier OCIX 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 AS34154 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

24 networks seen before AS34154 in AS paths

No rows match “”.

Showing – of

Observed downstreams

4 networks seen after AS34154 in AS paths

Observed downstreams
Families
AS61430 AS-MILDE 749 4,351
v4 v6
AS203175 rto 277 1,065
v4
AS62028 FNSH 17 32
v4 v6
AS209216 Trusted-Colo 1 2
v4

No rows match “”.

Showing – of

Uncertain adjacencies

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