Checking now
Is Terms down?
Contacting terms.org from Dallas, Phoenix and San Jose…
- Dallas
- Dallas 2
- Phoenix
- San Jose
Checking now
Is Terms down?
Contacting terms.org from Dallas, Phoenix and San Jose…
It's just you — terms.org is up from all 4 regions we tested.
Checked 1 time since
What each region saw
| Region | Result | Response | DNS | TLS expires | Server |
|---|---|---|---|---|---|
| DallasDallas, US | HTTP 200 | 386 ms | 41 ms | 2027-01-01 (46 d) | nginx |
| Dallas 2Dallas 2, US | HTTP 200 | 747 ms | 405 ms | — | nginx |
| PhoenixPhoenix, US | HTTP 200 | 769 ms | 172 ms | 2027-01-01 (46 d) | nginx |
| San JoseSan Jose, US | HTTP 200 | 617 ms | 1 ms | 2027-01-01 (46 d) | nginx |
Resolves to: 217.19.248.132
TLS issuer: Let's Encrypt
Median response across regions for each check of terms.org run on this site. Red markers = DOWN.
Not enough checks yet for a chart.
No user reports yet. Anonymous, no account needed.
One tap sends an anonymous report. You can add a comment afterwards.
ipconfig /flushdns, macOS sudo dscacheutil -flushcache.A live badge for your README, docs or status page. It updates on its own, checked from 4 regions.
<a href="https://isitdownorme.com/terms.org" title="terms.org status on IsItDownOrMe"><img src="https://isitdownorme.com/badge/terms.org.svg" alt="terms.org status" height="20"></a>It's just you — terms.org is up from all 4 regions we tested. Last checked 15 Nov 2026, 16:38 UTC.
If our servers reach the site but you cannot, the problem is local. Hard-refresh the page, try mobile data instead of Wi-Fi (or the other way round), switch DNS to 1.1.1.1 or 8.8.8.8 and flush your DNS cache, and turn off any VPN, firewall or parental filter that could block the site.
None of the 1 checks of terms.org run here since 15 Nov 2026, 16:35 UTC found it down.
We test from four servers in the United States: two separate networks in Dallas, one in Phoenix and one in San Jose. This check saw: Dallas: HTTP 200 in 386 ms; Dallas 2: HTTP 200 in 747 ms; Phoenix: HTTP 200 in 769 ms; San Jose: HTTP 200 in 617 ms. If it works from all of them but not for you, your provider or a local block is the likely cause.
Opening this page requests terms.org from four servers in three US cities at once and records the HTTP status, response time, DNS answer and TLS certificate from each. The site counts as DOWN only when most regions fail, so one bad network path can't cause a false alarm.
Verdict rule: DOWN when most regions fail, DEGRADED when some fail or the median exceeds 3 s, RESTRICTED when the site answers 401/403/429 to our probes. Share this page: https://isitdownorme.com/terms.org