NFSE outages and problems
User reports, last 24 hours
1,655 reports in total, counted in 15-minute windows
In the last hour, 8 problem reports came in for NFSE, and at this time of day there are usually almost none. Over the last 24 hours there were 1,655 reports. Most recent reports were about website (57%) and login (31%). The last spike in reports was 3 h ago and lasted 24 min. These are user reports from Brazil, where most people report NFSE problems.
- NormalClose to the usual level13 h · 99 reports
- ElevatedMore than 1.5 times the usual level9 h 15 min · 767 reports
- OutageMore than twice the usual level and far above the day's average1 h 45 min · 789 reports
- Usual levelWhat a usual day sees at that timeAlmost none at this time of day
In the past 24 hours, 1,655 user reports came in for NFSE. Counting only the 15-minute windows with a spike big enough to count as an outage, that comes to 92.71% uptime for the day.
The most recent spike big enough to count as an outage was 6 hours ago. The busiest 15-minute window of the day had 179 reports, about 13 hours ago.
-
Elevated reports
Ended 3 h agoLasted 15 min10peak reports
-
Elevated reports
Ended 4 h agoLasted 15 min11peak reports
-
Outage
Ended 5 h agoLasted 10 h 45 min179peak reports
NFSE in November 2026
- Problem reports in November (since 3 November)
- 1,704
Monthly report for November 2026
What went wrong
What people said was wrong in recent problem reports for NFSE.
Share of 294 recent reports that said what was wrong.
NFSE problem spikes, last 30 days
Since 3 November, NFSE had 1 outage spike and 2 periods of elevated reports. The longest lasted 10 h 45 min, on 4 November.
-
Elevated reports
Wed 4 Nov, 23:43–00:07Lasted 24 min13peak reports
-
Elevated reports
Wed 4 Nov, 23:03–23:18Lasted 15 min11peak reports
-
Outage
Lasted 10 h 45 min186peak reports
A spike is a sharp rise in problem reports from users, kept exactly as this page showed it at the time. This history starts on 3 November 2026. Monthly reports for all services
How to fix NFSE not working
NFSE is up on our end, so if it won't work for you, the problem is most likely on your side. Work through these in order:
Your browser tries to reach nfse.gov.br over your own connection, right now. Nothing is sent to us or stored.
Reload and restart
Reload the page (Ctrl+F5, or Cmd+Shift+R on a Mac), or fully close the app and open it again.
Try another connection
Switch between Wi-Fi and mobile data. If it works on one and not the other, the problem is your network, not NFSE.
Update the app
Install the latest version from the App Store or Google Play. Old versions can stop connecting after a server-side change.
While NFSE is down: what to use instead
- NFS-e Mobile app Use the official mobile app if the web portal is failing and you only need a basic invoice action that the app supports.
- Municipal NFS-e portal Try your city hall's own invoice system if your municipality still accepts service invoices outside the national portal.
- RPS contingency Use a Recibo Provisório de Serviços only if your local rules or accountant allow it, then convert it to an invoice when NFSE works again.
- City tax office channel Contact the prefeitura tax department when the invoice deadline is close and you need the local procedure for an outage.
Problems at the same time as NFSE
Since 3 November, all 3 of NFSE's spikes in problem reports overlapped a spike at another service.
When several services get problem reports at once, something they share, such as a cloud host or a network, can be the real cause. Matching times alone do not prove it.
Most often at the same time
- Freenet3 times
- Sainsbury’s3 times
- GOV.BR3 times
- USPS3 times
- Facebook3 times
- Deutsche Glasfaser3 times
How many of NFSE's spikes overlapped one of theirs.
During the latest spike
NFSE: Wed 4 Nov, 23:43 to 5 Nov 00:07
- Sainsbury’s, outage,07:33 to 5 Nov 00:03
- GOV.BR, outage,10:18 to 5 Nov 02:18
- USPS, outage,10:48 to 5 Nov 02:03
- Facebook, outage,13:47 to 5 Nov 03:02
- Deutsche Glasfaser, outage,14:03 to 5 Nov 00:48
- Sam's Club, outage,15:18 to 5 Nov 02:33
- Capital One, outage,16:48 to 5 Nov 03:03
- X (Twitter), outage,18:03 to 5 Nov 00:03
68 more services. Red dot: outage. Amber dot: elevated reports.
A spike is a sharp rise in problem reports from users, as the live pages showed it. Times are Central European time.
When people report NFSE problems
The busiest hour for reports about NFSE is 01:00 to 02:00 Central European time, and the busiest day is Wednesday.
By hour of the day
- 00:00 to 01:00: 0.83 reports on an average day
- 01:00 to 02:00: 1.1 reports on an average day
- 02:00 to 03:00: 0.66 reports on an average day
- 03:00 to 04:00: 0.16 reports on an average day
- 04:00 to 05:00: 0.11 reports on an average day
- 05:00 to 06:00: 0 reports on an average day
- 06:00 to 07:00: 0 reports on an average day
- 07:00 to 08:00: 0.04 reports on an average day
- 08:00 to 09:00: 0.04 reports on an average day
- 09:00 to 10:00: 0.03 reports on an average day
- 10:00 to 11:00: 0.38 reports on an average day
- 11:00 to 12:00: 0.87 reports on an average day
- 12:00 to 13:00: 0 reports on an average day
- 13:00 to 14:00: 0 reports on an average day
- 14:00 to 15:00: 0 reports on an average day
- 15:00 to 16:00: 0 reports on an average day
- 16:00 to 17:00: 0 reports on an average day
- 17:00 to 18:00: 0 reports on an average day
- 18:00 to 19:00: 0 reports on an average day
- 19:00 to 20:00: 0 reports on an average day
- 20:00 to 21:00: 0 reports on an average day
- 21:00 to 22:00: 0 reports on an average day
- 22:00 to 23:00: 0.08 reports on an average day
- 23:00 to 00:00: 0.51 reports on an average day
By day of the week
- Monday: 0 reports on an average Monday
- Tuesday: 0.96 reports on an average Tuesday
- Wednesday: 29 reports on an average Wednesday
- Thursday: 9.8 reports on an average Thursday
- Friday: 0 reports on an average Friday
- Saturday: 0 reports on an average Saturday
- Sunday: 0 reports on an average Sunday
Each bar is the average number of user reports in that hour, or on that day of the week, from 28 days of reports since 5 October 2026. The busiest bar is highlighted. Spikes in reports are left out, so one outage does not set the pattern.
NFSE IP address, servers and network
- IPv4 address
- 2.59.134.75
- IPv6
- Not offered
- Network
- AS58212 · dataforest GmbH, registered in Germany
- DNS hosted by
- its own name servers (gov.br)
- HTTPS certificate
- Issued by Let's Encrypt, valid until 7 Dec 2026 (32 days)
- HTTP/3
- Not advertised
- Our check
- No answer within 10 seconds
Checked from our server in Frankfurt, Germany, 1 h ago, for nfse.gov.br. Visitors elsewhere may see different addresses.
Checked from 12 places around the world
None of the 12 locations got an answer from nfse.gov.br (address not found). Our own check from Frankfurt got no answer either, 1 h ago. Some sites drop automated checks from particular data-centre servers, so this alone doesn't mean people there can't reach it; the live reports above show what users see.
| Location | Result | Time | Address reached |
|---|---|---|---|
| FrankfurtGermany | Address not found | – | – |
| ViennaAustria | Address not found | – | – |
| MilanItaly | Address not found | – | – |
| ParisFrance | Address not found | – | – |
| AmsterdamNetherlands | Address not found | – | – |
| MadridSpain | Address not found | – | – |
| WarsawPoland | Address not found | – | – |
| DallasUSA | Address not found | – | – |
| Los AngelesUSA | Address not found | – | – |
| São PauloBrazil | Address not found | – | – |
| SingaporeSingapore | Address not found | – | – |
| TokyoJapan | Address not found | – | – |
Checked with check-host.net from its servers in these cities 1 h ago, for nfse.gov.br. Time is how long each server took to load the page.
Contact NFSE support
Tip: NFSE doesn't list a public status page that we know of, so its help centre and the report chart on this page are the best places to check.
How we track NFSE
The status on this page comes from user-submitted problem reports for NFSE, counted in 15-minute windows over the last 24 hours. Each window is compared with the normal level for NFSE, so a few complaints on a quiet day don't trigger anything, but a sudden jump well above normal does.
When reports climb well above normal, the status here changes to partial outage or major outage and the chart moves with it. NFSE doesn't publish a public status page that we know of, so user reports are often the quickest sign that something is wrong on their side.