Net@ddress outages and problems
In the past 24 hours, 105 user reports came in for Net@ddress. Counting only the 15-minute windows with a spike big enough to count as an outage, that comes to 96.88% uptime for the day.
The most recent spike big enough to count as an outage was 19 hours ago. The busiest 15-minute window of the day had 39 reports, about 19 hours ago.
-
Outage
Ended 19 h agoLasted 45 min39peak reports
Net@ddress in October 2026
- Problem reports in October (since 28 October)
- 105
Monthly report for October 2026
What people said was wrong in recent problem reports for Net@ddress, as a share of those reports:
- 78% Login
- 19% Website
- 3% App
Where Net@ddress problem reports come from
Recent reports came from 45 areas. The most came from around San Jose, CA, St. Louis, MO and Washington, DC. Share of recent reports by area, named after its biggest town:
- 10% San Jose, CA
- 6% St. Louis, MO
- 6% Washington, DC
- 4% San Francisco, CA
- 4% Louisville, KY
- 4% Houston, TX
From 105 recent problem reports. Big cities always send the most, so reports from many places point to a widespread problem, and one area far ahead of the rest can mean a regional one. Town names: GeoNames.
Net@ddress problem spikes, last 30 days
Since 28 October, Net@ddress had 1 outage spike.
-
Outage
Wed 28 Oct, 01:23–02:08Lasted 45 min42peak 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 28 October 2026. Monthly reports for all services
How to fix Net@ddress not working
Net@ddress 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 netaddress.com 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 Net@ddress.
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 Net@ddress is down: what to use instead
- Gmail If the inbox will not load and you need to send a message, sign in to Gmail in a browser and send from that address.
- Outlook When you need a working mailbox for an urgent reply, open Outlook on the web and use that address for the thread.
- Yahoo Mail If you are locked out long enough to miss a message, Yahoo Mail gives you a browser inbox you can check from another device.
- Phone call For a time-sensitive message that cannot wait on email, call or text the person directly and confirm they got it.
Problems at the same time as Net@ddress
Since 28 October, Net@ddress's only spike 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.
During the latest spike
Net@ddress: Wed 28 Oct, 01:23 to 02:08
- Spotify, outage,27 Oct 19:16 to 01:41
- ESPN Fantasy Football, outage,27 Oct 19:50 to 21:08
- USPS, outage,27 Oct 19:50 to 01:30, 01:53 to 03:23
- Astound, outage,27 Oct 19:50 to 08:26
- Verizon, outage,27 Oct 20:14 to 02:25
- Brightspeed, outage,27 Oct 20:35 to 03:12
- Straight Talk, outage,27 Oct 20:35 to 02:18
- 3 (Three), outage,27 Oct 20:35 to 01:27
44 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.
Net@ddress IP address, servers and network
Checking netaddress.com from our server…
How we track Net@ddress
The status on this page comes from user-submitted problem reports for Net@ddress, counted in 15-minute windows over the last 24 hours. Each window is compared with the normal level for Net@ddress, 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. Net@ddress 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.