It can be very very hard to comply with the AGPL in the business world. (I am not going to say corporate because even a mom and pop shop end up with these questions at times.)
Does a one line patch to some code to have a package run in /opt/foo versus /srv/foo need to be made public? In what way is properly making it public?
Does your config file need to be public (especially if the config file contains AGPL headers?)
Ask upstream and you get one answer, Ask your company lawyer and get another answer. As a "customer" ask a lawyer and get a third answer. Ask the FSF and you get possibly a fourth answer.
All of which may not have any meaning until brought before a court as the License may be seen as a Contract due to the fact that you are promising services (download of software) as a third party. Hopefully this can be clarified by various groups, but it is the unanswered Fear, Uncertainty and Doubt I have heard time and time again by even proponents of AGPL.