AwwURL logo

Is Tnebnet down right now?

Partial outage  since 01:48 UTC
Tnebnet is having problems. It failed from 3 of 7 locations and loaded from the rest, so it depends where you are.

No one has reported a problem in the last hour.

🇺🇸Phoenix✕🇺🇸Los Angeles✕🇿🇦Cape Town✓3.4s🇮🇳Mumbai✕🇫🇷Paris✓1.4s🇸🇬Singapore✓1s🇺🇸San Francisco✓2.3s
Checked 3 h ago · 7 locations · this page updates by itself while it is open
Locations checked · 01:48 UTC
4 of 7 loaded it
fastest response –
Official status page
None published
we look for status.tnebnet.org automatically
Visitor reports, last hour
0
normal for this hour: about 3

About Tnebnet

It ranks #9,710 among the most visited sites in the world on the Tranco list.

The current problem is a partial outage that began on 8 November 2026 at 01:48 UTC and is still ongoing. There have been 4 incidents in the last 90 days, 21 h 16 min of downtime in total, and 82.57% of our checks succeeded.

Your connection
Testing from your browser…
This test runs in your browser and compares with our servers. Nothing about you is stored.

Reports, last 24 hours

0 reports · normally about 3 per hour
04:54 yesterdaynow
Problem reportedNo reports in the last 24 hours.
What is not working?

Get notified

One email when tnebnet.org goes down and one when it recovers. No account needed; unsubscribe from any email.

What we checked

01:48:06 UTC
LayerResultOutcome
DNS name lookuptnebnet.org resolves to 103.234.149.210pass
TLS certificateCertificate from DigiCert Inc, expires 2027-02-05pass
HTTP, PhoenixDNS resolution failed 3 h agofail
HTTP, Los AngelesHTTP 530 3 h agofail
HTTP, Cape TownHTTP 404 in 3.42 s · Reachable; answered HTTP 404 · via cpt1 3 h agopass
HTTP, MumbaiTimed out 3 h agofail
HTTP, ParisHTTP 404 in 1.37 s · Reachable; answered HTTP 404 · via cdg1 3 h agopass
HTTP, SingaporeHTTP 404 in 0.99 s · Reachable; answered HTTP 404 · via sin1 3 h agopass
HTTP, San FranciscoHTTP 404 in 2.33 s · Reachable; answered HTTP 404 · via sfo1 3 h agopass
ContentNo page title captured–
ReputationRun the trust check–

Outage history, 90 days

82.57% uptime · 4 incidents
Started (UTC)IncidentDuration
2026-11-08 01:48Partial outage · Phoenix: DNS resolution failed; Mumbai: Timed outongoing
2026-11-07 04:32Down · Phoenix: DNS resolution failed; CF: HTTP 53021 h 15 min
2026-11-06 01:37Partial outage · Phoenix: DNS resolution failed; Phoenix: HTTP 5306 s
2026-11-05 11:41Down · Phoenix: DNS resolution failed; Phoenix: HTTP 53019 s

Common questions

Is Tnebnet down for everyone or just me?

Compare the test from your browser above with our server checks. If our servers reach tnebnet.org and your browser cannot, the problem is on your connection, DNS or network. If both fail, the site is down.

How do you know if Tnebnet is down?

We request the homepage from 7 locations, check DNS, the TLS certificate and the HTTP response, and compare the page content with what we saw before. We also read the service's official status feed where one exists and count visitor reports against the usual rate for the hour.

What can I do while it is down?

Subscribe to the alert on this page and we will email you when it recovers. Clearing your DNS cache or switching networks only helps when our servers can reach the site and your browser cannot.

Related status pages