Skip to main content

AS197049

ISBANDUROWSKI

INTERNET SERWIS WOJCIECH BANDUROWSKI

Registry

Authoritative registration data

AS number
197049
Name
ISBANDUROWSKI
Organisation
INTERNET SERWIS WOJCIECH BANDUROWSKI
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

0

Total announced

4

Announced prefixes

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

Prefixes announced by AS197049
178.216.104.0/21 IPv4 /21 not checked
178.216.104.0/22 IPv4 /22 not checked
178.216.108.0/22 IPv4 /22 not checked
178.216.105.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 AS197049
Address families
EPIX.Katowice 10,000 Mbps IPv4
EPIX.Warszawa 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 AS197049 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS197049 in AS paths

Observed upstreams
Families
AS50607 175 698
v4
AS62081 276 555
v4
AS201054 EPIX-PolMix 23 97
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS197049 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 36
v4
AS49544 i3Dnet 1 8
v4
AS36236 NETACTUATE 1 4
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.