Skip to main content

AS59611

GIGANET-AS

INTERKAM sp. z o.o.

Registry

Authoritative registration data

AS number
59611
Name
GIGANET-AS
Organisation
INTERKAM sp. z o.o.
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

0

Total announced

2

Announced prefixes

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

Prefixes announced by AS59611
91.245.80.0/21 IPv4 /21 not checked
195.20.200.0/23 IPv4 /23 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 AS59611
Address families
EPIX.Katowice 10,000 Mbps IPv4
EPIX.Warszawa 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 AS59611 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

7 networks seen before AS59611 in AS paths

Observed upstreams
Families
AS3257 GTT-BACKBONE 132 347
v4
AS50607 EPIX-KTW-GlobalMix 86 218
v4
AS6939 HURRICANE 21 44
v4
AS201054 EPIX-PolMix 8 30
v4
AS24115 ASN-EQIX-MLPE 8 16
v4
AS137409 GSLNETWORKS-AS-AP 2 4
v4
AS9009 M247 1 2
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS59611 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 18
v4
AS49544 i3Dnet 1 4
v4
AS36236 NETACTUATE 1 2
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.