Skip to main content

AS200031

NETCITY-KIELCE

Netcity Sp. z o.o.

Registry

Authoritative registration data

AS number
200031
Name
NETCITY-KIELCE
Organisation
Netcity Sp. z o.o.
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 AS200031
45.159.164.0/22 IPv4 /22 not checked
195.60.64.0/23 IPv4 /23 not checked
91.193.40.0/23 IPv4 /23 not checked
91.195.56.0/23 IPv4 /23 not checked
91.215.44.0/23 IPv4 /23 not checked
91.215.46.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 AS200031
Address families
EPIX.Katowice 40,000 Mbps IPv4
EPIX.Warszawa 40,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 AS200031 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS200031 in AS paths

Observed upstreams
Families
AS29535 MIX2_OpenPeering 162 1,290
v4
AS174 COGENT-174 84 600
v4
AS201054 EPIX-PolMix 22 138
v4
AS33891 CORE-BACKBONE 4 36
v4
AS3257 GTT-BACKBONE 4 24
v4
AS6204 ZET-NET 1 6
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS200031 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

4 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS49544 i3Dnet 1 12
v4
AS24482 SGGS-AS-AP 1 6
v4
AS28917 Fiord-AS 1 6
v4
AS36236 NETACTUATE 1 6
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.