The node this request was sent to never answered at all -- the responding side of THIS message is reporting that a peer it depends on timed out (Remote peer not responding). The failure is one hop further away than the node that generated this message.
In the Cause IE of a GTPv2-C response (Create Session, Modify Bearer, Delete Session…) on S11, S5 or S8.
Got a trace with GTPv2 cause 100 Remote peer not responding? Drop it in the analyzer: it finds the step that really failed first, which node sent the code and what to ask the other side. Captures, test-system PDFs and vendor exports. 5 free analyses a month, no sign-up.
Analyze a trace free