Transactions randomly not getting broadcasted

Hi!

We recently have issues with transaction not getting broadcasted seemilngy random.

On example (of many).
Here are 3 tx hash we got of the “same” (nonce) transaction we tried to send out. Only the last one was broadcasted.
0xef9bcb27a1f28b8d8b5c9b38b537d237d6ebde2edede2355dd354183dcf383fa
0x679c93a37a45047499732a545981c8c35abc73c6e5b3beb12f2a28a6a2fa1afb
0x414006436b5c715c933381a3c4d359420834121f82800062f62954c802c50ba6

It is no issues with the gas is too low as we had problem previous with, those have gas prices of 72, 69, 70 gwei respectivly.

I suspect that Infura currently has a degraded node(s) which transactions never get broadcasted or some other issue because on our end there is no communication errors between us and Infura and we do get a tx hash from Infura and no errors. And it seems random whenever a tranasction gets broadcasted when we “bump transactions”/resend same nonce. It eiter works the first time or in other cases after 3-5 resends (even with the exact same data so the same tx hash is created).

2 Likes

Hi @Sh1ro and welcome to our Infura community :slight_smile:

We did some investigation at the time this ticket came in and found that one of our transaction subsystems was having some problems. We deployed the fix to mainnet at 18:58 (UTC - 1 October) and our systems should be performing consistently now. If you are still seeing issues with transactions, please let us know.

Hi!

Thanks for the update. However we still experience the same issue.
Here is a recent tx hash timeline where the first two never was broadcasted and the last one was
0x1e17ddf6be8ae28a12acd3bdf3917a539174d036ae75a193111cdacf77b00f78
0x63728be3077a0ea49a0196cda6f26ebf0d2dd08254348dd9678a4f451ebbbfdf
0x77df07cd479ac1d622a5cbea44a1f79ec05eb60e45ad3cafa3dd09a88decb1f7

Same with this timeline
0xa7b6f343d7cc410421bb82740ebbb8077077f620406d4212cd4914ad119219fe
0xea8f990c75554d2e650c2f0cc00fff55e86e8f58311c52753e3e91743e0fece8
0x5b37837cf9270ad66365f25f55a38d280f9d860c886ed91dcc864c0cde6ef106

If you need anymore information from us to investigate/debug just ask.

I had the same issue today at Oct 2 11:35 pm. I can provide more details (privately) if that would be useful @Flaviu