Bling logo

Bling outage on 16 November 2026

Major outage
Resolved · 11:36–20:03 UTC
Get alerts for Bling

An email when it goes down, and when it’s back.

“180 - Rejeição: Código Regime Tributário do emitente diverge do cadastro na Receita Federal”

On 16 November, Bling's Fiscal component had a major outage from 11:35 to 20:02 UTC, about 8 hours 27 minutes, during which some merchandise return invoices (NF-e de devolução) were rejected with error 321. The status page said the rejection was related to instability at SEFAZ, and at 20:02 it said the situation appeared normalized. Alura, Bitbucket, Hostinger, Musixmatch, GitHub, Auto Trader UK and Lovable also had problems at the same time.

Bling’s own incident page ↗
When
11:36–20:03 UTC
How long
8 h 27 min
Incident open on its page
11:35–20:02 UTC
Components affected
1
Bling, 30 days before
5 other outages

What broke when

Major outage
Partial outage
Degraded
Fiscal
UTC 12:0014:0016:0018:0020:00

From Bling’s own status page: when it moved each component into trouble, and back.

At the same time

Started in the hour before or during it

And 466 lesser-known services. Problems at the same time are a clue, never proof that one caused another.

Timeline

Times in UTC

  1. Investigating
  2. Fiscal: partial outage
  3. Resolved
  4. Fiscal: back to normal

Where this comes from

Stackpulse reads Bling’s official status page at status.bling.com.br every minute. The times above are when it reported the problem; the summary is written from its updates and checked against them.

Stackpulse isn’t affiliated with Bling. Names and logos belong to their owners.