Skip to main content

AS43171

MAXNET

MAXNET-AS

Registry

Authoritative registration data

AS number
43171
Name
MAXNET
Organisation
MAXNET-AS
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

6

IPv6 prefixes

0

Total announced

6

Announced prefixes

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

Prefixes announced by AS43171
46.175.224.0/20 IPv4 /20 not checked
91.189.32.0/21 IPv4 /21 not checked
185.59.108.0/22 IPv4 /22 not checked
195.22.126.0/23 IPv4 /23 not checked
91.221.172.0/23 IPv4 /23 not checked
77.87.77.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 AS43171
Address families
EPIX.Katowice 100,000 Mbps IPv4 · IPv6
EPIX.Warszawa 100,000 Mbps IPv4 · IPv6
Equinix Warsaw 10,000 Mbps IPv4
POM-IX 10,000 Mbps IPv4
TPIX PL 1,000 Mbps IPv4
WRIX: WRIX 10,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 AS43171 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

7 networks seen before AS43171 in AS paths

Observed upstreams
Families
AS62081 823 2,592
v4
AS29535 86 325
v4
AS9141 103 230
v4
AS201054 16 28
v4
AS24115 ASN-EQIX-MLPE 4 20
v4
AS137409 GSLNETWORKS-AS-AP 2 15
v4
AS35320 1 5
v4

No rows match “”.

Showing – of

Observed downstreams

4 networks seen after AS43171 in AS paths

Observed downstreams
Families
AS202962 293 387
v4
AS215204 293 384
v4
AS5550 TASK-AS 122 161
v4
AS197848 5 10
v4

No rows match “”.

Showing – of

Uncertain adjacencies

3 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 3 28
v4
AS49544 i3Dnet 3 14
v4
AS36236 NETACTUATE 3 7
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.