PacketStream stopped earning for a month, then started again

September recorded $0.44. The account was fine, nothing structural had changed at PacketStream, and no outage I could find ever happened. A single month simply went to zero and then it did not.

The most likely explanation is still the boring one I named before having the answer: either the client stopped on my host and recovered, or no buyer routed traffic through my IP for a full month. On a connection where PacketStream is the smallest earner in the stack, a month of nobody wanting it is entirely plausible and needs no scandal to explain it.

I am leaving the original version of this page below rather than rewriting it into something that looks prescient. The useful part was never the diagnosis. It was that a row can go silently to zero and stay there, and if you are not reading dashboards monthly you will not notice.

PacketStream earned $1.22 in July, which was modest but real and in line with where it sits against the rest of the stack. In August it recorded nothing at all. Not a reduced figure, nothing.

That is a different shape from what happened elsewhere. Honeygain fell 22%, Repocket fell 37%, Traffmonetizer fell 64%, all of which look like demand softening. A clean drop to zero usually is not demand. It is something structural: a node that stopped running, an account flagged, a payout page I could not read, or the service itself changing.

I went looking for reports of a wider PacketStream outage or shutdown in this period and found nothing usable either way. Absence of chatter is not evidence that nothing happened, so I am not going to present it as a finding.

I also cannot rule out the most boring explanation, which is that the client died on my host and I did not notice, because an app that silently stops is the single most common failure in this category and the main argument for --restart always on every container.

Resolved: September earned $0.44, so the account was in good standing throughout.

Nobody writing about these apps publishes the ones that stopped working. Every table in this category is a list of survivors, which is why every table in this category is useless for deciding what to actually run.

A row going to zero is more informative than a row earning two dollars. It tells you the failure mode exists, that it can happen quietly, and that if you are not reading your own dashboards monthly you will not catch it. If this turns out to be my container dying rather than anything PacketStream did, that is still the most useful thing on this page.