Skip to main content

AS198579

KOMPUTERSAT-AS

KOMPUTERSAT SP. Z O.O.

Registry

Authoritative registration data

AS number
198579
Name
KOMPUTERSAT-AS
Organisation
KOMPUTERSAT SP. Z O.O.
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

0

Total announced

1

Announced prefixes

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

Prefixes announced by AS198579
83.242.112.0/20 IPv4 /20 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 AS198579
Address families
EPIX.Warszawa 10,000 Mbps IPv4
THINX Warsaw 10,000 Mbps IPv4
TPIX PL 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 AS198579 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS198579 in AS paths

Observed upstreams
Families
AS29535 MIX2_OpenPeering 258 336
v4
AS62081 EPIX-WAW-GlobalMix 22 24
v4
AS201054 EPIX-PolMix 8 11
v4
AS33891 CORE-BACKBONE 4 7
v4
AS6204 ZET-NET 1 1
v4
AS24748 THINX_Poland 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS198579 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
AS49544 i3Dnet 1 2
v4
AS24482 SGGS-AS-AP 1 1
v4
AS28917 Fiord-AS 1 1
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.