Skip to main content

AS29056

CITYCOM-AS

------------------------------------------

Registry

Authoritative registration data

AS number
29056
Name
CITYCOM-AS
Organisation
------------------------------------------
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

17

IPv6 prefixes

1

Total announced

18

Announced prefixes

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

Prefixes announced by AS29056
85.237.0.0/19 IPv4 /19 not checked
109.73.144.0/20 IPv4 /20 not checked
217.29.144.0/20 IPv4 /20 not checked
37.143.176.0/20 IPv4 /20 not checked
91.143.96.0/20 IPv4 /20 not checked
185.15.236.0/22 IPv4 /22 not checked
185.220.252.0/22 IPv4 /22 not checked
185.222.128.0/22 IPv4 /22 not checked
185.225.144.0/22 IPv4 /22 not checked
185.228.128.0/22 IPv4 /22 not checked
185.233.144.0/22 IPv4 /22 not checked
185.236.72.0/22 IPv4 /22 not checked
195.88.238.0/23 IPv4 /23 not checked
193.46.248.0/24 IPv4 /24 not checked
194.110.78.0/24 IPv4 /24 not checked
77.75.23.0/24 IPv4 /24 not checked
91.208.56.0/24 IPv4 /24 not checked
2a02:758::/32 IPv6 /32 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 AS29056
Address families
GraX 1,000 Mbps IPv4
VIX 30,000 Mbps IPv4 · IPv6

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 AS29056 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

17 networks seen before AS29056 in AS paths

Observed upstreams
Families
AS8447 2,279 5,906
v4 v6
AS1764 NEXTLAYER-AS 176 3,415
v4
AS6939 HURRICANE 119 401
v4
AS3303 SWISSCOM 47 167
v4 v6
AS13030 INIT7 28 167
v4 v6
AS14840 ASN14840 16 150
v4
AS5405 21 80
v4 v6
AS48362 TKSWF-AS 2 71
v4 v6
AS41327 FIBERTELECOM-AS 14 58
v4
AS9002 RETN-AS 24 44
v6
AS15958 8 30
v4
AS6204 9 29
v4
AS9498 BBIL-AP 6 25
v4
AS6663 6 24
v4
AS263444 6 9
v4
AS29208 4 5
v4
AS25447 1 2
v6

No rows match “”.

Showing of

Observed downstreams

10 networks seen after AS29056 in AS paths

Observed downstreams
Families
AS41437 KNAPP-AS 415 1,247
v4 v6
AS29143 243 933
v4
AS35646 193 501
v4
AS204410 feistritzwerke-steweag 205 434
v4 v6
AS44462 277 410
v4 v6
AS31473 262 384
v4 v6
AS41198 271 350
v4
AS47106 271 350
v4
AS48735 270 349
v4
AS214262 3 15
v6

No rows match “”.

Showing of

Uncertain adjacencies

18 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS47147 AS-ANX 10 108
v4 v6
AS59890 10 64
v4 v6
AS49544 i3Dnet 10 60
v4 v6
AS51184 10 60
v4 v6
AS212483 level86 8 60
v4
AS47692 9 56
v4 v6
AS34288 10 33
v4 v6
AS3212 10 32
v4 v6
AS40994 10 32
v4 v6
AS215628 AS-XENOX-AT 10 32
v4 v6
AS50629 LWLCOM 9 32
v4 v6
AS35369 10 30
v4 v6
AS6720 9 30
v4 v6
AS13004 8 30
v4
AS198150 SIACOM-AS 8 30
v4
AS31510 IKB-AS 8 29
v4 v6
AS29049 8 28
v4
AS8218 NEO-ASN 4 28
v6

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.