We are experiencing an issue with Apigee destination endpoint routing following the automatic mainte

Google Cloud Apigee
1

Hello mates,

A customer told us about this bug after Friday’s update. We can’t find the reason, has something similar happened to you?

We are experiencing an issue with Apigee destination endpoint routing following the automatic maintenance update for the Apigee instance last Friday. The issue arises when routing hostnames to IP addresses for newly created endpoint attachments.

Problem summary:
- Existing Attachments: The example.com endpoint attachment is being correctly routed to IP 7.0.20.5 as expected.
- New attachments: After creating a new attachment with IP 7.0.20.28 and updating DNS (example.com → 7.0.20.28), routing fails. Apigee logs show the destination IP as "example.com/7.0.20.28", while previous endpoint attachment configurations that were created before Apigee maintenance correctly show “7.0.20.28”.

2

Hey @alexdvtgcloud , thanks for your question - We’re keeping an eye on this thread to ensure you get the answers you need, and we also invite the community to pitch in with their thoughts.

Your patience means a lot to us. Additionally, consider checking our articles and upcoming events! :blush:

1 Like
3

Hi @alexdvtgcloud – please could you clarify what you mean by “Apigee logs”.

Have you tried setting a new DNS record for the new IP/attachment instead of updating the existing one?

In any case, this seems like a specific enough question that would be most appropriate for the support teams to investigate, as it may require visibility and access to the infrastructure/instance in question. Please could you raise a support case to have this properly investigated. Feel free to include a link to this post in the case description.

Thanks!