Skip to main content

AS41297

ABAKS-AS

ORG-AA278-RIPE

Registry

Authoritative registration data

AS number
41297
Name
ABAKS-AS
Organisation
ORG-AA278-RIPE
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

12

IPv6 prefixes

0

Total announced

12

Announced prefixes

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

Prefixes announced by AS41297
185.241.196.0/22 IPv4 /22 not checked
193.200.50.0/23 IPv4 /23 not checked
91.224.28.0/23 IPv4 /23 not checked
185.241.196.0/24 IPv4 /24 not checked
185.241.197.0/24 IPv4 /24 not checked
185.241.198.0/24 IPv4 /24 not checked
185.241.199.0/24 IPv4 /24 not checked
193.200.50.0/24 IPv4 /24 not checked
193.200.51.0/24 IPv4 /24 not checked
195.74.91.0/24 IPv4 /24 not checked
91.224.28.0/24 IPv4 /24 not checked
91.224.29.0/24 IPv4 /24 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 AS41297
Address families
EPIX.Katowice 10,000 Mbps IPv4
EPIX.Warszawa 20,000 Mbps IPv4
POM-IX 20,000 Mbps IPv4
TPIX PL 20,000 Mbps IPv4

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 AS41297 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS41297 in AS paths

Observed upstreams
Families
AS12741 191 2,360
v4
AS8308 252 1,256
v4
AS6939 HURRICANE 64 330
v4
AS28917 Fiord-AS 2 20
v4
AS6204 2 12
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS41297 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

3 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 28
v4
AS49544 i3Dnet 1 24
v4
AS36236 NETACTUATE 1 12
v4

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.