Live / Bling / Incident
Bling: 321 - Rejeição: NF-e de devolução de mercadoria não possui documento fiscal referenciado por item
Bling · bling.com.brMajor incidentResolved2026-10-06 14:01 UTC
Public — what happened
Summary
Bling reported a problem on October 5, 2026, starting at 14:37 UTC, in which some return invoices (electronic tax documents for returned goods) were being rejected with error code 321, a message saying the referenced original document was missing for each item. The company classified the issue as major and said its team was looking into the cause, advising customers to wait and try issuing the invoice again later. Bling did not publicly name a cause, and the incident was marked resolved on October 6, 2026, at 14:01.
Affected
Fiscal
Timeline
- Started — 2026-10-05 14:37 UTC
- Investigating — 2026-10-05 14:37 UTC
- Resolved — 2026-10-06 14:01 UTC · 23h 24m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Bling against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Bling: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Bling report →
More from Bling
Covered in The Squid’s Ink, Week 42, 2026, our weekly internet health report.