interesting test case! your granular data is below.... interesting that it was #3 where we saw the zap receipt... this can sometimes happen due flakiness on whatever server you have producing your zap receipts -- or could possibly be whatever relays you are sending zap receipts to... or could be something else...

Individual Zap Attempts:

1. Attempted at: 2025-12-28 04:52:07 UTC

LNURL: 1710ms

Callback/Invoice Generate: 1040ms

Attempt ➡ Lightning Confirmation: 2602ms

Lightning Confirmation ➡ Zap Receipt: N/A

---

2. Attempted at: 2025-12-28 05:49:51 UTC

LNURL: 1605ms

Callback/Invoice Generate: 1071ms

Attempt ➡ Lightning Confirmation: 1058ms

Lightning Confirmation ➡ Zap Receipt: N/A

---

3. Attempted at: 2025-12-28 06:38:14 UTC

LNURL: 552ms

Callback/Invoice Generate: 921ms

Attempt ➡ Lightning Confirmation: 5153ms

Lightning Confirmation ➡ Zap Receipt: 4049ms

---

4. Attempted at: 2025-12-28 07:01:14 UTC

LNURL: 1794ms

Callback/Invoice Generate: 1083ms

Attempt ➡ Lightning Confirmation: 1038ms

Lightning Confirmation ➡ Zap Receipt: N/A

---

5. Attempted at: 2025-12-28 07:36:26 UTC

LNURL: 1929ms

Callback/Invoice Generate: 1100ms

Attempt ➡ Lightning Confirmation: 1171ms

Lightning Confirmation ➡ Zap Receipt: N/A

---

6. Attempted at: 2025-12-28 08:18:20 UTC

LNURL: 547ms

Callback/Invoice Generate: 1074ms

Attempt ➡ Lightning Confirmation: 1013ms

Lightning Confirmation ➡ Zap Receipt: N/A

---

Reply to this note

Please Login to reply.

Discussion

No replies yet.