Hey there,
sometimes it happens that when you request something that is a bit further away, that it doesn't get transported. Instead, when you request it, it vanishes from the request pipe list, but stays in the chest and shows up again when you press refresh. You can work around this by destroying a pipe in the network and rebuild this pipe.

Using the latest versions.

it's build as follows:

• The main storage:
  
  

• The connection between the bugging Request Pipe and the storage:
  There's a junction pipe at about each 40 blocks.
  

The chunks should have been active.

Thanks in advance.

Did some more testing. It seems like this happens when the Requestpipe is too far away from the chest, the stuff is stored in.
If one player is requesting for example 1 stack cobble and someone else is looking into the chest where it is stored, player 2 can see that it is not getting transported. Sometimes it vanishes for a split second on request and gets restored.

The count of those items is often also not correct. For stuff that is stored far away you mostly see much more items in the request pipe and you can request them. But they either get transported and not everything is arriving or it looks like it gets transported but on a refresh everything is there again.

Can you verify that by 'far away' you are still maintaining the max search length of each routed pipe? It is a config option.

Yes. I configured it to 200, 1000, 10000 for testing and all routing pipes are within a +-50 block distance from each other.

And it also still happens that items get stuck. It feels like not all routing pipes are known by the network.
The problem is that this doesn't happen reproducible. Sometimes it's after you started the server, sometimes it happens later.